You can also speed up your website with our How to Speed Up Your WordPress Site guide.ĩ Easy Fixes of The NET::ERR_CERT_COMMON_NAME_INVALID errorīefore moving on to fixing the error, we would suggest you identify the reason behind its occurrence. If you are getting this issue while browsing your own website, then you should fix it as soon as possible. The misconfigured redirect can result in Google Chrome displaying the NET::ERR_CERT_COMMON_NAME_INVALID error.
In addition to this reason, another reason behind the occurrence of this error is the misconfigured redirect. This is why this error is called the common name mismatch error. It must be added in the SSL certificate either as a subject alternative name, wildcard or even as the common name. This error is most commonly displayed in Google Chrome when the domain name is not listed on the installed SSL certificate. Why is the NET::ERR_CERT_COMMON_NAME_INVALID Displayed on Google Chrome? Thus, ensure your SSL certificate name matches the address included in the webserver and the search console. If the name of the SSL certificate fails to match the web address within the addresses or search bar, it can result in an error. Your common name could also be similar to the web address that is included in the web server and the search console. The domain names have two different versions, one is If you are wondering whether or not the common name can have a subdomain, then yes it can have one. If you are trying to browse a website with abc.com with an SSL certificate, the common name should also be abc.com. The domain name must match your host’s web address, and these two must be exactly the same. The common name you see in the error is your domain name. What is The Common Name on an SSL Certificate That is Displayed on the ERR_CERT_COMMON_NAME_INVALID? This guide will help you fix the error and browse websites seamlessly. And today we will look at 9 easy ways to fix the NET::ERR_CERT_COMMON_NAME_INVALID error. However, fixing this error is relatively easy, just as fixing DNS errors. This error can be caused by a multitude of reasons, and one of the reasons behind this error is a misconfigured redirect.
This error can occur due to a common name mismatch when the SSL certificate’s domain is installed on but not listed on the certificate. But another reason for this error can be due to third-party extensions, antiviruses, and firewalls. A simple certificate misconfiguration on the server can cause this error. output of certbot -version or certbot-auto -version if you’re using Certbot): certbot-auto 0.40.NET::ERR_CERT_COMMON_NAME_INVALID is a common SSL error that is mostly seen when loading the website. I’m using a control panel to manage my site (no, or provide the name and version of the control panel):no I can login to a root shell on my machine (yes or no, or I don’t know): yes The operating system my web server runs on is (include version): RHEL 7 My web server is (include version): Apache 2.0, API version 20120211 I wonder, could someone help me get this sorted out? I’m out of my depth. Looking under Certification Paths, I see the two Let’s Encrypt Certificates, and a self-signed certificate in the trust store. There, it says that there are certificate issues - the certificates are out of order, and there are extra certs.
#NET::ERR_CERT_COMMON_NAME_INVALID INSTALL#
I followed the instructions to generate and install a Let’s Encrypt certificate - however, my site still rejects ssl connections.