ERR_CERT_COMMON_NAME_INVALID Error Resolution Methods 2019

ERR_CERT_COMMON_NAME_INVALID Error Resolution Methods 2019

ERR_CERT_COMMON_NAME_INVALIDSometimes Chrome gives the message “ERR_CERT_COMMON_NAME_INVALID” when you want to browse the site?

Because of this, it is impossible to visit the resource, because this error is related to failures of the SSL / TSL certificate, which guarantees secure browsing.

The most common causes of errors are as follows:

On the server side, the security certificate is incorrectly configured — for example, and the subjectAlternativeName extension is not tied to a certificate;

In the user device, incorrect network settings, time, date, time zone;

addition to Chrome interferes with the operation of the SSL / TSL certificate

The content of the article

How to fix ERR_CERT_COMMON_NAME_INVALID error?

No. 1: fighting the buggy Chrome extension

No 2: we check the work of the antivirus or firewall

No. 3: clearing the cache

No 4: contact the site administrator

No. 5: disable security warnings

No. 6: Check if the incognito error occurs

No. 7: Check date and time

How to fix ERR_CERT_COMMON_NAME_INVALID error?

Ensure that the time, date, and time zone are correct on the device. Still, try to visit the site in incognito mode – often this happens without warning about the security of the connection.

No 1: fighting the buggy Chrome extension

If the error ERR_CERT_COMMON_NAME_INVALID does not appear in incognito mode, but it occurs during standard viewing, then it is still unknown what Chrome add-on is. The problem is solved as follows:

  • go to the browser settings: “Additional Tools” => “Extensions” and turn off all add-ons;
  • include one extension and update each time the page on which a security warning was issued before;
  • repeat the cycle until you find an add-on that, when activated, generates an error;
  • remove the buggy extension – almost always there is the same functionality.

No 2: we check the work of the antivirus or firewall

Turn off the antivirus or firewall and update the page. If the attempt is successful, then the root of the problem is in the antivirus software.

In order not to reduce the security of browsing, it is worth including the https scan option in the antivirus or firewall.

No 3: clearing the cache

  • Press Ctrl + Shift + Del while Chrome is running – a window for deleting user data will open. You can also call it from the “Additional Tools” => “Clear History” menu.
  • Delete only “cookies” and “files stored in the cache.” Make sure that the top of the window is selected all the time, not just the last day.



No 4: contact the site administrator

Sometimes only a resource manager can solve a problem. Report an error. He could have installed the SSL certificate incorrectly and preferred that he create a new one.

No. 5: disable security warnings

This is an extreme measure, since only the consequence of the inconsistency is eliminated, but not the reason. However, the ERR_CERT_COMMON_NAME_INVALID error will not appear when security notifications are disabled.

No. 6: Check if the incognito error occurs

Regardless of whether the ERR_CERT_COMMON_NAME_INVALID (ERR_CERT_AUTHORITY_INVALID) error occurred on Windows or on Android.

Try opening a new window in incognito mode (this item is in the Google Chrome menu) and check if the same site is open, where you normally see the error message.

If it opens and everything works, then try the following options:

  • On Windows, first, disable all (including those you trust) the extension in Chrome (menu – additional tools – extensions) and restart the browser (if it worked – then you can find out which extension caused the problem, including one by one). If this does not help, then try to reset the browser (settings – show advanced settings – button “Reset settings” at the bottom of the page).

 

  • In Chrome on Android, go to Android Settings – Applications, select there Google Chrome – Storage (if there is such an item), and click the “Erase data” and “Clear cache” buttons. Then check if the problem has been solved.

Most often, after the described actions, you will no longer see messages that your connection is not secure, but if nothing has changed, try the following methods.

No. 7: Check date and time

Previously, the most frequent cause of the error was the incorrect date and time set on the computer (for example, if you reset the time on the computer and do not synchronize with the Internet).

However, now Google Chrome gives a separate error “The clock is lagging behind” (ERR_CERT_DATE_INVALID).

However, just in case, check that the date and time on your device match the actual date and time according to your time zone.

And If they are different, correct or enable the automatic setting of the date and time (applies equally to Windows and Android).

 

Leave a Comment