@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

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

So the only version 9 of cloudron i can upgrade to is a prerelease version. This is a prod system, so id rather not.

3 1/2 years ago? Sorry, no I don’t even remember what I had for dinner yesterday….

Correct, I have updated all custom apps without a title in the manifest, this solved the issue.

the command "cloudron-support --unbound-use-external-dns" worked for me. Thanks for looking into it.

It may no longer be relevant since it successfully updated to 9.0.13. Seems to be related to an early version of CCAI. I've since updated it. box:tasks updating task 22301 with: {"percent":72.23846153846154,"message":"Snapshotting app ccai.toldyouso.com"} Nov 25 21:14:20 box:backuptask fullBackup: app ccai.toldyouso.com backup finished. Took 0.003 seconds Nov 25 21:14:20 box:locks write: current locks: {"box_update_task":null} Nov 25 21:14:20 box:locks release: app_backup_ef83ce0c-414b-49f1-969f-ecd520962d56 Nov 25 21:14:20 box:tasks setCompleted - 22301: {"result":null,"error":{"message":"Error creating config.json: ENOENT: no such file or directory, open '/home/yellowtent/appsdata/ef83ce0c-414b-49f1-969f-ecd520962d56/config.json'","reason":"FileSystem Error"},"percent":100} Nov 25 21:14:20 box:tasks updating task 22301 with: {"completed":true,"result":null,"error":{"message":"Error creating config.json: ENOENT: no such file or directory, open '/home/yellowtent/appsdata/ef83ce0c-414b-49f1-969f-ecd520962d56/config.json'","reason":"FileSystem Error"},"percent":100} Nov 25 21:14:20 box:taskworker Task took 896.054 seconds Nov 25 21:14:20 BoxError: Error creating config.json: ENOENT: no such file or directory, open '/home/yellowtent/appsdata/ef83ce0c-414b-49f1-969f-ecd520962d56/config.json' Nov 25 21:14:20 at Object.writeConfig (/home/yellowtent/box/src/apps.js:3071:15) Nov 25 21:14:20 at snapshotApp (/home/yellowtent/box/src/backuptask.js:340:16) Nov 25 21:14:20 at uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:351:11) Nov 25 21:14:20 at backupAppWithTag (/home/yellowtent/box/src/backuptask.js:393:32) Nov 25 21:14:20 at Object.fullBackup (/home/yellowtent/box/src/backuptask.js:569:56) Nov 25 21:14:20 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) Nov 25 21:14:20 at async updateBox (/home/yellowtent/box/src/updater.js:183:13) Nov 25 21:14:20 Exiting with code 0 @girish hope you can make this more resilient

@nebulon thanks, should have thought of that - yes, hard refresh makes it go away. prob needs some file versioning to force the new to load.

I also had similar issues as soon as I migrated to Cloudron 9.x and after a while or maybe after successful login attempts with an alternative auth flow, I had no longer any issues authenticating through OpenID. weird indeed but I have noticed similar complains about Cloudron 9 and OIDC in other threads.

Hello @nexus-ai-solutions and welcome to the Cloudron Forum It seems this is similar to https://forum.cloudron.io/topic/12500/after-update-8-0-5-all-services-wont-run-and-apps-wont-run-too-it-happen-7am-this-morning Can you please check that? If you run the following command manually: docker network rm -f cloudron what is the output?

--troubleshoot gave everything as "ok" however: root@my ~ # cloudron-support --check-db-migration /usr/bin/cloudron-support: unrecognized option '--check-db-migration' Running the start.sh fixed the backups page issue, and now the updates appear to be running (and the error is gone) thankyou!

@ghosted @mdc773 9.0.13 has the fix .

@ghosted said in Update 9.0.11 Broke Services: It was THOUSANDS of lines, currently had a production instance, so needed it back up asap. This is fixed now . Was a bug in the polling in the UI.

@girish said in Attempted to restore Cloudron 9.0.12, receiving error when loading backup configuration and hitting Restore button: @d19dotca I tried to reproduce this but I couldn't figure where to set this IP allowlist in iDrive e2. Maybe it's only for paying customers since I am on the trial plan ? Hi Girish. This link can help, assuming it isn’t gated to paying customers (I’m not sure if it is or not), but hopefully this provides some instructions for setting up an allowlist. https://www.idrive.com/s3-storage-e2/faq-buckets#ip-allowlisting I suspect you’re right though, that it is sending back a non-XML response to provide a response message that it’s forbidden from accessing it. I understand this use-case may be rare, but I think if there’s a way to improve that error handling, it may help others too because at first glance it’s really not clear where the issue could be coming from.