While each Chrome update resolves known bugs in the browser, it can also introduce new issues if things don’t go as they should. Other problems may also arise from various extensions installed in your browser, too. These issues include the most common error users often stumble on their browser: ERR_CERT_COMMON_NAME_INVALID.

This common error is type of SSL error that shows up in many other platforms and is due to a server misconfiguration of the website you are visiting, a bug in Chrome, firewall issues, or third-party extensions. The issue displays the following message:

Your connection is not private.

In this post, we try to provide the solution to this kind of bug. First off, ensure that the settings for date, time, and location of your Windows PC are accurate by selecting Control Panel > Clock, Language, and Region.


  1. Identify problematic extensions
  2. Check proxy settings
  3. Clear cache and data
  4. Disable your antivirus or firewall
  5. Clean your SSL cache
  6. Update your Chrome
  7. Reinstall Chrome

Solution 1 – Identify problematic extensions

Scout for the extensions or plugins that may be causing the problem. To determine that an extension is causing the trouble, browse in incognito mode first and see if everything is fine. If you don’t see the error message in incognito mode, then an extension might be the culprit.

To identify the problematic extension, first disable all the plugins in your Chrome browser by unchecking the box to their right. Then enable one extension at a time and visit any site to see if the error message still appears. Repeat this step for the rest of the extensions until you find the culprit. Remove the extension that’s causing the problem by hitting the trash bin icon to the right.

Solution 2 – Check proxy settings

Proxy settings can also affect how your browser works. A small error in configuration is enough to cause problems with browsing, such as limited access to any site. To check if the proxy settings on your PC are correct, follow these steps:

  1. Launch the Start menu and type inetcpl.cpl in the Search box to open Internet Properties
  2. Go to the Connections tab.
  3. Then select Settings and make sure that Automatically detect settings is checked and nothing else.
  4. Hit OK.

Now check if the error is gone after correcting your proxy settings.

Solution 3 – Clear cache and data

Corrupted cache and cookie can sometimes generate problems in Chrome. Clearing them might be of help. Here is how:

  1. Press CTRL + H on your keyboard.
  2. Select Clear Browsing Data.
  3. Check relevant options for cache, cookies, content license, hosted app data.
  4. Then click Clear browsing data.

Solution 4 – Disable your antivirus or firewall

Antivirus programs and firewall applications are also among the culprits for the errors in your browser. This results in SSL issues that will limit your browsing. You may choose to disable security applications in the interim and check if it solves the issue.

Solution 5 – Clean your SSL cache

If the above method does not help, clear the SSL cache to fix the err_cert_common_name_invalid error. Here is how:

  1. Open Internet Properties and go to Content tab.
  2. Then, select Clear SSL State.
  3. To do it on your browser, go to Settings > Show Advanced Settings > Change Proxy Settings.
  4. Select the Content tab.

Solution 6 – Update your Chrome

Also, make sure that your Chrome browser is up-to-date. Outdated applications are a fountain of various problems. Just open Chrome > 3-dot menu > About Google Chrome and update it.

Solution 7 – Reinstall Chrome

In the end, you can also try reinstalling the Chrome. This should resolve possible issues and get you in the clear. Of course, don’t forget to backup your bookmarks and passwords. Just open Control Panel > Uninstall a program. Uninstall the Chrome and delete associated files. You can do it manually or use a third-party uninstaller.

If you know of any other method to fix the ERR_CERT_COMMON_NAME_INVALID issue in Chrome, share them with us in the comment section below!

Editor’s Note: This post was originally published in May 2017 and has been since completely revamped and updated for freshness, accuracy, and comprehensiveness.