Cloudron Forum

Thanks for sharing the solution. Maybe there is a corner-case bug in the database migration about the directory server config.

@jdaviescoates actually it should work with any cloudron apps that use the mysql addon (and no other database addons)

@TheNils If you write to us on support@cloudron, I can debug further. It's not clear what's going on.

@girish thanks, that worked 🙂

@msbt said in Can't manage existing email address since v7.3.4 update:

for debugging, lmk if needed

Not needed. Just takes a really long time to fetch for domains with bigger maildata.

Thanks @girish 👍

@thenils I have pushed a new package, can you please check? It should have composer 2.1.8

@tx-hermit Ah, here's the explanation - https://serverfault.com/questions/1024770/ubuntu-20-04-time-sync-problems-and-possibly-incorrect-status-information . Uninstalling/disabling ntp service does the trick! I will make a fix for next release.

@TheNils If you think it's worth getting those apps published, please join our chat at https://chat.cloudron.io if you have any questions 🙂

@TheNils See https://forum.cloudron.io/topic/1813/site-embedding-x-frame-options-partially-broken-since-cloudron-4-1-3 if it's roundcube + nextcloud

@TheNils For new domains, the NS record sometimes takes to propagate. That error message means that it's not propagated to the Cloudron server yet. You can try this:

SSH into the Cloudron host -t NS mydomaine.net (This should not display NXDOMAIN) If the above works, it should work on Cloudron as well. If not, can try sudo systemctl restart unbound and then try adding the domain again?

We will improve the error message to be more descriptive (https://git.cloudron.io/cloudron/box/issues/548).