Fix SSL Common Name Mismatch Error like ‘ERR_CERT_COMMON_NAME_INVALID’ in Chrome

This article very clearly talks about how to get rid of common name mismatch errors regarding the SSL certificates in Chrome.

SSL errors are also known as SSL ‘connection error’. This error usually occurs when one is attempting to achieve a secure and safe connection in a website server. SSL error results when the SSL certificate executions are deficient and sub-standard. One of the most common SSL error is the SSL Common Name Mismatch Error or ‘ERR_CERT_COMMON_NAME_INVALID’, a result of certificate misconfiguration error in the server.

To fix ‘ERR_CERT_COMMON_NAME_INVALID’ error, it is important to identify the possible cause of the error. Here is a list of possible causes for which this error might occur.

The inaccuracy of Date and Time

Date and time might seem to be simple in a device and might feel to be insignificant. But, incorrect dates and times might cause severe errors like this. One of the main reasons for SSL error is the inaccurate date and time of the device or system used to access the server. As all the information is saved as an authentic record in the server, the wrong time and date might mislead to fallacy and piracy. Hence, before accessing the SSL certificate of any website, check and fix the date and time of the device to the current date and time.

Perilous Extensions

If there is an SSL error found, the first thing one needs to check is the extension is okay or not. Opening an incognito window and pasting the extension is the easiest way; if the site opens, then the problem is resolved. Or else, one has to check one by one extension of the server. The first one needs to disable the extensions found in (Menu>More Tools> Extensions). Now, trigger every single extension to check if the error continues by browsing the website. Once you find the error-extension, delete it from the browser and your error is resolved.

Confirmation of the Correct Certificate

When the domain name and the certificate name mismatch, this error can happen. For example, one might install the correct certificate; however, the certificate might not cover the web address typed. If there is another certificate installed in that web address this clash will occur. Then one needs to check for the domain and sub-domain name that one is browsing as it is required to be registered under SAN (counts every domain separately) and wildcard certificates (cover single-level sub-domains).

Redirects Check- Non-WWW/ WWW

All SSL certificates by default does not cover in the WWW or non-WWW accounts. One should cease the redirection of non-WWW to WWW or vice-versa during the purchase of the certificate. It is important to confirm whether the browser is compellingly redirecting its visitors to any other part of the website. These adjustment needs to done from the settings to resolve the error. It is one of the most common reasons why err_cert_common_name_invalid on google chrome can be seen. As it is a very common error to find, it is also very easy to be fixed.

The Aptness of the Cite-Address

As the users are always curious, one might interchange the site protocol from an unsecured HTTP to secured HTTPS. When the saved changes do not have an SSL certificate bought or installed, there is a change in the site protocol that caused the “NET: ERR_CERT_COMMON_NAME_INVALID”. If the certificate is not installed or bought, it is recommended not to put‘s’ before the ‘HTTP’ (one having WordPress). It is better to go back to WordPress general settings and do the URL checking first.

Clearance of SSL State

Net::err_cert_common_name_invalid edge is the problem that can be resolved if there is an SSL cache available. The common name mismatch error in SSL can be solved in this same way. For this, one needs to open the ‘internet’ properties. Next, go to the content tab followed by clearing the SSL cache. And thus the problem is resolved. How to resolve the problem using Google Chrome is mentioned below in steps.

Settings

Advanced settings

Change proxy settings

Clear the SSL slate

And the error is resolved. It is a very common process; this problem can be resolved using any other browser in the same way.

Proxy Settings Checking

The common name mismatch error can occur when the proxy settings are not set according to the ‘Automatically detect settings’. It will not just make the user face an error but also affect your browsing experience. Besides all these, it will also restrain you to surf other websites on your browser. Here is the flow chart of how to fix this problem-

Right-click on Network access icon>Internet settings

Connection> LAN settings

Check in the box ‘Automatically detect settings’

Press OK.

Hopefully, the concurrent error will be resolved. If in case it persists, then the following point description will resolve the issue.

Keeping browser and OS updated

An outdated or old browser, as well as Operating System (OS), can give rise to this error very frequently. If this is the cause of the problem, then the issue will be resolved most easily and quickly. One simply needs to update the OS or the browser or both. There are new patches given by the developers to rule out the existing updates. This is one of the reasons why the problem might arise. If one is facing such a problem with one OS/Browser or one version of any of these, one must consult others who use the same browsers/OS. If they are not facing the same problem, then it requires to be updated. And by updating, the issue will be resolved.

Certificates that are ‘Self-signed’ and different domains

This form of error happens when the assigned SSL certificate is allocated to a different domain name. Or the other possibility is that another self-signed certificate is attached to the browsed domain name. When it is a self-signed certificate, most of the time, it is used for internal-service. As most of the browsers do not approve self-signed certificates as ‘legitimate certificates’, it will reflect as an error. For this purpose, one needs to contact the developer for the installation of a new SSL on the domain instead of the removal of the SSL that is ‘self-signed’. This will be fixing the issue for certainty.

Anti-Virus/Firewall

This problem needs to be checked after the first time the error happens, along with the date and time settings. If the antivirus is blocking the applied SSL connection, In that case, uncheck the box in the setting that says ‘disabling HTTPS scanning in anti-virus’. If such an option is not found, one can turn off the software.

Clear data and Cache

If one is having a lot of browsing sites in the cache or have browsed to sites that use cookies, then it might get corrupted and cause an “err_cert_common_name_invalid” error. All one needs is to clear the cache by the following process.

CTRL+SHIFT+DEL from the Keyboard

Lead to a new page

Checking for ‘cookies & other site data’ and ‘cached files and images’.

Click clear data.

Now run the SSL and if the error was caused by this reason, it will be resolved.

Above are the simple most ways to guide the user to resolve this problem. If still there is a glitch that needs to be resolved, one can seek help from the network admin or the ISP. However, this is one of the most common problems that users face; there is nothing to be worried about or tensed about it. It is a resolvable issue.