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 !

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.

@necrevistonnezr I guess you mean the rsync binary. Sure that will work "locally" but the real benefit of rsync (protocol) comes from having a server component. This server component will not be used with nfs mounts (the topic of this thread). If you want to use rsync just locally, there are also other tools you can use. I don't have any context more than that one sentence though I was just replying in passing.

@smitrparikh 8.3.2 is the latest stable version of Cloudron . If you are asking about Cloudron 9, it is being rolled out slowly. The update will appear in the coming weeks.

In my case it was a Redis service not being active, thanks!

As long as the config is in a separate file at /etc/apt/apt.conf.d/ , it should be OK.

@svtx do you have a post/more info on this already? Would like to understand what the problem is.

@ExocortX what if you add an additional SPF for your domain? @girish there should be a way for Cloudron to have clean notifications when configs are correct. For many it’s psychological and triggering their ADHD or OCD.

@nebulon No luck, I don't have a reliable answer for you.

As @james mentioned, things will keep running fine, however since we do not automatically downgrade to the free tier for the moment, you will not receive any app updates at that point. Just ping us at support@cloudron.io with your Cloudron ID once the subscription has ended, and we will reassign the free tier then.