Mail queue is exposed in 7.3, so you should be able to clean such files from the UI in the next release.

@nebulon Okay, thanks. Importing the backup wasn't completing successfully since I'd had to use the Clean Backups function to free up space. I ended up just restoring the last backup image of the whole Droplet from DigitalOcean. That put things back as they were the night before the disk filled up so I only lost items from a single day. I was relieved to find that once I'd gotten things back to a green status I was able to complete the setup process for an external backup in an S3 object storage account. I tried setting up Backblaze B2, DigitalOcean Spaces, and Wasabi on Sunday and Monday, but they always errored out with a complaint about the bucket not being available to the region the DO Droplet is located in. Monday I was able to get my DigitalOcean volume mount set as external backup, but obviously don't want to use block storage for backups. Once I'd restored the droplet and resolved the space issue, though, I was able to add B2 as external backup storage with no issues. Thanks for the help!

The First Time Usage dialog is shown by clicking app configure -> book/docs icon -> First Time Setup. [image: 1664268781989-c4a6f027-913b-46da-aa28-c80a284e55ff-image.png]

@dylightful thanks, fixed now with https://git.cloudron.io/cloudron/dashboard/-/commit/8de1befcdb98a715c1542204fa389c051f340bd8

@d19dotca Thanks for that answer the guide is perfect.

@nebulon That sounds like exactly what happened, what kind of monitoring solution would you recommend for cloudron (interested in space and RAM monitoring)? We've been hesitant about using any sort of apt get for fear of interfering with cloudron operation

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.