Thanks, I have fixed that in the docs now.

@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

Is this error still persisting, I cannot reproduce it here, since the tarball from that location loads just fine for me.

Nevermind. I will just have my host provider reinstall the OS.

@nebulon nevermind. It fixed itself. Weird.

@ruihildt This is not for deleting emails but for deleting a whole mailbox. If email is deleted, they are gone forever. You can see all the mailboxes under /home/yellowtent/boxdata/mail/vmail.

@scooke This was indeed a bug in our restore UI. I have fixed this for 4.1.5

Okay, that makes sense. Thank you for the quick reply. I wonder if it would make sense to add a feature where we can set the IP address to accommodate floating IP's in providers like DigitalOcean, so that the DNS records automatically setup by Cloudron in DigitalOcean would be using the floating IP instead. Without such a feature, it kind of removes the ability to have a sort-of manual failover method which is one of the main purposes of a floating IP from DigitalOcean (along with a secondary use-case of setting up a new server to replace an old one and moving the floating IP to the new one when ready, eliminating the need to update a whole bunch of DNS records). It would be nice, I think, to have Cloudron use a floating IP that we give it even if it means we have to set it manually in Cloudron first since it can't detect it automatically. The main reason for this is that whenever I switch a server, for example, nothing really needs to be changed at all, leaving downtime to a minimum if it exists at all during a server switch.

Indeed, missed that. Just making a blog post for 4.1 release which will include it.

We already implemented a mechanism wherein if the userId and the domain name matches, you will get subscribed to any previously subscription. If you have to change the domain, currently the only way is to contact support and give us the new cloudronId. @dustinddotca I guess you changed the domain name? Can you please send the new cloudronId to support@cloudron.io, will be happy to refund and transfer existing subscription.

@murgero Thanks for reporting, this was indeed a regression. Fixed now for the next release.

The version you are referring to is correct. So far we have stayed in-sync with ubuntu security updates, but probably have to revisit this and see if nginx can and should be indeed updated individually.

@dustinddotca If you add a CNAME record manually from mail.example.com to my.example.com that should work. Your email client might complain about certificate hostname mismatch but this is unlikely.

The app has now moved to stable, so the previous setting to list unstable apps is not needed anymore for WordPress unmanaged.

The tzdata package will fallback to UTC which is correct already, however sudo on scaleway comes pre-installed with a custom sudoers file, which we want to keep. So the fix is pushed via https://git.cloudron.io/cloudron/box/commit/9d237e7bd68f43ae59b4bbc591ef1d7680918567 and will be part of the next release.

Thanks @girish!

I tried to reply via your support email already. The cert on your domain looks valid to me, so please clear your history and cache locally for that domain first.

@girish Just as a quick add-on, if you have Comcast business class, port 25 may be allowed by calling the business support line. Same with ATT.

@doomilation Yes, what you have done should work. You don't have to move out appsdata and platformdata.