Net err cert common name invalid как исправить

How to FIX ERR_CERT_COMMON_NAME_INVALID in Chrome

ERR_CERT_COMMON_NAME_INVALID is a very popular SSL error during loading the website. In most cases, the issue is due to certificate misconfiguration on a server. However, it may appear due to antivirus and firewall or another third-party extensions and software. Check the example of the error on the screenshot below.

Fixing the NET::ERR_CERT_COMMON_NAME_INVALID error is not very difficult, but would takes some time and extra steps. You have to start by identifying the cause of mismatch error first.

Solution 1: Check date and time are proper

Your Chrome browser will show ERR_CERT_COMMON_NAME_INVALID error in case the date and time are wrong on your computer or mobile device. Please recheck and adjust it on your via PC settings.

Solution 2: Check browser extensions

In some cases, the problematic browser extension could be a reason for the error. First of all, try to open the website in Incognito window and if that solves the issue then no need to check extensions. Otherwise, follow the next steps:

1. Click the «three dots» button on the top right corner of your browser window
2. Select More tools and Extensions
3. Turn off extensions one by one to find culprit extension and delete it to fix the browser error.

Solution 3: Check Installed SSL certificate

In most cases the issue comes from wrong SSL installed, it may simply not support the correct domain name or sub-domain. That makes a real mismatch result. For example, you issued and installed SSL for www.domain.tld, but installed it for sub.domain.tld which is not protected. You can check that with your browser.

In Chrome, you have to click to the «Not Secure» button located on the left side of the address bar, and then click to «Certificate». There you will see the details of SSL certificate using the field «issued to». The feature is available in most browsers.

You can also check that using Online SSL test by SSL Labs, that will be a more accurate result.

Solution 4: Protection of both with/without WWW

All Single Domain SSL certificates we sell protect WWW and non-WWW version of your domain name. However, there are some certs that do not protect it by default. In that case, you may have a problem using redirection from WWW to non-WWW or opposite option.

The possible solution is to install a proper SSL certificate or remove any redirect and install Multi-Domain, or Wildcard SSL or even multiple single-domain SSL to protect all domains/sub-domains in use.

Solution 5: For WordPress users

A very popular issue is forgetting to purchase an SSL certificate. WordPress owners enable secures HTTPS protocol for their website without installing or buying SSL, as result they get NET::ERR_CERT_COMMON_NAME_INVALID error message in the browser. There are two possible solutions in that case:

1. a purchase an SSL certificate and install it your web server;
2. or changing HTTPS back to HTTP to enable your website without any protection and encryption of transmitted data.

Solution 6: Clear the SSL cache

The browser’s SSL cache can be an issue. You have to try clearing the cache to resolve the error.

• For IE/Edge. You have to open the Internet properties and find the «Content» tab, there will be a button to «Clear SSL state».
• For Chrome browser the process is similar, click «Three dots» button on the top right side of the browser, find the «Settings». There you will find «Advanced settings» at the bottom of a page. Now find «Open Proxy Settings» and there you will see the «Content» tab with «Clear SSL state»

Solution 7: Proxy settings

You may have limited browsing experience if Automatical detection of settings is not set via proxy setup. The solution is a Right-click on the Network Access icon to see Internet Properties. Tap on the «Connection» tab and then to «LAN Settings».

You will see a new window where you have to click to checkbox near the «Automatically detect settings» if it is not checked already. Once done, you can retry opening the website to see if error was solved.

Solution 8: Update OS and Browser

The classical idea is to make sure your OS and Browser is Up to Date as old or outdated software may bring unexpected issues. The developers are working hard to create new patches and bug fixes, so that is critical to have an updated system.

Solution 9: Checking your Firewall/Antivirus

We suggest checking Firewall and Antivirus settings and LOG files to be sure they are not blocking the website you are trying to visit. Review the blocking reason carefully, if you found a block, as probably they are trying to secure you from a malicious website. We do not suggest switching off Antivirus.

Conclusions to summarize

You can clearly see that there are multiple possible issues that may bring you to error FIX ERR_CERT_COMMON_NAME_INVALID . However, it is known error and there are quite easy steps to fix the issue. Check data/time of your PC, browser extensions, try to clean SSL cache, recheck Proxy settings and update OS with Browser to latest versions. That should definitely help. Good luck!

