Cloudron Forum

Update: Day 5 of the mystery backup issue After 4 days of backups appearing to succeed (no errors in the notification centre), the backup finally failed on day 5 with this error: Jun 07 01:24:44 BoxError: Not enough disk space for backup. Needed: 47.1GB Available: 45.71GB at runBackupUpload (file:///home/yellowtent/box/src/backuptask.js:192:15) at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async uploadAppSnapshot (file:///home/yellowtent/box/src/backuptask.js:359:34) at async backupAppWithTag (file:///home/yellowtent/box/src/backuptask.js:382:26) Jun 07 01:24:44 Exiting with code 0 This is confusing because: The server's local disk has about 60 GB free I don't see any backup files actually being written to the server itself So I'm not sure what disk or location this error is even referring to. I need to investigate further, but I'm posting this in case it helps explain what's been going wrong. Thread summary so far: There seem to be a few possibly related issues: Missing backups: For one app no backups were created from one day onwards. Though a second identical app was unaffected. Only discovered through a Cloudron restauration Backup to phantom location: After migrating to a new server, backups to a disconnected external drive kept succeding for 4 days. On day 5, that same location finally failed with a "not enough space" error referencing a disk that doesn't match anything visible on the server. Unreliable integrity check: Integrity check succeeded for backups which didn't contain the backup of the app in question (prior to restauration). Even on the backups to the phantom location, the integrity check kept succeeding

@james Sorry, perhaps we're misunderstanding each other. After upgrading to PeerTube 8.2, newly uploaded videos started generating both HLS versions and Web Video versions. Before the upgrade, only HLS versions were generated. Web Videos are disabled in the PeerTube Admin UI. The setting is also set to false in local-production.json. While investigating, I noticed that after every application restart, /app/data/production.yaml contains: transcoding: web_videos: enabled: true If I manually change this value to false, it is set back to true after a restart. I'm not concerned about the configuration file being overwritten. I'm trying to determine the actual cause: Is this an intentional change in PeerTube 8.2? Is this a bug in the Cloudron PeerTube package? Or is this a bug in PeerTube 8.2 itself? As far as I know, there is no other place where Web Videos can be disabled. The option is disabled in the PeerTube Admin UI, and local-production.json is also set to false. Nevertheless, new uploads are still transcoded into both HLS and Web Video formats. This worked correctly up to PeerTube 8.1, where only HLS files were generated.

@jdaviescoates Thanks. I can only confirm. Should have read the right posts. I get the feeling that LAMP-doable apps need their show window as well.

Hello Upstream reported that the issue will be resolved with the next release. https://github.com/ONLYOFFICE/DocumentServer/issues/3686#issuecomment-4631461296

@joseph Perfect

It also does Wireguard AND OpenVPN simultaneously, which is hella convenient

Thanks for the quick reaction!!

@girish Well, if developers like @luckow essentially maintain their own appstore, I fully agree. With all other community apps, you always risk going down the Yunohost way - a plethora of apps, many if not most unmaintained. Your USP is - inter alia! - that people can rely on well maintained apps. IMHO opinion, the goal should always be to maintain a broad-ranging, well maintained appstore. This is also relevant in a commercial scenario, where individuals/companies have to ascertain risks before implementing Cloudron („are those apps maintained and up-to-date?“).