So turns out we've resolved this portion.

Main issue is there were way too many confs pointing to the main problematic certficate. Everything in /home/yellowtent/platformdata/nginx/applications basically needed to be moved (/removed) in order to get nginx to restart again once more

Thank you, the same happened with a browser that had never opened the site, I think I will continue checking.

Alright, just for future similar issues,

here is the solution : sudo -u www-data php -f /app/code/occ files:scan "username"

https://docs.cloudron.io/apps/nextcloud/#rescan-files

It's also possible you are on a very old version of Cloudron (like Cloudron 6, where we initially introduced translations). You have to clear the browser cache in that case.

@axbom said in Has something changed with Ghost email config?:

After I changed the support email address everything seems okay.

I think there used to be one place you could change both, then they changed it. I got caught out by it too.

@msbt this would really be a separate feature request forum post, if you don't mind 🙂

Updated first post with more data.

@Refugee_Ranger said in Enormous Security Hazard:

Cloudron will configure Cloudflare for DNS only

By default, Cloudron configures any new app for DNS only. You have to go to the Cloudflare dashboard to enable proxying. Once you enable it in Cloudflare, Cloudron will preserve the proxying flag.

There is a bug in the current release that the code crashes when trying to send a notification if a backup failed. This is fixed . I think in the coming releases we can explore more notification options but atleast now you should get an email.

@eddowding Ah, perfect. I actually sent you a note from support early today morning, but that was probably too late.

To follow up here, the next release 7.3 has built-in support for external links in the dashboard, so it will be unnecessary to install some trampoline app like surfer or lamp.

@jdaviescoates Cool, works perfect!

@nightmare thx i try that later

@nebulon So, I am looking for the web terminal and this file manager. I am sure I am missing something simple.....

Ahh I found them - they are in the app that is installed! Got it!

@nebulon This worked! I just replaced the old one, not sure how to add a second one. But I have an installation. Now to check it out... Thanks a lot!

@BrutalBirdie So I figured this out, and it's definitely NOT a Cloudron issue. Actually, it's a Thunderbird issue... so I'll probably go write a quick report on Bugzilla at some point.

It turns out that when you hook up two emails for Thunderbird that (1) go the same mail server and (2) share the same password, that causes Thunderbird to ignore the username.

What this means:

Let's say you set up two mailboxes in Cloudron, your.name@company.com and service@company.com. While your.name@company.com is accessible to you, service@company.com is instead accessible to a group you are a part of. You can use user account password to log into both.

Let's say you first add your.name@compay.com to Thunderbird. It will work fine. However when you add service@company.com, outgoing will be messed up (though incoming will work). Rather than outgoing being registered for service@company.com, it'll go out through your.name@company.com, which is not the correct behavior.

You can fix this by going into Outgoing Servers in Thunderbird, but it's a big pain it doesn't need to be, and I'm sure it's something that can be fixed on the Thunderbird end.

Anyways, that was a fun dive into some email issues... hopefully I can get this fixed and jump back into using groups, as that helps make security issues with emails a little easier to deal with (no having to reset everybody's shared password).

Hope you all have an awesome day!

@chris thanks for creating those!