As you mention, you need a separate account for accessing the app library. Do you see any errors in the browser console? Alternately you can also sign up first at https://console.cloudron.io/#/signup and then use that account to login via your Cloudron dashboard.

This is handled in support by now. The AAAA records for that domain are not set up.

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?

I've solved the docker daemon problem, I just couldn't start my docker on my pc. But for the rest of my problems I still don't have an answer.

Always good to hear, if things are fine

@girish Thank you, Cloudron team, once again for the great work. After updating Cloudron, the problem is resolved. Thank you very much.

I fixed the DNS

No, it was a one-time issue so far. I posted it more as a bug report. Version 7.7.2, by the way.

Please send an email to support@cloudron.io with your Cloudron Id or cloudron.io email address.

@luckow The info has moved to a separate section called Info. The updates section looks a bit empty in 8.0.3 yes...

well I had to reset and reinstall to have access again.. can close the topic

Sounds good! It was also odd that some other apps were affected by the restart-looping Nextcloud instances.

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.

I have submitted a new AMI in any case.

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.

Ok that file is showing regular checks but no packages marked for upgrade. I will keep an eye on this. Thanks for the support.