Using the HTTPS extension to encrypt your website is an important security practice. However, an incorrect Secure Sockets Layer (SSL) certificate or browser setup may result in an error message such as NET::ERR_CERT_COMMON_NAME_INVALID.
This error does not prevent access to a website. Although the browser will have a warning that the site may steal visitors’ personal information, the error message will create an initial negative impression.
What is the NET::ERR_CERT_COMMON_NAME_INVALID error?
To create a secure connection when visiting a website, the browser usually needs to confirm the website’s SSL certificate. The request will be forwarded over the secure HTTPS protocol by the website that has a valid certificate.
The NET::ERR_CERT_COMMON_NAME_INVALID error indicates that the browser did not successfully check the SSL certificate. Most of the time, this happens because the common name of the SSL certificate does not match the actual domain name.
For example, if you want to install an SSL certificate on the example.com website, the common name must be example.com.
Not all reasons for this error include domain mismatch. In some cases, the site’s original address, antivirus protection options, browser add-ons, caching, and more may cause problems.
While there are many possible explanations for this problem, it’s easy to fix quickly.
Ten practical ways to fix err_cert_common_name_invalid error
As mentioned earlier, the causes of the err_cert_common_name_invalid error are different. Consequently, there are several possible solutions. Here are 10 methods you can use to solve this problem on your website.
Here are 10 methods you can use to solve this problem on your website
Check if your SSL certificate is correct.
A frequent cause of this error is a difference between the common name of your SSL certificate and the valid domain name. Make sure the relevant certificate is installed, and SSL is set up correctly to resolve the issue.
The SSL certificate configuration can be checked as follows:
- Click the padlock icon in your website’s address bar.
- A safer option is to select Connect from the dropdown menu.
- Please select the valid certificate.
- The SSL certificate information for the website will be displayed in a new window.
The common name mentioned in the SSL certificates issued in the domain information should match the original domain name. If not, then there is an SSL mismatch issue between the two.
The only solution is to remove the SSL certificate and replace it with a new one.
Also, check your wildcard SSL server configuration. Wildcard data in numerous subdomains can be encrypted with SSL certificates. As a result, the common name of an SSL certificate may sometimes be listed as a subdomain such as domain.example.com
The error err_cert_common_name_invalid indicates that your SSL certificate does not cover the subdomain you are trying to visit if you use a wildcard certificate in your subdomain.
Be sure to check the Subject Alternative Names (SAN) configuration. An SSL certificate with Subject Alternative Names (SAN) support enables data encryption across multiple domains pointing to the same website address.
It covers a website’s top-level domain (TLD) variations, subdomains, and www and non-www versions. If the website you’re trying to visit uses a SAN certificate, check the certificate details to see what domains it protects. If a web address is missing then the certificate is not valid.
Check for misconfigured redirects
Since not all SSL certificates support www and non-www site versions, it is important to understand if your browser directs users to a different version of your website. If there is only one SSL setup for the “www” version, the problem may occur if your domain is mydomain.com and the server directs website visitors to www.mydomain.com.
There are two different ways to fix the err_cert_common_name_invalid error in this situation. The first step is to change the common name that appears by default on your domain certificate.
A second option is to get an additional SSL certificate to cover the domain you redirect traffic from.
Make sure your site and WordPress addresses are identical
Without an SSL installed, the HTTP web protocol can sometimes be manually changed to HTTPS. This is a common cause of err_cert_common_name_invalid error. If so, you need to change your WordPress URL by following these steps:
Click Settings in the WordPress dashboard and select General. Verify that the site address (URL) and WordPress address (URL) are the same.
If they do not line up, make necessary adjustments.
Check for conflicts between browser extensions
Many browser extensions can conflict with each other, which can cause of err_cert_common_name_invalid error. Check whether the website is accessible by opening it in a private window. If so, a browser extension may be responsible for the problem.
Disable extensions one at a time to find the root of the problem while investigating your website To fix the err_cert_common_name_invalid error remove the conflicting extension after you identify it.
Follow these steps to delete extensions from Google Chrome:
- In the top-right corner, click on the three dots.
- Navigate to More Tools and select Extensions
- Select the extension you want to remove and click Remove in the new window that appears.
Make sure to continuously audit and update existing extensions to avoid this issue in the future.
Disable your firewall and antivirus software
Some antivirus programs offer an HTTPS scanning option to provide extra security. However, it may prevent you from accessing HTTPS websites. If you trust the website, try disabling HTTPS scanning in your antivirus software If this option is unavailable, you may need to disable the antivirus program.
To turn off Windows antivirus software, follow these steps:
- Find Settings by clicking the Start button.
- Select Windows Security under Update and Security.
- To manage settings, click Virus and threat protection and then Open Then, turn off real-time protection.
Here’s how to use ESET Endpoint Security on macOS:
- Find the ESET Endpoint Security program by opening the Finder.
- Launch the program, then select Setup. Turn off real-time file system protection.
Naturally, you should not disable your antivirus program for long periods of time as doing so puts your security at risk.
Hence, it is recommended to restart it while waiting for help from the antivirus support team and follow their instructions to fix the error while keeping your computer safe.
Clear your browser’s cache
Browser caching is a great feature that keeps track of the websites you visit. So, if you next time visit that particular website, the browser will load faster. Unfortunately, an older version of a website may load if an old cache is present.
Clean and Clear the browser cache frequently to avoid this problem. Doing this will ensure that your browser is loading the most recent website version and avoid getting the err_cert_common_name_invalid error.
Update your operating system and browser
While trying to access certain websites, err_cert_common_name_invalid causes can be an outdated OS. For this reason, you should make sure that you are using the latest version of Linux, macOS, or Windows.
In addition, you should ensure your browser is current. To do this open the Settings menu in Chrome and select Help > About Google Chrome. You can check your browser version and enable automatic updates Opening this screen should trigger an automatic upgrade if Chrome is older.
Clear the SSL status
When you visit a website, your browser will save the SSL certificate from increasing the subsequent load speed. Later, this may result in an err_cert_common_name_invalid error. Clearing SSL status in the browser and operating system is one way to fix the err_cert_common_name_invalid error.
Depending on your operating system and browser, the method may differ. Here’s how to reset the SSL state in Windows:
- To access the Internet options, go to the Control Panel > Network and Internet.
- This will display the Internet Properties window. Under the Contents tab select Clear SSL Status.
- From the three-dot menu in the top-right corner, go to Settings.
- After choosing Security and Privacy, click on Security Options.
- To see the list of SSL certificates cached by Google Chrome, scroll down and select Manage Certificates.
- Finally, click Remove to remove the SSL status.
Change your LAN settings
Web traffic is routed through proxies to protect users from malicious outsiders. Any setting issues may prevent you from visiting the website or cause SSL failure.
Here’s how to change LAN settings in Windows:
- To access Internet Options, go to Control Panel > Network and Internet.
- Select LAN Settings under the Connections tab.
- Select the option of “Automatically detect settings”.
- By selecting OK, the changes are saved.
On macOS, follow these instructions:
- Select the Network under System Preferences in the Apple menu.
- Click Advanced after selecting a network service from the list.
- Select the Proxy tab.
- Select Automatic proxy configuration.
- Finally, click OK to save your settings.
Configure URL settings in phpMyAdmin
You want to restore the access to your dashboard after changing the address in the WordPress settings section without using the secure version (HTTPS). Most of the time, you can not even access the login page. This is the worst-case scenario for beginners; Thus, it’s time to mess with your hosting files.
A difference in the URL between the alternate value of the site URL and the home rows of your website’s database can be a cause of the err_cert_common_name_invalid error.
Through phpMyAdmin, you can change WordPress URL settings. For hPanel, follow these instructions:
- Open the phpMyAdmin program by logging into your hosting account.
- Locate the wp_options table in your website’s database.
- Find the site and home row in wp_options. Make sure they both lead to the same URL.
If there is a different address between these two categories, your site will generate an error notification Simply put, the web address of both locations must match. This is a different location where you can indirectly access the settings and change the address if you accidentally change the URL in the WordPress settings area. Buy WordPress Hosting from Oudel Inc.
If you want your website to use a secure protocol and have a valid SSL certificate, you can switch to HTTPS In the meantime, until SSL is installed, you must switch from HTTPS to HTTP if you do not currently have SSL and see privacy errors.
Once you’ve modified the URL, be sure to save your changes After making changes to fix the err_cert_common_name_invalid error, check that your site is reflected correctly by accessing the URL in Chrome’s incognito window.
Conclusion
Even if you have a wealth of information on your website, it is useless if it is not accessible. Additionally, a bad website can damage your business’s standing and alienate customers. Resolving err_cert_common_name_invalid errors can be challenging. However, if you can identify the root cause of the problem, you can quickly fix it and restore the trust of your site visitors.
As a first step to fix the err_cert_common_name_invalid error we recommend checking the SSL certificate in your browser and scanning for any incorrect redirects. If those don’t work, start looking at all the other reasons we’ve mentioned in this guide.
