I have created an ssl cert that apparently doesn’t work with .www. I do not have a certbot. What should I do? (I am sure the cert was also created for .www)
My domain is: dksdroner.ga
The operating system my web server runs on is (include version): Monster FTP (Unknown version)
But how it's possible that a Cloudflare customer server produces such a result? If the SSL of the customer server is broken, Cloudflare sends a typical error message and shows a SSL page with a http status 523 - Bad Gateway.
Right... but as we can now see, the Let's Encrypt cert on the origin server is working fine. So the problem is/was on Cloudflare's side.
My understanding is that this is how they respond when they should have a valid cert for the domain, but don't. Whether because of an issuance delay or a propagation delay or whatever, I don't know.
@SUBLOLLIPOP, in case you don't know, grey clouding everything disables Cloudflare's CDN, so that you're only using their DNS service. If that's what you intended, then great, it's working now However if you actually wanted to use the CDN you'll have to switch it back to orange cloud at some point. In that case you should proceed to try the remaining steps in that guide. If that doesn't help you'll probably have to ask Cloudflare for support.