[Support Guide] Troubleshooting SSL certificate errors

Hi there @Melvin, I saw that you are pretty active on this thread - I would really appreciate your support in helping me set up an SSL certificate for one of my Netlify websites.

The domain is superchargeyourprojectmanagementskills.com, purchased via GoDaddy. I delegated it to Netlify with the following steps. I checked that the NS records are updated via DNS Checker, and even ran a Let’s Debug test which verified that everything was OK. However, I’m not sure what I’m missing since it is stuck at the certificate provisioning step since the last 48 hours with the message ‘Currently provisioning your Let’s Encrypt certificate.’

Could you please help me debug the issue? Would appreciate any assistance! Thank you.

I checked all the steps in the main message. The domain NS settings seem to be correct.

However, the SSL has not been created for hours and I can only see the following screen:

When I try to visit the domain name, I get the following error: NET::ERR_CERT_COMMON_NAME_INVALID

Previously there was a button like “Retry SSL creation”. Now I can’t find this type of interaction anywhere in the panel.

Hi @rubyruins,

Thanks for reaching out and welcome to Netlify’s Support Forums!

I’ve renewed the SSL Certificate and it has now been provisioned for the site. You can see it here. Visiting the domain now properly resolves with the SSL certificate.

Let us know if you have any issues.

Hi @metnam,

Thanks for reaching out and welcome to Netlify’s Support Forums!

Could you provide us with the site name (for example sitename.netlify.app) or the custom domain that you’re having this issue with? That’ll help us investigate the issue.

Hi @Melvin, thanks a bunch! I can access the website via HTTPS now. Just curious about the issue, was there some misconfiguration on my end with the setup? Appreciate your help on this :slight_smile:

Hi Melvin,

Here is the subdomain: *** (edited)

Hi @rubyruins,

I don’t think it was an issue on your end, seems like somehow it just got stuck provisioning. I ran a command on our side to ‘renew’ the SSL certificate and it was then properly provisioned.

Hi @metnam,

Thanks for following up. I’ve renewed the SSL Certificate on your site as well. You should be all set now as I can see the SSL Certificate while visiting one of the domains and see the provisioning here. Let us know if you have any issues.

1 Like

Hi @ysoserious,

Thanks for reaching out! You should be all set now, you can see that the SSL Certificate has been provisioned here. Visiting the domain now shows as secure.

1 Like

Looks like this is resolved!

Hello @Melvin,

We’re using an externally registered subdomain for Netlify (netlify.dhis2.org) and for the last couple of days we’ve been having problems with getting SSL/TLS Certificates provisioned by Let’s Encrypt.

Here’s an example from one of our sites maps.netlify.dhis2.org:

Visting a Deploy Preview URL in the browser returns NET::ERR_CERT_COMMON_NAME_INVALID.

I went trough the troubleshooting guide, but all the tests seem to be passing and as expected.

$ dig netlify.dhis2.org NS +trace | tail -n 6    
netlify.dhis2.org.	3600	IN	NS	dns1.p04.nsone.net.
netlify.dhis2.org.	3600	IN	NS	dns2.p04.nsone.net.
netlify.dhis2.org.	3600	IN	NS	dns3.p04.nsone.net.
netlify.dhis2.org.	3600	IN	NS	dns4.p04.nsone.net.
;; Received 135 bytes from 198.51.44.68#53(dns3.p04.nsone.net) in 29 ms

I can’t find any way to “Renew” the certificate in the Netlify settings on our side.

Could we get some help with this?

Thanks!

Hi @radnov,

Thanks for reaching out! Sorry to hear about the issue.

I think, while looking at the site, that the issue is that you haven’t added the subdomain to the site yet. Additionally, only a Deploy Preview has been published and not production.

Could you try adding the domain here, and do a production deploy?

Hey. Thank you for taking a look at this!

We’re not using Production Deploys on most of our apps (if any), only Deploy Previews.

I just tried to add a different Additional Custom Subdomain for the Automatic Deploy Subdomain for our Maps app (changed from maps.dhis2.org to dhis2-maps.dhis2.org) and initially got an error like this:

But after a changing it back to maps.dhis2.org and waiting a bit the certificate got provisioned successfully.

Did the same for few other sites and got the same result. Seems like changing the Automatic Deploy Subdomain retries provisioning the certificate or something.

This seems like a bit of a hassle if we have to do this every time. Is there any underlying issue that could be the culprit?

I’m having issues with mine as well, I’ve registered my custom domain here with you, sorted out the DNS but for some reason it’s not integrating the SSL certificate by the looks of things? www.chromeextensiongenerator.com or extensiongenerator.com

I don’t see any CNAME for the subdomain:

dig CNAME +short @8.8.8.8 www.chromeextensiongenerator.com
> 

Hey @Melvin, sorry to bug you again, but did you get a chance to look at my latest reply above? The certificate provisioning is still stuck for our Capture app (note that I haven’t changed the subdomain back and forth as explained in my previous reply for that site).

Hi @radnov,

Thanks for following up. I’ve verified the DNS and you should be all set now with the SSL Certificate for that site. Could you let us know if you’re still having issues?

1 Like

Thanks a lot for looking at this again @Melvin. We are all set now. :thank_you:

hi @Melvin ,
I have trouble validating my TLS Certifications.
I have an error saying “missing certificates” but the DNS configuration looks good.
Can you check please ?
The domain name is : genquiz-ia.com
Thanks

Your site is secure. Please reach back out is not the case!