@james the resets for a long time no longer regularly, at least the mailboxes and the instances are still unchanged for over a week. Also gives it a problem with nextcloud which is in an update loop sometimes you get the very current version and sometimes you have to update 2 times up to the current version.

Ah sorry. Yes, it works now. Thanks very much! BTW. I have tried the "impersonate" option and it has a similar problem...

jdaviescoates said: Yep, the most recent rsync back-up into the new folder (rather than the same folder as the rsync backups were going into before the server migration) worked fine too and now I have rsync backups that pass the integrity check - finally! So it seems clear the issue was some file changes that happening during the full Cloudron server migration got rsync confused. Think I may have spoken too soon. Every rsync back since the one that passed the integrity check has failed it again [image: Screenshot from 2026-10-04 13-30-28.png] It's always the Jellyfin app that fails. Plus once also the Mail server again.

We have fixed some of the apps developed by us like surfer, calendearm, mail,.... to gracefully shut down handling the SIGTERM. Will be part of their next releases. So thanks for bringing this on the table good to have that improved!

Thanks, I have fixed the regression.

Thanks, this was an oversight and indeed the task got never refreshed. This is fixed then with https://git.cloudron.io/platform/box/-/commit/6178538a4c4b712b426a8b11eeb6ae8ac5fe9f10

This is now fixed for next release with https://git.cloudron.io/platform/box/-/commit/d122f06a05803f2cb71a51d5e9a7f078202ca71b

Hello @dualoswinwiz Thanks for providing the output of the troubleshoot. Your Cloudron version 9.2.0 is outdated. The latest Cloudron version is 10.0.5, and we are moving towards Cloudron 10.1. Since Cloudron 9.2.0 many improvements and fixes have been implemented regarding Passkeys. Please update your Cloudron to the latest version so we ensure this is not just an outdated Cloudron issue.

@james Well, looking at the logs, it’s actually running fine. Even though the UI dashboard looks stuck at 5%, I managed to successfully update it to version 10.0.5

@humpty Not just you, but usually if you refresh the page, it goes to 0, so probably a caching thing.

Hello @archos This is already fixed in the upcomming Cloudron udpate.

Hello @jayonrails The only instruction was: james said: To fix this please run the following command from your ssh root/sudo session: bash /home/yellowtent/box/setup/start.sh But you also did run: systemctl stop box apt install mysql-server systemctl start box From the log it looks like everything worked out correctly. Please make sure to carefully read provided instructions in the future since you did run commands that where not instruced to be executed. Please also read https://forum.cloudron.io/post/129886 which explains that the binlogs might not be purged correctly and how to clean it up. Otherwise some binlog files might remain and block some diskspace.

@msbt previously, forwarding feature did not use sieve rules. It was implemented in Haraka, so this setting was not needed.

Hi @james - I also received a response today. Hope its the same group of people you talk to I let the AI compare the responses: Key differences between response I received and from your summary: Root cause: GC overload vs. synchronous unlinking of old object data. 504: Both say the proxy times out after 600s while backend processing continues. HEAD vs. GET: Response I received assumes processing may still be ongoing and no data loss; from your summary says the affected data is unrecoverable. CopyObject / MPU: Covered as under investigation in response I received; not addressed in your summary. Fix: General GC optimization vs. explicitly decoupling GC from CompleteMultipartUpload. Anyway - looks like we helped uncovering the root cause

Thanks, that did it! I increased total swap from 4 GiB to 8 GiB, leaving the backup task’s memory limit at 3 GiB and all other backup settings unchanged. The next attempt completed the backup successfully, then updated Mastodon from package 1.19.1 to 1.19.2. Thanks for pointing me in the right direction!

omg.thanks - I really thought I did that... working now

Thank you very much for the reply. I’ve implemented it, and the issue is resolved. Regards.

There's nothing to be embrass - It's still a great platform! So thank's .)