Cert from previous my.example.com found, affecting PTR record
After seeing a few posts about errors with the 6.3.3 update, I tentatively tried it on my Cloudron. It too saw the apps not starting, with nginx errors. But shortly after the 6.3.4 update was available, and running that seemed to fix things. But, in between the fail and the success, I poked around and found something interesting.
The Status pane of the email dashboard kept telling me that the PTR record was wrong - it was the previous domain I had used. This had been going on for WEEKs, and the VPS service set the PTR 3 times. I didn't bother posting because undoubtedly ppl would tell me to just wait for caches somewhere to clear. But this persisted.
Well, what I found in one of those cert locations was both my current domain, my.example.com as well as the previous one. I simply deleted the previous one, and then checked the Status on the email dashboard, and for the first time in what felt like forever, everything passed.
So if anyone else has that error about the PTR record, this could be the same issue I had.
@scooke Interesting. The certificate and the PTR record check shouldn't have anything to do with each other. The PTR record check is really just
dig -x IPADDRESS. Can you try that say 10 times over the course of an hour with your VPS server IP and see if it's consistent?
As for old certs, they are indeed preserved forever even if you remove the domain from Cloudron itself but the latest release will now clean up obsolete certs which are 6 months old.