Cloudron Forum

I have successfully moved larger apps to an additional volume (Mountpoint) according to the documentation. My question is about backup and restore. (Awesome Cloudron feature) How does this affect backup? All apps backed up as normal?
And if I restore - I assume that the same mount points need to be in place -, but will the restore work normally then?
Thanks

OK just to recap - This seems to be working on my test system. This is after I followed the steps for my VPS to add a disk and the Cloudron instructions to add a disk and a volume. I did this as root. I used the "disk" in place of "volume".

Stop the app

mv /home/yellowtent/appsdata/dfaa72b8-8c42-433e-a001-c9d58563379b /mnt/disk/matomo/

ln -s /mnt/disk/matomo/dfaa72b8-8c42-433e-a001-c9d58563379b  /home/yellowtent/appsdata/dfaa72b8-8c42-433e-a001-c9d58563379b

chown -R yellowtent /mnt/disk/matomo/

Start the app
This would be nice to automatically happen with a Cloudron tool.
I will post back and edit if I find any issues when doing this on the production.
Thanks for all of the help.

OK now I will show my lack of linux. I did this all as root. What do I do now? How do I fix this permission issue? Thanks.

OK I have done the above, But get an error when doing a backup.

Problem:
I have a very large msqldump file (matomo) that is getting created when a backup is done. This is crashing my system eventually (disk full)
I have added an external disk to the instance and followed the very fine instructions to move the appdata location. This worked perfectly with no issues!

BUT the original yellowtent folder still contains a config.json file AND the large mysqldump. I just ran a full backup manually and it updated the file in the original location!

How do I redirect the location of this backup creation?

I need to figure this out soon.
Thanks a lot.

Yes it is possible to migrate to another Cloudron, but what's to say that the SSL will work on a different cloudron to the same domain that is having issues?

Ouch this is bad news. We have custom apps that directly work with API's in these cloudron apps.

yes.. I tried that 2 days ago when this started happening.

Yes we have all of our Cloudrons DNS automated - We have quite a few paid instances. This one instance is failing the automated renewal. That is the issue.

If you set up a new sub domain, do the certs work ok?

within GoDaddy or a new app in Cloudron?

BTW even the main "my.xyz.com" is also failing. Currently 4 apps installed in Cloudron.

OK I have access to the GoDaddy account _ have deleted the TXT record and restarted - I keep seeing the TXT record change, buy I get errors that they don't match. This is now a big issue I need to solve, but I am not very knowledgeable on LetsEncrypt. Where do I go from here?

No not yet - I have no idea how that would have happened. I currently do not have direct access to DNS records.

Nothing has changed from the initial install which went just fine several months ago - this just appeared.

One of our (paid) Cloud instances is refusing to update certs. Starting a couple of days ago. A manual refresh gets a lot of errors on the log. The client cannot log in - this is a big deal.
Where do I start?
filled with lines like this:
Dec 28 13:27:10 box:cert/acme2 sendSignedRequest: using nonce GJdccAF6CFXCywo_pgyPU5yKhGI7gls_ftlnroNQuIRwVCm8sb4 for url https://acme-v02.api.letsencrypt.org/acme/chall/1970589977/451963773075/ZgIswA
Dec 28 13:27:10 box:cert/acme2 waitForChallenge: status is "invalid" "{"type":"dns-01","url":"https://acme-v02.api.letsencrypt.org/acme/chall/1970589977/451963773075/ZgIswA","status":"invalid","validated":"2024-12-28T19:23:46Z","error":{"type":"urn:ietf:params:acme:error:unauthorized","detail":"Incorrect TXT record "dU24qPdE0kcVPGtd9z6Bf1KVFhUdUsO4QBFQPIpuXFc" found at _acme-challenge.fpiw-content.media","status":403},"token":"dDgFIftTVmWxvJ7vUeVLq-iux1rxrN_1-cw8SxaXWyU"}"
Dec 28 13:27:10 box:cert/acme2 Attempt 11 failed. Will retry: Unexpected status when waiting for challenge: invalid

https://github.com/alexta69/metube

https://github.com/alexta69/metube/raw/master/screenshot.gif

Run using Docker
docker run -d -p 8081:8081 -v /path/to/downloads:/downloads ghcr.io/alexta69/metube
Run using docker-compose
services:
metube:
image: ghcr.io/alexta69/metube
container_name: metube
restart: unless-stopped
ports:
- "8081:8081"
volumes:
- /path/to/downloads:/downloads
Configuration via environment variables
Certain values can be set via environment variables, using the -e parameter on the docker command line, or the environment: section in docker-compose.

