Site name: kiwiplates-uat.netlify.app
Custom domain: preprod.kiwiplates.nz
I’m having issues with my website, when navigating there on chrome I get the message " This site can’t provide a secure connection", I had this issue on other dev sites which was fixed by switching from my custom certificate to lets encrypt, but even when doing that on this website, I can see it is still using my custom cert.
So I have 2 questions.
1.) Why did my custom wildcard cert suddenly stop working? After seemingly no changes to the site.
2.) Why, when switching to use lets encrypt, is my website still trying to use my custom cert?
Hi, @asap_fraz. This site isn’t serving the custom certificate now and I’m not seeing it in our database currently. In short, I don’t know why it stopped working as I don’t see it at all now. Do you have the certificate being used somewhere else now and, if so, what is the URL to see it in use?
Regarding why the custom cert would be used when switching, if the switch fails then current certificate continues to be used.
For our own provisioning of Let’s Encrypt’s wildcard certificates, we can only issue wildcard certs with a DNS based verification method. This is only possible when Netlify DNS is used and not with the external DNS instructions.
Note, there is an inactive DNS zone under Netlify DNS for this domain here: