@webliska Send the header from the Email Log here and check if you have the application password in the “Profiles” tab.

If we have a way to reliably reproduce the issue, we can see if there is a workaround for that S3 provider, but most likely it is some issue on provider end, if this is not happening all the time. Sadly the S3 implementations between provider are not always behaving the same way. We use the AWS S3 SDK for all requests, which is the standard.

I was in a similar situation as you. However, rather than bashing my head (figuratively) against the same wall, i just moved to a vps with more space. Granted, this was before using external volumes was as easy as it is now. But reading that your two main apps are Immich and Sync thing... there's two walls. Listen, there are amazing workarounds and solutions offered by Cloudron and from others on this forum. But, I've never viewed any of this as "recommended and official"; it's more, "enough people refuse to/can't do the obvious, so how can we help them?" The obvious being - get a server or vps or whatever that has all the space you need. It's one reason I moved to ssdnodes (but just enough users have not had a good experience with them so this isn't an ad, I've just had excellent results with them and the 1.2tb server they offer.)

@girish I don't think I've hit this issue myself, but why not just push out an 8.3.3 with this fix?

Joseph. Thanks for the reply. Would it be something that you would be considering for the future, the possibility to add a feature move email data to a volume? I have a single domain with 25gb of mail. If it cannot be moved off I will have to enlarge the droplet. Thanks for your help and a great product.

@wu-lee we have to implement this feature. Currently, Cloudron will only accept email from external sources when incoming email (MX) is enabled. Even with incoming email enabled, it only accepts email from defined "mailboxes" . i.e as a hack you have to create a mailbox as a relay endpoint. BTW, why not just use the relay features of your MX?

Right, as you already figured out, you have to resize the fs manually. https://docs.cloudron.io/storage/#aws-ebs . Cloudron was more of an app deployment platform. Though after many years depending on which problems are often reported, we are putting in server management features (maybe we will add fs resize at some point).

You can check if the server itself is particularly low on memory by running free -m . Can you give nextcloud much more memory (in the Resources section) ? What is it at currently ?

Cloudron uses SRS for mail forwarding. Does SES support SRS? I think off late gmail has also changed behavior wrt SRS. I think @girish is aware of this already, there is no fix currently.

Back from vacation. I had to write a script to search the backups for gitlab backups that had postgresqldump files with actual data. Apparently the last "good" backup that had a good postgresqldump file was back in April (2025-04-24-090000-501/app_gitlab_v1.103.0.tar.gz.enc). I was finally able to get it working by reapeating the restore steps: Install the matching version of Gitlab to the backup version Then restore by importing the backup Not sure how exactly it got to this state, but it's finally back up and running!

Disk space. Ram. Probably the two* main components of a server that will make running Cloudron (or any software, really) a pleasure or a pain. But I think the easy answer isn't necessarily the best - buy a server with lots of disk space and lots of RAM - because use-case factors in alot. Perhaps some sort of pop-up questionnaire at some point in the purchase stream or set up process asking which apps are likely to be used would be one way to give a user a heads-up that their 4GB RAM, 60GB SSD server isn't going to cut it (or in this case an 8GB running Gitlab! Plus, it seems they are running additional software on that server, this "Mesa de Ayuda" which seems to be some kind of helpdesk software... Cloudron clearly advises running only Cloudron on a server and nothing else, so that was utilizing the same minimal 8GB of RAM). That said, I moved my Mastodon app off of my main server which has 64GB RAM and successfully run it on another server with just 4GB RAM plus 4GB swap, plus a Wordpress app, with stable results. I've also run a Presearch node on a 3.5GB RAM server along with Cloudron, and it all worked. *A third would be using Cloudflare. I know why ppl use it, I just don't know why ppl use it.

@ruben.villarreal I got your mail on support@ and I have reset the app installations on our side. Can you please confirm?

I was able to resolve this. I created a subaccount API key that I used for authentication before generating a secret key for the primary API key (by default Mailjet creates a key but not a secret for that key, which is a manual action). Now I just generated a secret key for the primary API key and used this instead of the subaccount key and it worked.

Here my 2cents; I personally host my Cloudron at Hetzner I enabled in front of Cloudron Cloudflare and Enable proxying for new DNS records (that is inside Cloudron at the domain level) Enable Firewall at Hetzner for my Server HTTPS only between my Cloudron and CloudFlare [image: 1756114585161-brave_9vbg9hsube.png] you can find the IP here Why ? So even if someone retrieve the IP (example via mail service) it cannot try to hack any webapps. Of course; I have others Rules at Hetzner Firewall Level; that basically replicate Cloudron's Firewall: SSH, Mails, STUN, TURN, ... After that; you mostly need to choose wisely the apps you deploy; trust the due diligence of these developers. Having a WAF; bring more complexity that would probably slow down the integration of new apps...

Thanks! Can't wait to see the light

@girish Is this use case covered in Cloudron 9?

We will need a more complete logfile @jamie.mckenzie . Have you tried cloning that backup?

@ImatBagjaGumilar can you check host -t NS <domain.com> 127.0.0.150 on your server? You can also try to run cloudron-support --troubleshoot to check if DNS is working on the server.

@avatar1024 said in issue with email delivery going through Cloudron mailing lists.: also started using Lismonk for larger distribution lists. Is that what you're still doing? Do those somehow magically get through to Gmail addresses OK?