UID: user under which MeTube will run. Defaults to 1000.
GID: group under which MeTube will run. Defaults to 1000.
UMASK: umask value used by MeTube. Defaults to 022.
DEFAULT_THEME: default theme to use for the ui, can be set to light, dark or auto. Defaults to auto.
DOWNLOAD_DIR: path to where the downloads will be saved. Defaults to /downloads in the docker image, and . otherwise.
AUDIO_DOWNLOAD_DIR: path to where audio-only downloads will be saved, if you wish to separate them from the video downloads. Defaults to the value of DOWNLOAD_DIR.
DOWNLOAD_DIRS_INDEXABLE: if true, the download dirs (DOWNLOAD_DIR and AUDIO_DOWNLOAD_DIR) are indexable on the webserver. Defaults to false.
CUSTOM_DIRS: whether to enable downloading videos into custom directories within the DOWNLOAD_DIR (or AUDIO_DOWNLOAD_DIR). When enabled, a drop-down appears next to the Add button to specify the download directory. Defaults to true.
CREATE_CUSTOM_DIRS: whether to support automatically creating directories within the DOWNLOAD_DIR (or AUDIO_DOWNLOAD_DIR) if they do not exist. When enabled, the download directory selector becomes supports free-text input, and the specified directory will be created recursively. Defaults to true.
STATE_DIR: path to where the queue persistence files will be saved. Defaults to /downloads/.metube in the docker image, and . otherwise.
TEMP_DIR: path where intermediary download files will be saved. Defaults to /downloads in the docker image, and . otherwise.
Set this to an SSD or RAM filesystem (e.g., tmpfs) for better performance
Note: Using a RAM filesystem may prevent downloads from being resumed
DELETE_FILE_ON_TRASHCAN: if true, downloaded files are deleted on the server, when they are trashed from the "Completed" section of the UI. Defaults to false.
URL_PREFIX: base path for the web server (for use when hosting behind a reverse proxy). Defaults to /.
PUBLIC_HOST_URL: base URL for the download links shown in the UI for completed files. By default MeTube serves them under its own URL. If your download directory is accessible on another URL and you want the download links to be based there, use this variable to set it.
HTTPS: use https instead of http(CERTFILE and KEYFILE required). Defaults to false.
CERTFILE: HTTPS certificate file path.
KEYFILE: HTTPS key file path.
PUBLIC_HOST_AUDIO_URL: same as PUBLIC_HOST_URL but for audio downloads.
OUTPUT_TEMPLATE: the template for the filenames of the downloaded videos, formatted according to this spec. Defaults to %(title)s.%(ext)s.
OUTPUT_TEMPLATE_CHAPTER: the template for the filenames of the downloaded videos, when split into chapters via postprocessors. Defaults to %(title)s - %(section_number)s %(section_title)s.%(ext)s.
OUTPUT_TEMPLATE_PLAYLIST: the template for the filenames of the downloaded videos, when downloaded as a playlist. Defaults to %(playlist_title)s/%(title)s.%(ext)s. When empty then OUTPUT_TEMPLATE is used.
DEFAULT_OPTION_PLAYLIST_STRICT_MODE: if true, the "Strict Playlist mode" switch will be enabled by default. In this mode the playlists will be downloaded only if the url strictly points to a playlist. Urls to videos inside a playlist will be treated same as direct video url. Defaults to false .
DEFAULT_OPTION_PLAYLIST_ITEM_LIMIT: Maximum numer of playlist items that can be downloaded. Defaults to 0 (no limit).
YTDL_OPTIONS: Additional options to pass to youtube-dl, in JSON format. See available options here. They roughly correspond to command-line options, though some do not have exact equivalents here, for example --recode-video has to be specified via postprocessors. Also note that dashes are replaced with underscores.
YTDL_OPTIONS_FILE: A path to a JSON file that will be loaded and used for populating YTDL_OPTIONS above. Please note that if both YTDL_OPTIONS_FILE and YTDL_OPTIONS are specified, the options in YTDL_OPTIONS take precedence.
ROBOTS_TXT: A path to a robots.txt file mounted in the container
The following example value for YTDL_OPTIONS embeds English subtitles and chapter markers (for videos that have them), and also changes the permissions on the downloaded video and sets the file modification timestamp to the date of when it was downloaded:

environment:
  - 'YTDL_OPTIONS={"writesubtitles":true,"subtitleslangs":["en","-live_chat"],"updatetime":false,"postprocessors":[{"key":"Exec","exec_cmd":"chmod 0664","when":"after_move"},{"key":"FFmpegEmbedSubtitle","already_have_subtitle":false},{"key":"FFmpegMetadata","add_chapters":true}]}'

The following example value for OUTPUT_TEMPLATE sets:

This look like a good replacement for Alltube (which we were using)
https://github.com/alexta69/metube

Yes they are on the same server BTW. Great information, we will give it a try. Thank you so much. I am bookmarking this!

Hi all, We have setup a client with Matomo and also Metabase.
They are looking to connect Metabase to Matomo. I think this is possible, but it looks like we need the port# for Matomo MySQL to complete this. It is not in the config file.
Any help here would be appreciated.
BTW has anyone done this?

Thanks!

False alarm, Sorry for the noise. User error. CDN setting and a typo in the env file on a system. Actually surprising that it was working except for the downloads, which I had not tested. Thanks anyway!

I several Peertube instances. The last several I have launched new I have download errors.
I do not have them on older ones that I have upgraded along the way. Here is the error message. These are connected to s3 and everything works perfectly except for downloads. The videos move to s3 just fine during the publish.
Any Ideas?

This XML file does not appear to have any style information associated with it. The document tree is shown below.

SignatureDoesNotMatch
The request signature we calculated does not match the signature you provided. Check your key and signing method.
streaming-playlists/hls/34cb8c52-126f-4be5-b002-95cff379331b/a458c24d-ece7-4f42-b15a-bd665ffdbd1a-1080-fragmented.mp4
bb1-video
/bb1-video/streaming-playlists/hls/34cb8c52-126f-4be5-b002-95cff379331b/a458c24d-ece7-4f42-b15a-bd665ffdbd1a-1080-fragmented.mp4
17F8D23A3169A2D9
cbd6dd2b-9818-4914-9563-a238e79685ef