NET::ERR_CERT_COMMON_NAME_INVALID is a common SSL error that is mostly seen when loading the website. A simple certificate misconfiguration on the server can cause this error. But another reason for this error can be due to third-party extensions, antiviruses, and firewalls.
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. This error can be caused by a multitude of reasons, and one of the reasons behind this error is a misconfigured redirect.
However, fixing this error is relatively easy, just as fixing DNS errors. And today we will look at 9 easy ways to fix the NET::ERR_CERT_COMMON_NAME_INVALID error. This guide will help you fix the error and browse websites seamlessly.
What is The Common Name on an SSL Certificate That is Displayed on the ERR_CERT_COMMON_NAME_INVALID?
The common name you see in the error is your domain name. The domain name must match your host’s web address, and these two must be exactly the same. 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 names have two different versions, one is WWW, and the others are non-WWW. The common name can be seen on both. If you are wondering whether or not the common name can have a subdomain, then yes it can have one.
Your common name could also be similar to the web address that is included in the web server 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. Thus, ensure your SSL certificate name matches the address included in the webserver and the search console.
Why is the NET::ERR_CERT_COMMON_NAME_INVALID Displayed on Google Chrome?
This error is most commonly displayed in Google Chrome when the domain name is not listed on the installed SSL certificate. It must be added in the SSL certificate either as a subject alternative name, wildcard or even as the common name. This is why this error is called the common name mismatch error.
In addition to this reason, another reason behind the occurrence of this error is the misconfigured redirect. The misconfigured redirect can result in Google Chrome displaying the NET::ERR_CERT_COMMON_NAME_INVALID error. If you are getting this issue while browsing your own website, then you should fix it as soon as possible. You can also speed up your website with our How to Speed Up Your WordPress Site guide.
9 Easy Fixes of The NET::ERR_CERT_COMMON_NAME_INVALID error
Before moving on to fixing the error, we would suggest you identify the reason behind its occurrence. This error can be caused by a number of reasons, and if you successfully identify the issue, you can resolve the issue effectively. We have listed out several solutions for resolving this error. Have a look at the given solutions to eliminate this issue when browsing websites.
Check Your Browser’s Extensions
Obsolete and problematic browser extensions can be a primary reason behind chrome net::err_cert_common_name_invalid error. To check if the browser extensions are the reason behind the error, you should try browsing the website in incognito mode. If the website is accessible in the incognito window, the problem is because of any extension you have added to your browser.
If the website is working fine on incognito mode, then it is time to find out which extension is behind the problem. Navigate to the three dots located on the top right corner of your browser, and select the “more tools and extensions” options. Turn off the extensions one by one, and check if the website becomes accessible. This will help you identify the faulty extension. Delete that extension and you will be able to run the website seamlessly.
Check For Redirects and WWW vs Non-WWW
Almost all SSL certificates cover both WWW and non-WWW accounts by default. You should stop redirection of WWW websites to non-WWW websites and vice versa. This depends on the domain you entered when you purchased the certificate. Thus, it is important to confirm whether your browser is redirecting visitors to another part of the website. You can also make adjustments to the settings to resolve the problem of redirection.
If you bought the wildcard SSL and the main domain redirects to subdoamian.com, it will be displayed in the browser. The redirect is necessary in this case to get another SSL certificate. This will cover the redirecting of traffic to the chosen domain. Thus, checking your redirects and fixing them can help you resolve the NET::ERR_CERT_COMMON_NAME_INVALID error.
Clear Your SSL Cache
The browser’s SSL cache can also be an issue behind the error that shows you “your connection is not private; attackers might be trying to steal your information.” Clearing the browser’s cache can assist in resolving the error and make the website accessible.
If you are getting this error on IE or Edge, you should start by opening the internet properties and find the tab named “content”. You will find an option “Clear SSL slate” on this tab, and it will let you clear your browser’s SSL cache.
For Chrome users, the process is somewhat similar. Open the browser, and click on the three dots located at the top right corner of your browser. Find the “settings” option and navigate to the “advanced settings” option at the bottom of the page. Now open “proxy settings” and you find the “content” tab there. Click on the option to “Clear SSL Slate” and your SSL cache will be cleared.
Check If Your Date and Time Is Accurate
If the date and time are not accurate on your mobile and computer device, the browser may show the NET::ERR_CERT_COMMON_NAME_INVALID error. To fix this issue, you must recheck the date and time of your website and ensure it is accurate. If you find the time and date are incorrect, you should adjust them and try accessing the website again. If the website becomes accessible, then the issue may have been because of an incorrect date and time. However, if the issue is still not resolved, you can use other solutions to resolve this error.
Check Installed SSL Certificate
One of the primary reasons behind the ERR_CERT_COMMON_NAME_INVALID error is the wrong SSL certificate. The wrong SSL may not support the correct domain and sub-domain name. This can end up in a mismatch result and lead to an error. This error can occur if you have issued the SSL for a domain but installed the same SSL for a subdomain.
To resolve this issue, you can check your web browser. Navigate to chrome and click the “not secure” option on the left side of the address bar. Then, click on the “certificate” and you will be able to view the SSL certificate details in the “issued to” field. You can also check the details using the Online SSL test by SSL labs, it will show more accurate results.
Also, ensure that Self-Signed SSL is not in use. These types of SSL certificates are only used for internal purposes.
Purchase and Install SSL Certificate For Your WordPress Website
A common reason behind the common name mismatch error is forgetting to purchase an SSL certificate. But similar to other issues, these can be fixed easily too. Several WordPress users enable the HTTPS protocol for their websites but forget to install and buy an SSL, and this is why they get the NET::ERR_CERT_COMMON_NAME_INVALID error. This can affect the visitors who want to browse your website, and it is a server error that you can fix using two possible solutions.
The first solution is purchasing an SSL certificate and installing it on your web server.
The second solution is changing the HTTPS back to the HTTP protocol. This will enable your website without the encryption and protection of data and you will not need an SSL certificate.
Update Your Browser and Operating System
This solution works in almost all cases. Whether your website is experiencing DNS issues, or ERR_CERT_COMMON_NAME_INVALID error, updating your browser and OS can fix them. You should first check if your browser or operating system is running on an obsolete version. If it is, you should update it to get them on the latest version. Updating your browser and operating system may resolve the error and make the website accessible.
Due to common bugs and system errors, some websites become inaccessible, and the NET::ERR_CERT_COMMON_NAME_INVALID error occurs. However, developers come up with new and improved versions regularly to fix these bugs. Thus, updating your browser and OS from time to time can prevent these errors in the future. If this solution doesn’t work try any other method from this list.
Check Your Proxy Settings
If you have not set your proxy settings to “automatically detect settings,” you may face multiple errors, including the ERR_CERT_COMMON_NAME_INVALID error. This setting can affect your browsing experience and limit you from accessing some websites. Thus, you should check if this is the reason your browser is displaying the “your connection is not private chrome” message.
This setting can be resolved following some quick steps. First, navigate to the network access icon by right-clicking on it, and click on the “internet properties options.” choose the “connections” tab and then go to the “LAN Settings.” You will find a window, tick the box located right next to the “automatically detect settings.” After you have enabled this setting, try to check the website to see if it has become accessible.
Check Your Firewall and Antivirus
Some antivirus and firewalls can also block the SSL connection and lead to the NET::ERR_CERT_COMMON_NAME_INVALID error. You should check the Firewall and Antivirus settings to check the LOG files. This will ensure that your firewall and antivirus are not blocking the website you want to access. When you see the error message displayed on the screen, review the blocking reason. Sometimes, antivirus may block a website that can be a threat to your system. If this is the case, you should not access the website. However, you may be able to access the website by disabling Firewalls and antivirus. But we do not recommend doing that.
In the list above you can review all the popular solutions to resolve the NET::ERR_CERT_COMMON_NAME_INVALID error. This error is easy to fix, and following the steps above, you can do it yourself, without any expert help. However, if you are being blocked by accessing your one website and none of the solutions works. Then the problem can be on the eth server-side, and you should get it fixed. A slow or inaccessible website is not good for business. This is why we recommend optimizing your website to keep it accessible and easy to navigate for visitors. We hope the solutions in this article help you resolve the error and browse websites easily.
Also Read- How to Fix the ERR_CONNECTION_REFUSED Error