@atrilahiji hello, sorry for being late, got sick. like that: "dockerImage": "cloudron/org.wordpress.unmanaged.cloudronapp:20210208-171207-630daccf7",

Have you made sure DNS settings for previous mail settings have been all removed from the domain's DNS, before you've tried another approach? And, sometimes it takes awhile for the DNS settings to work. If you've been trying this, and that, and changing settings in the DNS, then it could just need a bit of time for the most recent to propogate.

@ianhyzy ah, good to know! basically, the snap version of docker starts with it's own container data which seems totally separate from the normal docker.

@fbartels thank you for the advice

I end this thread because I now have a more specific one going.

Debugged this with @ZeZaung a bit. Somehow, it was possible to re-run cloudron-setup on the existing install and this reset the database even though the app containers and data were still there. I have made a fix which should hopefully mitigate the problem.

@vladimir-d The only other case an app is restarted without anyone triggering it is if an app using the tls addon had the certificate renewed. Unless this is a custom app, there is only the AdGuardHome app that uses the tls addon. So, is this app AdGuard Home? I think you can get more insight by looking into the corresponding logs at the lines above those lines. What does it say above the lines you posted?

@imc67 keep an eye on this thread: https://forum.cloudron.io/topic/2457/owncloud-infinite-scale?_=1621875492434

@dylightful if you click the 'cleanup backups' button in the Backups view, is there anything interesting in the logs?

@christiaan I submitted a new image to the marketplace. Will leave a note here when it gets approved. Sometimes it's immediate and sometimes it takes 2-3 days.

@nebulon you would need a list of app backups that are allowed to fail (app store apps) and ones that aren't (system services). Partial backups are only ok if an app store app gets an error.

The root cause for this turned out to be disk I/O related. Leading to a postgres database startup time longer than 60sec. Our current code will kill the container if it takes longer than that for initial startup and thus the service never came up. The workaround solution was to stop apps temporarily until the postgres service is healthy and then start the apps one-by-one.

@privsec Note, just because it's "running" doesn't mean it's running well.

@christiaan on the free account, there is not much info we collect, so that is to be expected.

@d19dotca ah, noop is for the DNS. For the certs, if you click on advanced (in the Domains view), it will let you choose self-signed/fallback certs. That way it won't use let's encrypt.

@artd2019 Currently Cloudron does not offer (a documented) "whitelist" / "allow list" function, so there is no way to guarantee deliverability of an incoming email. There is a feature request for it already that I'd encourage you to upvote. Version 6.3 coming in the not too distant future is supposed to deliver on many of the email improvements users have been clamouring for (including myself). One thing you can do if you're not already is making sure to remove those emails from the Junk / Spam folder in order for SpamAssassin to unlearn the message as spam. Eventually after a sufficient number of them, it'll learn that those emails are not spam and will decrease the BAYES probability of it being spam. On a related topic, you may want to consider enhancing your SpamAssassin rules list from the defaults, specifically in your case the BAYES_## rules perhaps as I have offered previously in this forum.

@d19dotca I fixed this now. It cleans up certs which expired 6 months ago.

@d19dotca said in Loading Event Log page throws ER_OUT_OF_SORTMEMORY: Basically the real settings are coming from /etc/mysql/mysql.cnf, right? Yes, they are the same file as you found out. In any case, the change I made is good because ORDER BY <xx> should always have xx indexed in the database to lower memory use.

@robi That's the icon!

@girish Thanks for that command. It is indeed strange and I haven't seen it on other Cloudrons, so something must have got stuck with this one. Not a big deal, but it's nice to have that message not displaying any more.