Looks like that was the fix, now it doesn't change the A and AAAA records of the email server, and Cloudron can still use my External SMTP connection while having the Mail Server Location set to "cloudron.blockbluemedia.com".
@timbo I have practically zero spam with the rules mentioned in my post and abusix DSNBL (https://abusix.com/) - the free tier is sufficient.
Do you have catch-all enabled?
Just to note here, a server reboot often is not the best idea if some services are still up and running. Nearly everything can be fixed while the server is active and a reboot might just bring down those unnecessarily.
Looks like some tmpfs corruption caused files to have incorrect permissions. The reboot cleared up tmp and the previous state was not there. Just redownloading 8.0.1 and updating again made it work.
Yes, /24 would only allow 250 or so addresses, we do need a /16 . I am not sure why 172.17 and 172.18 networks are conflicting though . In the original error message it says "172.18.0.1" is in use. If your local network is 172.18, it all makes sense. Currently, there is no workaround for this since the code has some places where it hardcodes 172.18 network.
@girish
Interesting case, for 2 days it failed. There were attempts after clearing the browser, a trial on another device. Today it just started to work but for that it changes the permission after saving the file from ‘www-data’ to ‘root’.
Edit: Good with the entitlement is good, just need to refresh the page.
We haven't added a way to add custom persistent iptables rules . For SSH though, just move it port 202 and disable root auth and password auth. This usually cuts down all bots to 0.
