Hello @james ! Just normal cloudron apps like Mattermost or n8n that does not integrate with cloudron authentication and does not provide SSO

@avatar1024 in the previous versions, one could change the backup format between tgz and rsync . We used to track the format of each backup (for restore from old backups to work). in Cloudron 9, you cannot change the backup format of a site once set. instead, you can just create a new backup site if you want another format. The migration code probably detected that you have backups in both formats. So, it would create two sites - one tgz and one rsync. That's what you are seeing .

@tecbox thanks for the report. The fix is https://git.cloudron.io/platform/box/-/commit/b759fdb6e35762ef5586c3e552a387c4aef15a42#da95ffafbc09b42991a792cd9824d5814e1ec274_373_372 . You just need that one line change. Edit /home/yellowtent/box/src/storage/s3.js . Then change line 372. Basically, remove the leading slash at the front. No need to restart anything after making the change. Make a new backup, it should work. Can you please let me know? return `${bucket}/${output}`; In Cloudron 9, we upgraded the AWS library from v2 to v3. It's possible that v2 library automatically removed this trailing slash. Maybe in v3, they don't do this anymore. Hard to find any info, but it seems in other providers both works.

System -> Services -> sftp -> Restart . This usually fixes it. The sftp container is also used for file manager services.

@james @joseph thanks for your fast replies. I managed it with the hint from joseph and also created a new api token. Works well now. thnx!

ok thanks, below the result after just a few minutes, I'm not a technician but as far as I can see it's mainly mysql which is writing (I sorted Write): [image: 1764682318506-de0b4ce4-096f-4c6b-977b-dcf6574125ea-scherm-afbeelding-2025-12-02-om-14.30.00-resized.png]

@archos I wonder if the backupcleaner removed the entries from the database by mistake. Have you tried searching for the old backup in the eventlog? Maybe it hits one of the backupcleaner tasks . Just a thought.

@saikarthik I deleted the registry config. mysql -uroot -ppassword -e "DELETE FROM box.settings WHERE name='registry_config'" Then, re-run the migrations: /home/yellowtent/box/setup/start.sh After the upgrade, you can re-setup the registry . But you have to shorten the password length to < 128 chars.

@necrevistonnezr @joseph Ah, got it, thank you for clarifying. For what it's worth, I was following the upgrade guide for Ubuntu 22.04 (https://docs.cloudron.io/guides/upgrade-ubuntu-22/) which indicates that it should be active. Probably a decent number of people will follow the same trail I did: Cloudron updates to 9.x --> Notification about 20.04 EOL --> Follow 22.04 upgrade guide. If none of these folks need to worry about the collectd step, it might be worth adding a note in the 22.04 guide. The 24.04 guide also mentions collectd. While it's fresh in my mind and I'm looking at it, is there any reason I should or shouldn't go ahead and upgrade to 24.04?

@joseph Thank you. That seems to have fixed the problem.

@nostrdev you can pass -p or --port-bindings to cloudron install . It will query it. You can also pass directly using -p NEO4J_BROWSER_PORT=someportnumber,BOLT_BROWSER_PORT=anotherport .

The mysql db was corrupt beyond repair. I reimported from a back up and things are good.

@Teiluj said in 2FA enforcement issue on Cloudron 9.0.13: (major issue) 2FA enforcement does not work. Fixed in https://git.cloudron.io/platform/box/-/commit/76f2c5f9fc7ea673ddbe02e5aed9e691c85cd5c6 Thanks for reporting!

@woolfdrs3 It seems the server is running on OpenVZ which Cloudron doesn't actively support. However, it works after I added this workaround: # cat /etc/systemd/system/docker.service.d/openvz.conf [Service] Environment="DOCKER_IGNORE_BR_NETFILTER_ERROR=1"

@simplo thanks for reporting, fixed now - https://git.cloudron.io/platform/box/-/commit/fda393b5e148340e2dc138f31a5a6443fa8d0ee3

All the apps are back, thanks for your support !

@maxman I still cannot ping the IP address on your dashboard domain . Could there be some router/firewall setting that need to be tweaked since the IP changed? From the troubleshooting you posted, I think you can safely ignore Cloudron at this point. Cloudron itself is running fine, the server is just unreachable .