@shan I will mark this thread as solved. Let's follow up at https://forum.cloudron.io/topic/7750/backup-uploads-time-out-after-12-hours-can-no-longer-manually-adjust-timeout-to-be-longer

@subven Thanks! I will create a cloudron backup now, thanks for the idea.

You don't need a second app. Copy the files your app is missing from your latest backup (without using Cloudrons "restore from backup" function). Take a look at my output. Compare with the files in your backup and the one in your (broken) live app.

Fixed in https://git.cloudron.io/cloudron/box/-/commit/84ba333aa11fe7d0e2ae00d2b1437efc27a876b4

@girish hey forgot to mention. My IP is not listed but the AS network is declared as spammy. While I contacted OVH for this and I respect their answers, they said they are not willing and paying for deblacklisting their network because it like an hostage situation. So I asked them to change the IP of my instance, let's see.

Turns out the mountpoint for backups, which is /mnt/cloudronbackup/ had leftover files, which prevented it from being mounted. After clearing that folder it works fine. I will see how we can better communicate this into the dashboard to make this more obvious in the future.

Maybe try creating a filter in Snappymail and see how it is different in Thunderbird.

Create a backup using rsync and restore from it rsync does not store symlinks (as tgz does).

@burrito what are you using to arrange the 2 networks ? firewall ? managed switch ? VLAN on either ? I'm no expert, about to try setting up similar myself. I think someone who can answer will likely want to know how you are creating and managing the 2 networks.

I am just adding the docs for the proxy feature for 7.3 The release is out as unstable (gives us some time to update screenshots, write the blog post, update docs etc), so I will give it a few days before it can be ready for general use.

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.