@girish thank you, Girish. I already ensured that my server is running security updates using those commands.

Marking as solved due to inactivity.

@derin can you open a separate topic with that request for nextcloud? can you also elaborate on your use case for this (does nextcloud the app support aliases?) ?

@girish same issue here, totally unexpected and unannounced 1of 3 Cloudrons updated itself to 9.0.11 last night and the first backup at 8:00h failed with same errors. Opening the config and safe it (and remount) solved it. Compared to previous backups it's really slow, before 2 minutes for complete backup, now at 30% after 30 minutes. Hope this gets better 🤨

@luckow Maybe some sort of shared hosting? Should be able to support lots of wordpress instances, LAMP stacks and Surfer apps.

Perfect. Everything works as intended. Thank you, @girish, and have a great beginning of your week

This has gone back to normal for a few days in a row, indicating the upgrade didn't produce an issue, but probably the hardware infrastructure at Netcup.

Hello @maellerollet and welcome to the Cloudron forum It sounds like you are running into this issue: https://docs.cloudron.io/troubleshooting/#domain-issues-expiry Please check this documentation and see if this helps to resolve your issue.

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

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

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.

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 !