NET::ERR_CERT_COMMON_NAME_INVALID: 10 Solutions to the Error

It is an important security practice to secure your website using HTTPS extension. However, an error message like NET::ERR_CERT_COMMON_NAME_INVALID may appear because of a wrong Secure Sockets Layer (SSL) certificate or browser configuration.

NET::ERR_CERT_COMMON_NAME_INVALID doesn’t prevent visitors from accessing a website. However, the error message will create a poor first impression since the browser will contain a warning that the site may steal users’ private information.

In this article we’ll explain what the NET::ERR_CERT_COMMON_NAME_INVALID error means, why it occurs, and walk you through ten methods to troubleshoot it.

What Is the NET::ERR_CERT_COMMON_NAME_INVALID Error?

Usually when accessing a website, the browser has to verify the website’s SSL certificate to establish a secure connection. A website with a valid certificate will redirect the request via the HTTPS protocol, the secure version of HTTP.

However, if the NET::ERR_CERT_COMMON_NAME_INVALID error occurs, it means the browser has failed to verify the SSL certificate. Most of the time, this happens because the common name which is written in the SSL certificate doesn’t match the actual domain name.

For example, if you want to install an SSL certificate on your website example.com, the common name should also be example.com.

Domain mismatch is not the only reason why the NET::ERR_CERT_COMMON_NAME_INVALID error occurs. In some instances, the issue may be caused by the site’s address itself and antivirus configuration settings, browser extensions, cache, and more.

Although this error can be tricky to troubleshoot since it has many possible causes, rest assured that there are ways to fix it quickly.

10 Methods to Fix NET::ERR_CERT_COMMON_NAME_INVALID

In this tutorial, we will explain ten methods to solve the NET::ERR_CERT_COMMON_NAME_INVALID error on your website. That said, before you proceed, make sure to check whether your site is inaccessible only for you or everyone else.

1. Make Sure That the SSL Is Set Correctly

A common cause of this error is a mismatch between the common name on your SSL certificate and the correct domain name. To solve the issue, make sure you have installed the correct certificate and configured the SSL properly.

We will show you a step-by-step guide to troubleshoot the error using Google Chrome. If you use a different browser, the process will be similar.

Here’s how to check the SSL certificate configuration:

1. Go to your website and click on the padlockicon on the address bar.
2. From the dropdown menu, select Connection is secure.

1. Select Certificate is valid.

1. A window will open containing the site’s SSL certificate details.

The actual domain name should match the common name listed in the SSL certificate’s Issued to domain information. If that isn’t the case, there is an SSL mismatch error between the two. The only solution is to delete and install a new SSL certificate.

Check Wildcard SSL Configuration

Wildcard SSL certificates can encrypt data on multiple subdomains. Therefore in some cases, the common name inside an SSL certificate is listed as a subdomain like domain.example.com.

If you use a wildcard certificate on your subdomain and encounter the NET::ERR_CERT_COMMON_NAME_INVALID error, it means that your SSL certificate doesn’t cover the subdomain you are trying to access.

Check Subject Alternative Names (SAN) Configuration

A Subject Alternative Names (SAN) certificate allows data encryption on multiple domains pointing to one site address. It covers www and non-www versions of a website, subdomains, and top-level domain (TLD) variations.

If the website you’re trying to access uses a SAN certificate, examine the list of domains it protects by checking the certificate details. If a web address is not there, the certificate doesn’t cover it.

2. Check WWW vs. Non-WWW Versions and If Your Site Is Redirecting to Another URL

It is important to know whether your browser or you are forcing your visitors to another version of your website since not all SSL certificates cover both www and non-www site versions.

For example, if your domain is mydomain.com, and the server redirects your website visitors to www.mydomain.com, the error may appear if there is only one SSL installed for the “www” version.

There are two ways to solve this problem. The first one is to change the common name on the certificate your domain defaults to. The second is to purchase another SSL certificate to cover the domain you’re redirecting from.

3. Ensure WordPress URL Is Directing to the Site URL

In some cases, the web protocol HTTP may have been manually changed to HTTPS without installing an SSL. As a result, the website may encounter a common name mismatch error.

