Domain error ERR_CERT_COMMON_NAME_INVALID

Support
,
1

Hello,

I setup a new domain, but after almost 48h after setting the DNS, I’m getting the error:

NET::ERR_CERT_COMMON_NAME_INVALID
Subject: *.gridserver.com
Issuer: Go Daddy Secure Certificate Authority - G2

I also have a mail DNS from GoDaddy:

MX 0 smtp.secureserver.net
MX 10 mailstore1.secureserver.net

And I’ve already hit “Renew certificate”.

What should I do?
Thanks

2

Hi, @podrivo, and welcome to our online community.

Netlify can only provision an SSL/TLS certificate if the domain being provisioned is pointing to Netlify.

I’m not currently seeing the DNS records required to point the custom domain to Netlify. There are two ways to do this:

You might try the second URL’s instructions for the initial configuration and them move to Netlify DNS later once this is working.

When I test currently, the required DNS records do not exist:

$ dig gridserver.com NS  +noall +answer

; <<>> DiG 9.10.6 <<>> gridserver.com NS +noall +answer
;; global options: +cmd
gridserver.com.		4999	IN	NS	ns2.mediatemple.net.
gridserver.com.		4999	IN	NS	ns1.mediatemple.net.
$ dig gridserver.com A  +noall +answer

; <<>> DiG 9.10.6 <<>> gridserver.com A +noall +answer
;; global options: +cmd
gridserver.com.		4999	IN	A	64.13.192.60
$ dig www.gridserver.com CNAME  +noall +answer

; <<>> DiG 9.10.6 <<>> www.gridserver.com CNAME +noall +answer
;; global options: +cmd

This IP address above (64.13.192.60) is one controlled by Media Temple, not by Netlify.

Would you please try one of the two DNS configurations at the links above (either/or - not both) and let us know if there are other questions?

1 Like
3

Hey @luke,

The domain was already pointing to Netlify, but I think the SSL/TLS certificate was created before I updated with GoDaddy mail DNS records, so it took it’s time to renew it and make everything working again.

Thanks so much for your quick reply!
All the best.