Success! Thank you!

yes- was my error/ all resolved. Issue was I had disabaled some of the app backups under app level but then had selected to back these up in global settings but seems the global settings do not overide the app level backup settings/ nor is there anything in global settings to inform backups for sepcific apps have been turned off at app level (maybe this could be added).

@luckow not sure if that is the right expectation, you have to use env vars. Password is just one or the many config vars of an addon. Addons can change because of user actions. For example, a user changes the SMTP addon address, user changes internal ports of an addon, user changes oidc scopes etc. In many PaaS setups, they will cycle passwords periodically, so hard-coding will never work even if you don't move instance in the long run. The behavior is the same in all app deployment platforms - heroku, DO app. See https://devcenter.heroku.com/articles/add-ons#config-var-values-can-change for some rationale.

@webmaster we do offer direct support for businesses. We have a business plan exactly for businesses such as yours. If you are on a business plan, you can contact us at support@cloudron.io and we respond in a day.

@joseph said in Old system backups are not listed: 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. Thanks, Joseph. I checked the Event Log, but I don’t see any entries from backupcleaner or anything indicating that older backups were removed or pruned. All older backup folders are still present on the storage, but Cloudron simply doesn't list the system backups created before the upgrade to 9.x. To clarify: Older app backups are visible under each app, but older system backups are missing entirely, and restoring an older app backup fails with the fsmetadata.json ENOENT error. So it doesn't look like backupcleaner deleted the files – it just seems Cloudron no longer recognizes the old backups after the upgrade. Let me know if there is anything else I should check.

@joseph excellent work. Seems like it was designed for an RPM distro.

ohh yes thanks Cloudflare proxying is on. Turned off and all appears again- although I cannot quite work out exactly what is blocking it in cloudflare

@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 .

@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!

@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 !

@robi this worked, thank you. I hadn't realized there was a way to check services like that (I had another issue previously telling me to restart nginx, which I never could find out how, but this worked for that too). thanks for the help!