If that’s the case, you should change your WordPress URL:

1. On the WordPress dashboard, click Settings and choose General.

1. Check whether the WordPress Address (URL) and Site Address (URL) match.

1. If they don’t match, make the appropriate changes.

4. Check for Any Browser Extension Conflicts

Having too many browser extensions can cause issues as they may conflict with one another. This may be a possible cause of the common name mismatch error.

Access the website in an incognito window and see if it is reachable. If it is, the problem might be caused by a browser extension. To solve this, disable the extensions one by one while checking your site to determine the cause of the issue. Once you’ve isolated the conflicting extension, delete it.

Here is how to remove extensions from Google Chrome:

1. Click the three dots at the top-right corner.
2. Hover over More tools and select Extensions.

1. Once the new window opens, select the extension you want to uninstall and click Remove.

To prevent this issue from happening in the future, make sure to audit and update your extensions regularly.

5. Clear the Browser Cache

Browser caching is a great feature that stores records of websites you’ve visited so the browser cloud load them faster the next time you visit that specific website.

Unfortunately, outdated cache may cause problems by loading an old version of a website. To prevent this, clear the browser cache regularly. This way, your browser will load the most recent version of the website and prevent the NET::ERR_CERT_COMMON_NAME_INVALID error from reoccurring.

6. Disable Antivirus Software and Firewall

Some antivirus software has an HTTPS scanning feature to add more protection. That said, it may block you from visiting HTTPS sites. If you trust the website, try disabling HTTPS scanning on your antivirus.

If this option is unavailable, you may have to entirely turn off the antivirus software.

Here’s how to disable Windows antivirus software:

1. Click on the Start button and look for Settings.
2. Find Update & Security and choose Windows Security.
3. Open Virus & threat protection and click Manage settings. Finally, switch Real-time protection to Off.

Here’s how to do it on macOS using ESET Endpoint Security:

1. Open Finder and look for the ESET Endpoint Security application.
2. Open the application and click Setup. Switch Real-time file system protection to Disabled.

7. Configure URL Settings In phpMyAdmin

The NET::ERR_CERT_COMMON_NAME_INVALID may be caused by the URL difference between option_value in siteurl and home rows of your website’s database. You can change your WordPress URL settings via phpMyAdmin.

Here’s how to do it via hPanel:

1. Go to your hosting account and open the phpMyAdmin application.
2. Choose your site’s database and find the wp_options table. Inside wp_options, look for siteurl and home rows. Make sure both redirect toward the same URL.

8. Clear the SSL State

When you access a website, the browser will cache its SSL certificate to speed up the load time the next time you visit. This may cause the NET::ERR_CERT_COMMON_NAME_INVALID error later.

This troubleshooting method involves clearing the SSL state in the browser and operating system. The process may differ depending on your operating system and browser.

Here’s how to clear the SSL state on Windows:

1. Navigate to Control Panel -> Network and Internet -> Internet Options.
2. The Internet Properties window will open. Click the Content tab and choose Clear SSL state.

You can also clear the SSL state on your browser. Here’s how to do it on Google Chrome:

1. Navigate to Settings after opening the three dots menu at the top-right corner.
2. Select Security and Privacy and click the Security option.
3. Scroll down and choose Manage certificates to see the list of SSL certificates cached by Google Chrome. Lastly, click Remove to clear the SSL state.

9. Change Your LAN Settings

Proxy settings route web traffic to protect users from malicious third parties. Any misconfiguration may restrict you from accessing websites or even cause SSL errors.

Here’s how to change the LAN settings on Windows:

1. Navigate to Control Panel -> Network and Internet -> Internet Options.
2. Choose the Connections tab and select LAN Settings.

1. Tick the Automatically detect settings option. Save the changes by clicking OK.

Here’s how to do it on macOS:

1. Open Apple menu, click System Preferences, and choose Network. Select a network service from the list and click Advanced. Finally, switch to the Proxies tab.
2. Tick Automatic proxy configuration and save the changes by clicking OK.

10. Update Your Operating System and Browser

It is crucial to update your applications and operating system regularly. Failure to do so can result in software instability, potentially leading to a lot of website errors.

Here’s how to check for Google Chrome updates:

