@keldorn Can you please try this: Take the raw file from https://git.cloudron.io/platform/box/-/raw/417f5c36100ba63f41c4841c742b64a8448a2308/migrations/20250724141339-backups-add-siteId.js and put it into /home/yellowtent/box/migrations/20250724141339-backups-add-siteId.js Then run, sudo /home/yellowtent/box/setup/start.sh

Fixed in https://git.cloudron.io/platform/box/-/commit/3e6f3bd807a63e38711ace7e83eb5e2b722299b5 . Thanks for reporting!

Okay, with 9.0.10, backup was able to be completed.

I came here after facing this issue for the first time I first rebooted and retried. Then I found this thread, I saved the config, remount the storage, re-entered the private ssh key each time on each screen just in case. It seems to have solved the issue fortunately there is the forum, otherwise it's easy to panic I got no email for backup failed error, is that expected? @girish I have backup failed "enabled" in the notification settings

So turns out that potentially the issue is disk space. we ran the process again without changing anything - same result we clean up and enable at least 40 GB of space and relaunched the update process = successful update suggestions: better pre-update space check and verbose messaging about needed space for update

I came here to learn about Hetzner having periodic issues. Thanks @girish ! I'm currently facing a similar issue on a Cloudron 9.x instance and was looking for old threads mentioning the exact same error. Here am I. Damn Hetzner then @girish is there a support ticket open with Hetnzer or anything that we can do?

Hello @jkammerer I understand that backward compatibility is desired. In this specific case it was actually a bug in the previous version that the field could have been left empty in the API call and it worked. People still use pop3 and we have to accommodate for this.

hai @guacadmin , are you using ubuntu in Alibabacloud?

This was reported in the other thread. Was fixed - https://forum.cloudron.io/topic/14359/cloudron-9.0-beta-bug-reports/128

I confirm. It work without 127.0.0.1

Thanks a lot, that was tho Problem. I changed the user rights from Administrator to Superadmin an it's working as expected.

This is the server: RS 4000 G12 I have about 350 GB on the server. Note that the time increase didn't happen with the upgrade to Cloudron 9, but only to 9.0.6. It was fine with 9.0.5 and before constantly, and backups take much longer each time since the upgrade.

Ok, based on the box.log file I got a LLM/Claude debug session going and it was pretty quick showing me, that there was a docker container (postgres) running that was attached to the Cloudron Network, but not managed by Cloudron. I think that was something I set up super early, before I understood how Cloudron works. Claude helped me dettaching it and now the update went through without issues and everything is running again. Thanks for the hint with the box.log file @joseph !

@nebulon , per request: https://forum.cloudron.io/topic/14525/improving-user-experience-with-ssh-keys-for-sshfs-and-volume-mounts Many, many thanks. And, if I find anything useful, I'll update that thread. Or, this one, and cross-link.

Creating the AAAA DNS record for : *.mydomain.com *.my.domain.com with IPv6 address solved the problem. Thanks !

Have you configured the domain from the get go with OVH and that token during Cloudron installation? If so, was the dashboard domain created correctly or did you do this manually?

For the future, support@cloudron.io is a better id for all billing and support queries .

To update everyone here, this is fixed with https://git.cloudron.io/platform/box/-/commit/21191bdc5075bfd334c11d9ffc321e222fa0b6d4 Turns out the code would cleanup ssh identity files when a temporary mount (for the app import) gets removed, despite that key file still being used in another volume or backup site. Root cause was that the key file name was just the host of the remote, which is not unique. We have made the filenames now unique.

Good catch, this is fixed now with https://git.cloudron.io/platform/box/-/commit/c35543af924a5cc8e82eac8c8fc0ef8139503f5a The quota sorting was also off.