The schema is documented in this file - https://git.cloudron.io/platform/box/-/blob/master/migrations/schema.sql?ref_type=heads . completed BOOLEAN DEFAULT false The id has to be unique in oidcClients table. Can you check why you have a duplicate? Maybe you can delete the dup entry and run the migration again.

Apologies, I got hung up on your point about the 'combination of search and filters' since I'm experiencing only getting the amount of entries that's set in the per_page value even when using only the search box without any additional filters active. I'm really looking forward to the rework then because right now even basic stuff like checking if a specific email was delivered or if a specific user logged in is a bit of a pain since I have to unfold the details of the first entries just to make the scrollbar appear to load more.

@joseph oh geez, ok thx ️

I had this happen at a recent upgrade to Cloudron 9. All apps but Vaultwarden were working, and the "Cloudron has no app configured for this domain" message was showing. Indeed, it was just a hard refresh to solve it in Zen / Firefox (how odd!)

We will show the domain, for which the API call failed, in the error message for a start with next release. https://git.cloudron.io/platform/box/-/commit/f421fd771ff0e0550381d012414a6c35c8fd2afe

@girish Thank you, girish for the update!

@girish Thanks ! I replaced the /home/yellowtent/box/src/storage/gcs.js with the patched version and don't get the "old backup not found" error. the backup is listed in System backups. everything seems to be fine ! Thanks a lot for your help !

Fixed in https://git.cloudron.io/platform/box/-/commit/9773c02e7d6fda7a9704ad8866d7e16ba11dcae3

Minio is basically dead for community edition. I rolled back to image: quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z (last version with all management features - don't expose it publicly for security reasons) Then: Configuration > Region > Restore Defaults That wiped my region entry and now Cloudron connects properly again. Time to consider successor software now.

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