1. Click the three dots at the top-right corner and hover over Help. Select About Google Chrome.
2. The Settings will open, letting you know whether an update is available. If it is, click Update Google Chrome. If you can’t see this button, it means you’re on the latest version.

Follow these steps to update Windows:

1. Go to Settings, then click Update & Security.
2. Choose Windows Update. The system will let you know whether an update is available. You can also manually Check for updates.

Here’s how to check for updates on macOS:

1. Open the Apple menu and select System Preferences.
2. Choose Software Update. Click Update Now if a new version of macOs is available.

How the NET::ERR_CERT_COMMON_NAME_INVALID Error Appears on Different Browsers

Depending on your browser, the common name mismatch error warning message may differ. In this section, we’ll take a look at what it looks like on several popular browsers.

Google Chrome

If you visit a website with an SSL error using Google Chrome, the browser will display the “Your connection is not private” message with NET::ERR_CERT_COMMON_NAME_INVALID under it. Google Chrome also warns visitors that attackers might steal their information through the website.

Google Chrome will recommend users to get Back to safety. That said, it’s still possible to visit the website by clicking on Advanced and choosing to Proceed to the website.

Microsoft Edge

If you encounter the NET::ERR_CERT_COMMON_NAME_INVALID error on Microsoft Edge, you’ll see the “Your connection isn’t private” message along with a warning that accessing the website might invite attackers to steal your personal information.

You will be able to choose whether to Go Back or visit the website by choosing Advanced.

Mozilla Firefox

Mozilla Firefox displays a unique version of the NET::ERR_CERT_COMMON_NAME_INVALID error message. It says “Warning: Potential Security Risk Ahead” and warns the visitor that the browser has detected a potential security threat and did not continue to the website.

Firefox doesn’t indicate the code for the common name mismatch error. Instead, it informs visitors what happened in detail, mentions that the issue is most likely with the website, and provides solutions to the problem.

Opera

When you encounter the common name mismatch error using Opera, the browser displays a similar warning message to Google Chrome and warns you that attackers may be trying to steal your personal information.

The Help me understand button describes why Opera doesn’t let visitors access the website. It says the browser doesn’t trust the SSL certificate used on the website.

Internet Explorer

Internet Explorer keeps its NET::ERR_CERT_COMMON_NAME_INVALID error message simple by stating “This site is not secure” and explaining that someone might be trying to fool the visitor or steal their info. It then warns the user to close the site immediately.

Internet Explorer users can choose to Close this tab or see More information. If you select More information, the browser explains that it doesn’t trust this website’s SSL certificate and displays the error code DLG_FLAGS_INVALID_CADLG_FLAGS_SEC_CERT_CN_INVALID.

Find out the ways to solve other errors similar to NET::ERR_CERT_COMMON_NAME_INVALID

Conclusion

SSL is an essential part of a website that is dedicated to protecting users’ data via encryption methods. However, if you’ve misconfigured the SSL settings, you may encounter an error such as NET::ERR_CERT_COMMON_NAME_INVALID.

Dealing with the common name mismatch error can be tricky, but there are many methods to solve it quickly – this tutorial has discussed ten of them. The solutions involve changing the SSL configuration, URL redirection, advanced browser settings, and proxy settings.

We hope this article has helped you troubleshoot the common name mismatch issues. If you have questions or tips, feel free to leave a comment below.

NETT::ERR_CERT_COMMON_NAME_INVALID FAQs

Here are some frequently asked questions about the error.

What Causes NET:ERR_CERT_COMMON_NAME_INVALID?

NET:ERR_CERT_COMMON_NAME_INVALID is a certificate error that occurs when the SSL/TLS certificate presented by a website is not issued for the specific domain or subdomain that the user is attempting to access. This can be caused by a misconfigured certificate or a mismatch between the certificate and the website’s hostname.

How Do I Prevent NET:ERR_CERT_COMMON_NAME_INVALID?

To prevent NET:ERR_CERT_COMMON_NAME_INVALID, ensure that the SSL/TLS certificate presented by the website is valid, issued for the correct hostname, and issued by a trusted Certificate Authority. Ensure that the website’s hostname matches the name on the certificate. Avoid accessing websites that trigger SSL warnings or errors.

What Are the Consequences of NET:ERR_CERT_COMMON_NAME_INVALID?

