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

I thought this was fixed, but I see there is a new fix by @nebulon in https://git.cloudron.io/platform/box/-/commit/c2378d33b453a441709c585ab235102d61bcc1d4 . @nebulon should this issue be considered fixed?

@necrevistonnezr is correct. collectd has been removed in Cloudron 9 . @beardmancer it's normal that collectd says is it inactive (dead) .

Hi, just a quick follow-up. Even after updating to 9.0.13, the issue is still not resolved. The older backups are visible under each app, but the apps cannot be restored from them. And in Backups / Sites, I only see the backups created after updating to version 9.0.12 — all older system backups remain missing. The backup folders do physically exist on the storage.

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

Hello @imc67 Could it be that you simply need to zoom out of your terminal or make the window larger? Had the same first thought when running this command but when resizing the window or zooming out: [image: 1764363715688-4b9b8272-3458-4bf8-8e45-7adb9cc95592-image-resized.png]

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 .

This is fixed in 9.0.13 .