Experiencing "NET::ERR_CERT_COMMON_NAME_INVALID" errors

[MikeRosTX]

Is your feature request related to a problem? Please describe. While setting up a GitHub Page using a Custom domain name on GoDaddy,com, I kept getting the following "NET::ERR_CERT_COMMON_NAME_INVALID" errors intermittently:

Describe the solution you'd like While researching this issue a bit more in-depth, I stumbled across this GitHub troubleshooter to secure an https site:

https://help.github.com/en/github/working-with-github-pages/securing-your-github-pages-site-with-https#resolving-problems-with-mixed-content

Describe alternatives you've considered So it looks like the resolution was to replace all the http references for https on 120 files on my own repo. You may need to consider changing these references on the template so that GitHub Page can Enforce HTTPS on Custom domains.

https://github.com/MikeRosTX/mikerostx.github.io/commit/af28cdd7123e9f30f881011acdc665ce48a7b56c

[MikeRosTX]

Well I thought that I had resolved these intermittent errors "NET::ERR_CERT_COMMON_NAME_INVALID" by replacing http with https on 120 files, but intermittent errors are sill occurring. I'm back to the drawing board of troubleshooting.

[MikeRosTX]

Not sure if this helped or not, but as soon as I added it I noticed that it immediately started working, 🤔 I'll continue monitoring.

[christianezeani]

Hi @MikeRosTX

It looks like you're experiencing issues that have to do with SSL misconfiguration. I just checked your site's info and saw that the SSL Certificate was issued to shortener.secureserver.net - that is why you're getting the NET::ERR_CERT_COMMON_NAME_INVALID error. The links below might be useful:

• https://uk.godaddy.com/community/SSL-And-Security/SSL-for-a-forwarded-domain/td-p/148378

For more info on the above error, visit:

• https://www.ssl2buy.com/wiki/how-to-fix-err_cert_common_name_invalid-in-chrome

NB: It might take a couple of hours for changes to reflect on your browser

[MikeRosTX]

Thanks @christianezeani! I've already tried everything mentioned in the 2nd link from www.ssl2buy.com. Following thee article from GoDaddy, I changed the TTL in the red box from 600 seconds to 1 hour. The first IP 184.168.131.241 is fixed by GoDaddy. The 4 IPs 185.199.x.x are GittHub Pages IPs. I'll keep monitoring. But in order for GitHub Pages to Enforce HTTPS every reference in the code has to be https.

[christianezeani]

Alright @MikeRosTX. I'll make those changes asap

[MikeRosTX]

Deleted the Forwarding piece below from DNS Management on GoDaddy, and left A and CNAME records. So far it seems to be working better. I'll continue to monitor this issue.

[christianezeani]

Changed http references to https. These changes were made to the template files, 3rd party libraries were (and should be) left untouched.

[MikeRosTX]

Looks like the "NET::ERR_CERT_COMMON_NAME_INVALID" errors was a combination of things:

1. http references needed to be changed to https, to allow GitHub Pages to Enforce HTTPS.
2. The extra A and CNAME records on GoDaddy.com that were removed.
3. Also the Forwarding of domain name at the bottom of GoDaddy.com DNS Management that was removed so it doesn't forward any domain names to GitHub Pages.

The "NET::ERR_CERT_COMMON_NAME_INVALID" errors has not reoccurred in several days.

[christianezeani]

Nice to hear that.