The consequences of NET:ERR_CERT_COMMON_NAME_INVALID can include an inability to access the website, loss of sensitive data, and exposure to security risks. Users may also experience degraded website performance, slow page load times, and increased vulnerability to phishing attacks and malware infections.

Noviantika is a web development enthusiast with customer obsession at heart. Linux commands and web hosting are like music to her ears. When she’s not writing, Noviantika likes to snuggle with her cats and brew some coffee.

Исправление ошибки NET ERR CERT COMMON NAME INVALID

После длительного использования браузера без каких-либо серьезных проблем может возникнуть ситуация, когда веб-обозреватель выдаст ошибку: err cert common name invalid или «Ваше подключение не защищено».

Чаще всего с ней сталкиваются пользователи Google Chrome и Яндекс браузера, но не стоит исключать появление и в других веб-обозревателях. На, то есть множество программных причин, как со стороны сервера, на котором расположен запрашиваемый сайт, так и на стороне компьютера. Рассмотрим каждую из них и самостоятельно исправим сбой.

Неверно установленное системное время

Убедитесь, что на компьютере верно установлено системное время. Сверьте его со своими часами или через интернет, и при необходимости внесите изменения.

1. Если у вас неправильно выставлено время и дата, тогда вам необходимо кликнуть правой мышкой по виджету времени, расположенном в нижней части экрана и выбрать раздел с названием «Настройка даты».
2. Введите текущую дату и время, после чего сохраните изменения.
3. Проверьте результат, повторно посетив нужный интернет – ресурс.

Когда настройки времени и даты сбиваются автоматически после перезагрузки компьютера, говорит о севшей батарейке BIOS «CR2032». Этот питательный элемент находится на материнской плате и его нужно заменить.

Дополнительные модули блокирующие интернет-ресурсы

Некоторые пользователи для безопасности устанавливают антивирусные программы и защитное ПО. В большинстве случаев они имеют дополнительные модули, которые автоматически интегрируются в браузер в процессе установки. Это может стать причиной возникновения ошибки net err cert common name invalid.

1. В качестве решения предлагаю войти в раздел «Дополнительных инструментов» – «Расширения» через меню браузера.
2. В списке найдите элементы, относящиеся к защитному ПО, и отключите их.
3. Дополнительно можно деактивировать и другие лишние дополнения.

Если установлены блокировщики рекламы, такие как «Adblock» и «Adguard», то отключите их, поскольку они способны нарушать работу сайтов.

Блокировка интернет — ресурса защитными программами

Возможно, проблема кроется в основной защитной программе, блокирующей доступ к определенным ресурсам.

1. Проверьте это, временно отключив антивирус или встроенный в Windows защитник. При положительном результате, вновь включите защитное ПО и внесите нужный сайт в список исключений.
2. Некоторые антивирусы оснащены функцией проверки HTTPS трафика, что также способно вызывать сбои. Отключается данная опция через панель настроек. Например, в «Dr.Web» функция фильтрации безопасного трафика находится в разделе «Сеть».

Однако, насовсем отключать проверку зашифрованного соединения не рекомендуется. Если разработчики антивируса предлагают другие способы решения, например, ручную установку сертификата, то стоит ими воспользоваться.

Не установлен корневой сертификат

Также ошибка «err cert common name invalid» возникает из-за отсутствия в браузере корневого сертификата. Исправить ее можно установкой сертификата «GeoTrust Primary Certification Authority» с расширением (.crt), предварительно скачанного с интернета

1. По окончанию загрузки запустите файл и выберите «Установить сертификат».
2. Отметьте «Текущего пользователя».
3. В качестве хранилища укажите «Доверенные корневые центры сертификации». Нажмите «Ок», а затем «Далее».
4. Подтвердите установку кнопкой «Готово».

После того как вы произвели импорт сертификата, перезагрузите компьютер или ноутбук и проверьте, устранен ли сбой.

Очистка SSL

Если проблема связана с SSL сертификатом на вашем компьютере, то очистка SSL кэша решит ее.

1. Войдите в «Панель управления» через «Пуск» или «Поиск».
2. В верхнем правом углу выставите опцию «Мелких значков».
3. Перейдите в подраздел «Свойства браузера».
4. Переместитесь в «Содержание» и щелкните по кнопке очистки.

