@murgero Thank you bro! I learned how to create and manage SSH keys via terminal today. I'm going to start learning how to do basic Linux Terminal Commands now. So when installing Cloudron, I should select Let's Encrypt - Wildcard and turn that to yes. Anything else that you recommend?

@Mightymoose There are two flavors of the WordPress app - managed and unmanaged (the former has blue icon and the latter has a grayish icon). Which one did you install? Can you try re-installing the app?

@girish Hi, everything is ok now, after my s3 storage provider fixed their S3 error SSL certificate . Thanks

So, it seems like giving the app a "relocation" by pressing the save button under the Location config tab & a quick Cloudflare proxy off-on, and then some time is the fix. EDIT So it is Cloudflare that is the problem and not Cloudron. Specifically their proxy

@girish Will do. It's actually not the first time I've run into the problem and a re-fresh of the API credentials solved the problem, although this is the first time I specifically observed that it was a 500 error vs. a 401.

Thanks for the reply, @girish. Doing a host -t NS lead me to find that the NS records were not added in DigitalOcean. Adding them in fixed the problem.

@girish thanks for the info!

@bangden07 Ah, that's a smart work around! I just noticed that you had SSL issues on the root domain. The wildcard cert only covers subdomains i.e *.foo.com but not foo.com. Cloudron still has to get normal certs for foo.com. I guess after a week, you can remove the cloudflare proxy.

@girish I'm always amazed at how quick you guys on these things, thanks for fixing that so soon!

Thanks for the thorough reply @girish , I've updated my DNS accordingly and the certificates renewed! I'll figure something out with the Github Pages (or self host on Cloudron!)

@iJoel You can do this by simply concatenating the intermediate and CA cert files into a single cert file. So, in the '.crt' file which you upload to Cloudron, it will have: -----BEGIN CERTIFICATE----- the *.foo.com certificate -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- intermediate cert -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- root cert if any -----END CERTIFICATE----- The ordering of the certs is important above.

@Peter-Newman did you manage to narrow this down any further? I can't think of an obvious reason this will happen. Please ping this thread again if you hit this issue.

I tried to reply via your support email already. The cert on your domain looks valid to me, so please clear your history and cache locally for that domain first.

Another option is to simply Disable mail and then Enable mail for the domain. This will effectively end up copying the certs.