cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution
Highlighted

NET::ERR_CERT_COMMON_NAME_INVALID when visiting my domain using https:// rather than http://

I recently found out that visitors to my domain get NET::ERR_CERT_COMMON_NAME_INVALID and are unable to view the site in Chrome and Firefox when they visit my domain and put https:// at the start.

 

I want to submit a support ticket, because I can't do real-time communication about technical stuff due to disability issues, but the only options I can see on the GoDaddy help page are 24/7 phone support and IM (currently closed), neither of which are suitable for me.

 

Does anyone here know how I can fix this issue, or how I can contact GoDaddy by email or by opening a support ticket?

 

Thanks! Smiley Happy

4 REPLIES 4
Solution

Re: NET::ERR_CERT_COMMON_NAME_INVALID when visiting my domain using https:// rather than http://

It's a Tumblr blog, and one of my followers on Mastodon dug up this: https://security.tumblr.com/post/166219476810/support-support-ssl-security-which-has-been

 

I followed the instructions in the last update, so we'll see if that resolves it. Smiley Happy

Community Manager
Community Manager

Re: NET::ERR_CERT_COMMON_NAME_INVALID when visiting my domain using https:// rather than http://

Awesome @cassolotl! Thanks for coming back and posting the info to help with this issue. Take care and hope to see you around the community again very soon.

Rachel

Re: NET::ERR_CERT_COMMON_NAME_INVALID when visiting my domain using https:// rather than http://

I have the same problem and I would like to know the solution Re: NET::ERR_CERT_COMMON_NAME_INVALID when visiting my domain using https:// rather than http:// thank you in advanc

Re: NET::ERR_CERT_COMMON_NAME_INVALID when visiting my domain using https:// rather than http://

I just ran into the same issue and there isn't an option to turn off SSL for a website in Tumblr anymore... turned out it looks like my SSL cert had lapsed, so have re-added it to my hosting subdomain. 

 

Even though the SSL is advertised as supporting subdomains, it actually doesn't (read through the link, you need a wild-card SSL which costs a big chunk of change). 

 

Then accidentally installed the SSL to my primary domain and had to re-attach it to my subdomain (which is my hosting domain i.e. https://host.somewebsite.com). You can't do this by default when you go install an SSL the first time (I.e., the easy setup). You have to manually create the common name and then manually install it via the C Panel. 

 

If you're an idiot like me and didn't know that, you have to re-apply the SSL from one domain to another. As in, moving the SSL cert from one godaddy domain to another. 

 

GoDaddy's documentation is a little confusing on all of this so here's how to do it:

 

First, uninstall the certificate that's on the wrong domain (or sub-domain) from the C Panel's SSL manager (not the *account* SSL manager). You have to change the common name through the SSL manager (I.e., the correct domain URL), wait for it to verify, then you have to download the .crt file through the SSL manager. Lastly, you have to upload the new .crt via CPanel's SSL manager to the correct subdomain / hosting account. 

 

Works like a charm but took a few hours to figure out.