Отключение прокси и VPN

Пользователи или некоторые приложения могут внести изменения в настройки интернет-подключения, что может вызвать определенные неполадки.

Как это проверить и исправить:

1. Через меню браузера откройте панель настроек и найдите пункт, отвечающий за работу прокси-сервера.
2. Откроется окно конфигурации, в котором необходимо выставить функцию автоматического определения параметров и деактивировать опцию прокси-сервера.

Подождите несколько минут, пока восстановится нормальная работа интернет-подключения, после чего проверьте результат.

Очистка кэша и сброс сетевых параметров

Возможно, ошибка net err cert common name invalid уже исправлена, но сайты по-прежнему не открываются из-за устаревших данных в кэше. Тогда необходимо его почистить.

Как это сделать:

1. Войдите в браузер и с помощью нажатия клавиш «SHIFT+CTRL+DELETE» вызовите окно очистки.
2. Отметьте имеющиеся пункты, обозначьте «Все время» и нажмите «Удалить».
3. Перезапустите веб-обозреватель. Дополнительно рекомендуется использовать программу для очистки других устаревших данных, например, «Ccleaner».
4. Запустите командную строку. Найти ее можно через панель «Пуск» или «Поиск».
5. Введите в консоли ipconfig /flushdns и нажмите «Enter». Следом за ней выполните команду netsh winsock reset, после нее netsh int ip reset c:\resetlog.txt и в конце netsh winhttp reset proxy.

Остается перезагрузить компьютер вместе с маршрутизатором.

Смена стандартных DNS серверов

Как ни странно, но DNS сервера, предоставляемые провайдером не очень надежны. Поэтому, желательно их изменить.

1. Нажатием клавиш «Windows» + «R» вызываете окно выполнения команд.
2. Вводите фразу ncpa.cpl и жмете «Ок».
3. Заходите в свойства текущего интернет-соединения.
4. Выбираете протокол «IPv4» и открываете «Свойства».
5. Активируйте пункт использования DNS серверов. В первую строку введите цифры «8.8.8.8» и во вторую «8.8.4.4». Сохраните изменения, щелкнув «Ок».

Проблема должна исчезнуть.

Устаревшее ПО или операционная система

Некоторые пользователи до сих пор используют в своей работе Windows XP. Однако, она давно не поддерживается и если железо позволяет, то лучше установить Windows 7 или 10. Тем не менее, если вы, всё же хотите пользоваться операционной Windows XP, тогда установите последнее обновление SP3.

Такой же подход касается и веб-браузеров. Вероятность появления рассматриваемой ошибки в последних версиях популярных обозревателей меньше, по сравнению с их более ранними версиями.

Новые версии популярных браузеров не устанавливаются на Windows XP, за исключением Mozilla FireFox и Яндекс браузера.

Проблемы на стороне сайта

Владельцы интернет — ресурсов могут неправильно установить SSL сертификат или его настроить. Поэтому вам необходимо убедиться в том, что неисправен именно сайт.

Для этого попробуйте открыть сайт с другого устройства, например, смартфона, планшета или ноутбука. А еще лучше если воспользуетесь другим провайдером или мобильным интернетом. Если это не поможет избавиться от err cert common name invalid, то скорее всего неисправен сайт. В этом случае решить проблему самостоятельно не получится и нужно будет дождаться того момента времени, когда владельцы сайта восстановят его работу.

Панель общего доступа

Проверьте правильность настроек в панели общего доступа.

1. В панели задач найдите иконку с изображением компьютера, вызовите дополнительное меню нажав по ней правой мышкой, откройте параметры сети и интернета.
2. Переместитесь в раздел общего доступа.
3. У текущего профиля отключите сетевое обнаружение и общий доступ к файлам.
4. Разверните пункт «Все сети», активируйте 128-битное шифрование, доступ по паролю и сохраните изменения.

После перезагрузки компьютера, работоспособность интернет – ресурсов должна восстановиться.

Другие случаи и способы решения проблемы

