My netlify site name is yourideal.health.netlify.app
Custom domains yourideal.health and www.yourideal.health
I have been getting the “We could not provision a Let’s Encrypt certificate for your custom domain” error message for three days while using netlify DNS.
The verify DNS configuration comes back clean as well as the Let’s Debug. when I try to provision the certificate it says “missing certificate”.
The only thing I notice as being a potential problem is that on DNSchecker it doesnt propperly show up in Mexico City but is good everywhere else.
I made sure there is no DNSSEC enabled and I have not run it through a proxy or accelerator, I just switched DNS from namecheap to netlify 3ish days ago and the longest ttl should have been 48 hours so I am just wondering if there is any glaring issues I could have made in my setup.
Not sure but I can also add my DNS records if required.
There don’t seem to be any SSL errors at all that I can see. Where are you seeing SSL errors? In your local browser or somewhere else? Would you be willing to please share a screenshot of the error?
Well this is awkward… I guess asking made it work. I was having the unsecure statement when opening the custom domain all through this morning right before posting the question as well as the error message in the domain management area. Now it seems to be working. The youridealhealth.netlify.app seems to be unsecured still but that shouldn’t really affect anything for me.
Is there some reason why the Named Servers do not show up in Mexico City (just curiosity, you don’t have to answer).
Not sure what happened but I’m sure you fixed it by looking. Thank you Luke,
Do you have the IP address for the DNS resolver that isn’t working? If so, what happens when you query it directly? I ask because my best guess is that the ISP is blocking DNS lookups that do not come from its customers. So the resolver is working it just looks like it is not because it does not allow dnschecker.org (or anyone else that is not their customer) to use it.
The meaning here is not clear. What are you asking here?
An SSL certificate failure after successful DNS verification indicates that while the domain ownership was confirmed, other issues are preventing the certificate from being properly used or trusted.
