Cloudron Forum

@Kinzi said in Problem recieving emails when using AWS SES:

The questions was: I thought I need that MX for the DMAR/DKIM to work?

No MX is not needed for DMARC or DKIM. They are separate concepts.

Setup script hanged in the earlier cases.

Great! Thank you so much for the detailed and helpful answer 🙏

Back again now - https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

Thanks. I’ll give it a shot!

I am still confused why they demand an answer from you, if your website is getting abused...

@plains-digital yes, you can also restore app by app. https://docs.cloudron.io/backups/#import-app-backup . But obviously, restoring entire server via backup is far simpler.

@arshsahzad the ocsp thing is only a warning and not a fatal error. But let's continue on support.

Ignore me. This was an issue with PowerShell apparently. If run from linux it works fine.

Thanks again

@macone see https://docs.cloudron.io/email/#firewall

@prusaman If the instance has no IPv4, how do you ssh in ? Via a jump host?

@nottheend said in Help wanted: Mount EFS in EC2:

My only unfulfilled wish is to exclude the nextcloud data now from the cloudron backup.

You can disable the backup for the app but that is of course living dangerously 🙂

@girish perfect! Thank you so much! I really highly appreciate the effort! Thanks! I see it now!

@krishnav Is https://aws.amazon.com/elasticloadbalancing/ the product you are referring to? Can you post a screenshot of how you have configured the load balancer? And where are you seeing this error message?

Also, any reason to use this load balancer?

@adhithiyan I thought I fixed this in 7.2.2 . collectd has an option to disable FQDNLookup. Can you tell me which version of Cloudron you installed ? If you don't remember, you can check the file /home/yellowtent/box/VERSION. It's also in the Settings page of the dashboard (this appears only after you have setup cloudron).

That took a while but we are back in business - https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

@scuba9273 glad you figured it out and thanks for sharing the solution!

I updated the email relay page with newer screenshots of the SES console - https://docs.cloudron.io/email/#amazon-ses

@girish thank you, that made it a bit easier 👍🏼

Just found the solution here: https://forum.cloudron.io/topic/1279/receive-email/4

The problem was that AWS EC2 instances close port 25 by default. As soon as I opened it in the AWS console, I was able to receive emails.