1. Если вы используете Google Chrome на смартфоне, работающем под управлением ОС Android и у вас появляется ошибка net err cert common name invalid, можно попытаться исправить ситуацию следующим образом: Войдите в раздел «Настройки» и выберите в нём подраздел «Конфиденциальность». Далее нажмите по пункту «Очистить историю» и «Удалить данные».
2. Если неполадка возникает только в одном веб-обозревателе, то скорее всего дело в его настройках. Проще всего выполнить сброс параметров к значениям по умолчанию. Найти эту функцию можно через «Меню» — «Настройки», воспользовавшись поисковой строкой.
3. Попробуйте зайти на сайт через поисковик Google, Яндекс, вбив его название или адрес в строку поиска.
4. Проверьте устройство на наличие вредоносных программ, в том числе через утилиту «Adwcleaner».
5. Полностью удалите веб-обозреватель через специальные деинсталляторы «Your / Revo Uninstaller», произведите очистку системы используя «CCleaner», а затем выполните повторную установку.
6. Избавьтесь от лишних программ, поскольку некоторые из них могут влиять на работоспособность компьютера. К таким приложениям можно отнести различные бары, например, «Research bar».
7. Установите обновление «KB4474419» через «Центр обновления Windows».
8. Крайним вариантом станет добавление параметра -ignore-certificate-errors в конец поля «Объект», после закрывающейся кавычки в свойствах ярлыка браузера.
9. Сбросьте настройки маршрутизатора. Для этого на задней панели предусмотрена кнопка «Reset».
10. Если не работают все ресурсы, то скорее всего дело в нестабильном интернет-подключении. Читайте подробнее о том, как самостоятельно проверить качество интернет-соединения через доставку сетевых пакетов. При выявлении сбоев, обязательно свяжитесь с вашим провайдером.

В заключение стоит отметить, что были разобраны основные способы устранения неполадки, но возможно, далеко не все. Пишите в комментариях о том, что помогло, а что нет. Постараюсь помочь.

How to Fix – NET::ERR_CERT_COMMON_NAME_INVALID in Chrome

NET::ERR_CERT_COMMON_NAME_INVALID is an SSL certificate error. In this era where cyber-crime is on the rise, Google loves to provide a secure environment for its users, and so do its browsers. This error is shown by the Chrome browser when a user or a website owner tries to load a website.

SSL certificate errors can be confusing, and being a website owner, these errors can impact your sales figures, network traffic as well as your site reputation. Hence it is essential to take preventive measures to get rid of the error.

But, before moving to the solutions to resolve this error, let’s check out why this error occurs.

Table of Contents

# Causes of ERR_CERT_COMMON_NAME_INVALID Error

The red triangle shown in the image is a warning signal that the site you are trying to access is risky. But this error may appear on genuine and known websites too.

The “Common Name” mentioned in the above error cites the domain name required for certificate issuance. There are multiple reasons which cause this error.

Example: If your website name is www.mysite.com, for which you require an SSL certificate, your CSR (Certificate Signing Request) will display the site name as the common name.

Net::Err_Cert_Common_Name_Invalid warning is displayed by the browser when a mismatch occurs between the common name mentioned in the SSL certificate and the one mentioned in the URL. This error also appears when the SSL certificate fails to display the domain name in any form, i.e., common name, wildcard SSL, or SAN (Subject Alternative Name). Such mistakes can lead to this error.

Few more Reasons for Causing this Error:

• Misconfiguration of SSL certificate on the server
• SSL certificate has expired
• SSL securities are clashing with firewalls or another anti-virus software
• Browser extensions may cause this error

Now that there is some clarity about why this error is displayed, you need not panic because this error can be resolved with simple solutions. Let’s start.

# Solutions to Fix this Error:

1. Start from the Basics:

Minor issues can sometimes create significant problems. Something as small as an incorrect date and time on your PC or laptop can trigger this error. Did you check if both these options are correct or not? If incorrect, rectify them, and resolve your error.

2. Look for Problems in your Browser Extensions:

Though web browsers play a small role in protecting your website data, they act as the first line of defense against cyber-attacks. Browser extensions are small software that prevents the entrance of malicious sites and emails by filtering content and data.

But these browser extensions may sometimes cause problems with the SSL certificate security.

Solution:

• Enable the Incognito mode by opening the Chrome app.
• Go to the right of the address bar > click More > New Incognito Tab
• In the new window, open the Incognito icon.

If you don’t run across any errors while opening the Incognito icon, there may be a browser extension problem. Go to Chrome://extensions/, deactivate all extensions, and later activate one by one to find the extension creating the problem. Disable the same or remove it if unnecessary.

3. Clear Cache and Data:

Browser Cache and Cookies may disrupt the smooth functioning of a website.

Click Ctrl + Shift + Delete keys, and a new page will appear. Click all the options as shown in the below image and later click “Clear Data.”

Check for error resolve after completing the process.

4. Clear SSL Common Name Mismatch Error:

As specified earlier, domain name mismatch error in the SSL certificate is one of the reasons which may cause this error. The SSL certificate is either installed on the wrong site, or the domain name is not matching the site URL mentioned in the address bar.

Re-confirm the domain information in the SSL certificate by checking the “Issued to” field in the Certificate details. You can also re-check the same by using the Online SSL test – by SSL Labs for better results.

5. Verify the Site Address:

When installed on a site, an SSL certificate shows the URL starting from HTTPS instead of HTTP. But if your website does not have an SSL certificate installed and begins with HTTPS, it may display this error.

Verify the site address and change it according to the site protocol to eliminate the error.

6. Check if Your browser is Redirecting Visitors to Your Other Website Version:

Misconfigured redirects can display an error message, and it is necessary to alter the settings to stop these redirects.

Process:

• Go to Chrome browser > Click on three dots on the upper-right hand corner > Go to Settings > Click Advanced.

• Go to Privacy & Security Section > go to Content Settings > go to Pop Ups and Redirects.

• Ensure that the “Blocked (Recommended) feature is active.

7. Check for WWW vs. Non-WWW:

It is essential to keep a check on the Chrome redirects to ensure that errors don’t appear. If Google Chrome forcefully redirects your site visitors from the WWW version to the non-WWW version of your website, you are bound to face Err_Cert_Common_Name_Invalid error.

Since all SSL certificates don’t cover both versions, it is better to purchase an SSL certificate that takes care of both these versions to avoid future errors.

You can reconfigure your settings by banishing the redirect. If it is essential, buy another SSL certificate, which covers the site’s domain name to which your network traffic is redirected.

Example: Multi-Domain Wildcard SSL certificate secures many domains and subdomains in a single certificate.

8. Clear SSL Cache:

SSL Cache can sometimes interfere with the security certificate, causing an invalid name error. Even some expired data in the cache can trigger this error.

The Process to Clear SSL Cache:

• Click three buttons on the top right-hand corner of Chrome browser and go to Settings > Advanced Settings.
• Open “Proxy Settings > Internet Properties > Content.
• Click “Clear SSL State” and click Ok.

9. Set Your Proxy Settings to Detect Settings Automatically:

Your proxy settings must be set to “Automatically Detect Settings” to give you a better browsing experience. If that is not the case, then your browsing experience is bound to be limited, and you may end up facing an error.

Solution:

Go to Network Access Icon and Right-click it. “Internet Properties” menu will appear.

Go to Connections > Click LAN Settings. In LAN Settings, tick “Automatically Detect Settings” if it is unticked. Re-open the website and check the error.

10. Disable Antivirus or Firewall:

Securities sometimes clash up with each other and display various error messages. Especially anti-virus software and firewalls are heard messing up with SSL encryption securities to show the above error.

The best solution is to disable both these securities temporarily and check if the error is resolved or not. Later you can enable the same to secure your site.

11. Upgrade to the Latest Operating System & Chrome Browser:

Outdated versions or old versions of any digital infrastructure are risky because they have security bugs. They tend to miss out on the latest security patches since they are not upgraded.

The same is valid for operating systems and browsers which pose a threat to your business website. Hence keep them updated regularly to keep your website error-free and safe from cyber-attacks.

Final Thoughts:

Websites are the largest informative sources for customers. When these sites make information inaccessible due to errors, it not only disappoints customers but also drives them away from your site. Hence it is essential that your website’s functioning is smooth and hassle-free for increasing the network traffic of your site and business.

Resolving Net::Err_Cert_Common_Name_Invalid error is just a couple of mouse clicks away, and I hope the above solutions will help you in fixing your problem.