Err ssl protocol error что это

ERR_SSL_PROTOCOL_ERROR: What It Is and 3 Effective Ways to Repair It

Many Internet users who use the Google Chrome browser may have encountered the ERR_SSL_PROTOCOL_ERROR. It is a Secure Sockets Layer (SSL) error that occurs when the browser fails to establish a secure connection with the website.

ERR_SSL_PROTOCOL_ERROR may appear because of an issue with the website’s SSL certificate or the client’s browser. Although the main reason behind the error is often difficult to identify, there are simple ways to fix it.

This article will discuss what causes ERR_SSL_PROTOCOL_ERROR and explain three steps to repair it. We will also look at how the error appears differently on other popular browsers. Let’s get started.

What Is ERR_SSL_PROTOCOL_ERROR?

ERR_SSL_PROTOCOL_ERROR occurs due to the website’s misconfigured SSL certificate. The SSL connection error message also appears when a browser fails to connect to an SSL-protected website.

The cause of this error is difficult to discern. It may be caused by an error on the website or the visitor’s end.

For visitors, old browser extensions, outdated SSL caches, or the QUIC protocol may be the culprit. It is also possible that the Windows Defender Firewall or an antivirus program is blocking the secure connection.

When encountering ERR_SSL_PROTOCOL_ERROR as a visitor, try:

• Disabling an outdated or problematic browser extension.
• Temporarily turning off firewall or antivirus.
• Clearing browser cache.
• Disabling QUIC protocol.
• Fixing the system date and time.

If none of the solutions above work, the problem should be with the website. Use website checker tools to verify whether the website is down for everyone else or just you.

On the website’s end, a misconfigured SSL is a common reason. For instance, this error may appear when forcing HTTPS without a valid SSL certificate installed. Similarly, not forcing HTTPS on an SSL-certified website may cause the same issue.

3 Efficient Steps to Fix ERR_SSL_PROTOCOL_ERROR

Since it is difficult to pinpoint what causes the error, we will explain three typical steps to fix ERR_SSL_PROTOCOL_ERROR for both site owners and visitors.

These methods include making sure SSL is installed, forcing HTTPS, and clearing the browser’s cache and SSL state.

Important! Try the following troubleshooting methods in order. If the first one doesn’t fix the issue, try the next one.

1. Make Sure SSL Is Installed on Your Website

Forcing HTTPS without having SSL installed will make your website inaccessible, showing the ERR_SSL_PROTOCOL_ERROR. This happens when websites don’t have the certificate required to enable HTTPS connections.

If you host your website at Hostinger, use the hPanel control panel to check whether SSL is installed:

1. Open hPanel and click the Websites section.

1. Select the website in question from the drop-down menu.

1. Under the website’s domain name, look at the SSL status.

A green check mark indicates the website’s SSL is installed and active. Otherwise, you need to get an SSL first before enabling HTTPS.

Since many companies offer different types of SSLs, choosing one may be challenging. Follow these tips to help you purchase the right certificate:

• Choose a legitimate company. Make sure to buy a valid certificate from a reliable SSL provider to ensure its safety and legitimacy. Read user reviews and testimonies before finalizing your purchase.
• Know your use case. Depending on the type, SSL can support a different number of domains. For example, a multi-domain SSL protects multiple domains, while a wildcard SSL protects the main domain and its subdomains.
• Look for warranty and support. Pick a company that offers a warranty and 24/7 customer support. These features let you quickly fix or refund your SSL with the provider’s help.
• Consider your budget. SSLs vary in price, but you can get a free certificate from a nonprofit like Let’s Encrypt. Obtaining and installing Let’s Encrypt SSL has its benefits and is free, but you must renew it every 90 days.

The buying process of an SSL certificate differs depending on the provider. But generally, the steps are as follows:

1. Generate Certificate Signing Request (CSR). It is the encoded information about your website’s domain name, contact details, company, and public key.
2. Purchase the SSL you want.
3. Submit your CSR to the Certification Authority (CA) or the certificate issuer.
4. Wait until the domain validation process completes.
5. Install the SSL certificate on your website.

Alternatively, purchase any Hostinger web hosting plan, and get a free lifetime SSL service. For enabling a secure connection, these free SSLs are enough. They offer the same level of protection as the paid ones.

To install the free SSL with Hostinger, use hPanel:

1. Open the SSL section on hPanel.

1. Find the certificate and click Setup.

1. Select the website’s domain and click Install SSL.

1. The website should have SSL installed and the status as “active.” If not, likely, the domain is not pointing to Hostinger nameservers. To fix this, simply point the domain to our nameservers.

You may also install a custom SSL in hPanel if you purchase it from a third-party provider. The process may differ on other hosting control panels and hosting providers.

2. Force HTTPS Connection on Your Website

After installing SSL, your website will be available in HTTP and HTTPS protocols. Unless forced to run on HTTPS, your website will run on HTTP by default.

If the previous step does not solve the issue, check whether your website has HTTPS forced. Not forcing HTTPS is also a possible cause for ERR_SSL_PROTOCOL_ERROR.

Remember, switching from HTTP to HTTPS can cause issues for your website, including inaccessibility. For this reason, create a backup of your website before making further changes in case it goes wrong.

With Hostinger, all SSL certificates force HTTPS by default. To enable HTTPS manually using hPanel, follow these steps:

1. Go to the SSL section of hPanel.

1. Find your installed SSL certificates and click Manage.

1. Choose the domain you want to configure and click Force HTTPS.

These steps may differ for different hosting providers and control panels. Consider using other methods to force HTTPS:

• Edit the code on your .htaccess file to force HTTPS. This file is found on your WordPress site root directory. for websites made using the content management system.

Before generating the SSL credential, you must confirm that your website’s DNS settings have been fully propagated. Use online DNS checker tools such as WhatsMyDNS to track the propagation. Usually, the process can take up to 24 hours.

Installing an SSL certificate before the DNS fully propagates may cause the ERR_SSL_PROTOCOL_ERROR issue. The reason is that the certificate will have an incorrect associated domain name. In this case, try uninstalling the SSL and redo the troubleshooting steps.

3. Clear Your Browser’s Cache

After following the previous two steps, you should have resolved the issues on your website’s end. If the error persists, the problem is likely with your browser.

Browsers store information about the visited websites, including images, texts, files, and SSL, as a cache. When you revisit the website, your browser will retrieve the required resources from the cache instead of the site’s web server. This allows the web page to load more quickly.

Benefits aside, keeping an old cache may cause problems. If any important changes are made to the site, your browser may not be able to display it until it retrieves the new information.

Clearing your browser cache will force it to renew the cache with updated information. Therefore, doing so may help resolve various issues on your browser, including SSL errors.

Depending on the browser, the steps of clearing the cache may slightly differ. However, the overall process is similar. To clear the cache on Google Chrome, do the following:

1. On your Google Chrome browser window, click the three little dots icon next to the address bar.

1. From the drop-down menu, click More tools -> Clear browsing data.

1. Select your preferred Time range – the option ranges from Last hour to All time. We recommend choosing All time to ensure all caches are deleted.

1. Choose which type of website data you want to delete. To clear caches, check Cached images and files only. You may also delete Browsing history and Cookies and other site data.
2. Click the Clear data button to proceed.
3. Restart your browser.

Pro Tip

For Windows users, press Ctrl+Shift+Delete to access your browser’s delete browsing data menu. This key combination works on most browsers, including Google Chrome, Firefox, Edge, and Opera. To do the same in macOS, use Command+Shift+Delete.

Keep in mind that you may experience a slower site loading speed after clearing your cache. Moreover, wiping all browsing data will sign you out of most websites.

Similar to Google Chrome, other browsers’ clear cache functionality is accessible through the settings menu. Excluding Safari, most browsers also allow you to select the type of browsing data and the time frame of deletion.

In addition to caches, clearing the browser’s SSL state is another method to resolve the error.

Your browser stores an SSL cache for a similar purpose. If the website updates its certificate, this cache may cause an SSL connection failure because the cached certificate does not match the new one.

The steps of clearing the SSL state vary depending on the operating system and browser. For Google Chrome users running Windows, do the following:

1. Open your browser window, click the three little dots icon, and select Settings.

1. On the left sidebar, go to System -> Open proxy settings.

1. The Internet Properties pop-up window will appear. Go to the Content tab and click Clear SSL state.

1. Press OK to confirm.

For older versions of Google Chrome, open the Settings menu -> Advanced settings. The Open proxy settings button is under the Network tab. Alternatively, open the same window by typing Internet properties and hitting Enter. However, this method only works on newer Windows operating systems.

You may also clear the SSL state with Manage certificates on Google Chrome:

1. Navigate to the three dots menu on the browser window and click Settings.
2. On the left sidebar, select Privacy and security -> Security.

1. Scroll down and click Manage certificates. It shows a list of the SSLs cached by Google Chrome.

1. Navigate through the different tabs. After selecting an SSL, click Remove to clear the SSL state.

1. Click the Close or X button.
2. Restart Google Chrome to finish the process.

Pro Tip

If after clearing SSL or browser cache the ERR_SSL_PROTOCOL_ERROR persists, other programs may be the cause. Temporarily disable antivirus programs, firewall software, and browser extensions. Make sure that your system doesn’t have the incorrect date and time.

Other Errors Similar to ERR_SSL_PROTOCOL_ERROR

How Different Browsers Display ERR_SSL_PROTOCOL_ERROR

Although all browsers can face this problem, they may show different error messages. Let’s take a look at how several popular browsers display ERR_SSL_PROTOCOL_ERROR.

Google Chrome

When you encounter ERR_SSL_PROTOCOL_ERROR on Google Chrome, you will get the “This site can’t provide a secure connection” message. The exact error code is shown at the bottom.

Google Chrome explains that the website sent an invalid response. You may choose to Reload or Try running Windows Network Diagnostics.

Opera

Similar to Chrome, Opera users will also get the ERR_SSL_PROTOCOL_ERROR code. Opera will show “This site can’t provide a secure connection” with a description saying that the website sent an invalid response.

Clicking the Try running Windows Network Diagnostic will bring up the troubleshooting tool.

Microsoft Edge

Microsoft Edge will display the “The connection for this site is not secure” message when encountering the ERR_SSL_PROTOCOL_ERROR issue. The exact code will appear at the bottom of the error message.

Similar to the previous browsers, it also provides the Try running Windows Network Diagnostics clickable text.

Mozilla Firefox

Mozilla Firefox gives visitors a detailed description of the error message. When encountering a similar issue, the browser will warn you about a failed secure connection and show the SSL_ERROR_RX_MALFORMED_HANDSHAKE code.

You will get an explanation of what causes the error and what to do about it. Firefox users may retry by clicking the Try Again button or Learn more… to get further information about the error.

Conclusion

The ERR_SSL_PROTOCOL_ERROR occurs when a website cannot provide a secure connection. This may be due to issues on the website, such as not forcing HTTPS or not having an SSL certificate.

A problem with your browser may also cause the ERR_SSL_PROTOCOL_ERROR. Moreover, depending on the browser, the error message may appear differently.

While the error may seem tricky to resolve, we have provided three steps to help you fix ERR_SSL_PROTOCOL_ERROR as a website owner or visitor:

1. Ensure your website has SSL installed. To do this, check your hosting control panel. Having HTTPS enabled without the certificate can lead to an SSL connection error.
2. Force HTTPS on your site. After your website has an SSL installed, force HTTPS by configuring it through your hosting control panel, .htaccess file, or the WordPress dashboard.
3. Delete your browser cache. The browser may store an old SSL cache which can cause the connection issue. Clearing cache and SSL state allow the browser to renew the existing information.

We hope this article helps you troubleshoot the error. If you have any questions or alternative solutions, leave a comment below.

Aris is a passionate IT professional and WordPress enthusiast. He loves to share his knowledge and inspire people to start their online journey. When he’s not working or blogging, Aris enjoys watching gadget reviews and scribbling random doodles.

How to Fix ERR_SSL_PROTOCOL_ERROR?

Google Chrome is the most popular browser on the Web, but sometimes, even it can spoil your browsing experience. You might run unexpectedly into an SSL security error and struggle to fix it.

One such error is “This site can’t provide a secure connection — ERR_SSL_PROTOCOL_ERROR”. It’s quite tricky because there could be dozens of reasons behind it. If you’re lucky, it will go away with a simple page refresh, but if it sticks around for a while, you may need to try a few different fixes and see which one works for you. In this tutorial, we’ve listed several solutions to tackle this issue and get rid of it in no time.

Check the date and time on your system

The wrong date and time on your device may trigger the ERR_SSL_PROTCOL_ERROR in your Chrome browser. If the date on your PC or mobile phone isn’t in sync with the date of the servers you’re trying to connect to, chances are you’ll bump into this problem. Thankfully, there’s an easy fix to this. All you have to do is set the date of your system to the current date, and then re-open the site. If the error persists, don’t worry, try the next solution.

Disable QUIC Protocol

QUIC is a new Google Protocol that makes the Web faster and more efficient. Unfortunately, sometimes it can cause unexpected errors, including the ERR_SSL_PROTCOL_ERROR. Here’s how you can quickly rule it out:

1. Type chrome://flags#enable-quic in the Chrome browser’s address bar and click enter.
2. Under the Experimental QUIC Protocol option, change it from Default to Disabled.
3. Restart Chrome. If you still see the error, we recommend you enable QUIC back, as something else causes the issue.

Clear Browsing Data

It’s never a bad idea to clear your browsing data from time to time, just to keep things tidy and prevent all sorts of errors from popping up. You may even get rid of the ERR_SSL_PROTCOL_ERROR in the process.

1. Open your Chrome Browser and press Ctrl + Shift + Delete.
2. Set the time range to “All Time”.
3. Click the Cookies and other site data checkbox.
4. Click the Cached images and files checkbox.
5. Hit the Clear Data button.

Clear SSL State

The SSL state stores a cache of SSL certificates on your device, and you can empty it just like you’d clear your browser’s cache. Follow the steps below:

• Click the Google Chrome Settings icon, and then click Settings.
• Click Show advanced settings.
• Under Network, click Change proxy settings. The Internet Properties dialog box will appear.
• Click the Content tab.
• Click “Clear SSL state”, and then click OK.
• Restart Chrome.

Still no progress? Don’t give up! We’ve still got a couple of fixes on the way.

Remove the Hosts File

1. Press Windows + R, type in C:\Windows\System32\drivers\etc, and hit the enter button.
2. Find the Hosts file and delete it.
3. Restart Chrome

How’s your luck? Still nothing? Let’s try something else.

Disable Extensions

Extensions make browsing so much easier and efficient. However, sometimes they may interfere with its core functionality and mess quite a few things up. Disable all your Chrome extensions one by one and check the affected website again and again. To view all Chrome Extension, type chrome://extensions/ in the URL bar.

Check Firewall Settings

If your firewall has blocked the website or its IP address, Chrome will display the error. Check your firewall settings, and ensure that the website you’re trying to access isn’t blocked behind it.

Check Your Internet Security and Privacy Level

One last thing you should try is to adjust the level of your Internet Security and Privacy, because if it’s set too high, it may also be blocking access to websites.

1. In the search bar of your PC and type “Internet Options then press Enter.
2. Inside the Internet Properties dialogue, go to the Security tab and adjust the slider to Medium level if it’s set to a higher Scale.
3. Restart your browser, and open your site.

Hopefully, one of our solutions will fix the ERR_SSL_PROTOCOL_ERROR, once and for all.

Ошибка «Этот сайт не может обеспечить безопасное соединение» в Chrome, Opera и Яндекс Браузер

31.03.2022
itpro
Windows 10, Windows 11
комментариев 37

У меня почему-то перестали открываться некоторые HTTPS сайты (не все!). При попытке открыть такой сайт в браузере появляется окно с ошибкой «Этот сайт не может обеспечить безопасное соединение». Сайты не отображаются как в Google Chrome, так и в Opera, Яндекс Браузере и Microsoft Edge. Без HTTPS некоторые сайты открываются, но не все, только те, у которых страницы доступны и по протоколу HTTPS и по протоколу HTTP. В Google Chrome ошибка при открытии HTTPS сайт выглядит так:

Клиент и сервер поддерживают разные версии протокола SSL и набора шифров. Скорее всего, сервер использует шифр RC4, который считается небезопасный.» [/alert]

Или в Mozilla Firefox :

В Opera и Яндекс Браузере ошибки выглядит примерно также.

Как мне открыть такие сайты?

Ответ

Как вы уже вероятно поняли, проблема связана с проблемами при SSL взаимодействии между вашим компьютеров и HTTPS сайтом. Причины такой ошибки могут быть довольно разные. В этой статье я попробовал собрать все методы исправления ошибки «Этот сайт не может обеспечить безопасное соединение» (This site can’t provide a secure connection, ERR_SSL_PROTOCOL_ERROR) в различных браузерах.

Сразу хочется отметить, что несмотря на то, что браузеры Google Chrome, Opera, Яндекс Браузер и Edge выпускаются разными компаниями, на самом деле все эти браузеры основаны на одном и том же движке — WebKit (Chromium) и проблема с ошибками при открытии HTTPS сайтов в них решается одинаково.

В первую очередь нужно убедиться, что проблема не на стороне самого HTTPS сайта. Попробуйте открыть его с других устройств (телефон, планшет, домашний/рабочий компьютер и т.д.). Также проверьте, открывается ли в других браузерах, например, IE/Edge или Mozilla Firefox. В Firefox похожая ошибка обсуждалась в статье Ошибка при установлении защищённого соединения в Mozilla Firefox.

Очистите в брайзере кэш и куки, сбросьте SSL кэш

Кэш и куки браузера могут быть частой причиной возникновения ошибок с SSL сертификатами. Рекомендуем сначала очистить в браузере кэш и куки. В Chrome нужно нажать сочетание клавиш Ctrl + Shift + Delete, выберите промежуток времени (Все время) и нажмите кнопку очистки данных (Удалить данные / Clear Data).

Чтобы очистить SSL кэш в Windows:

1. Перейдите в раздел Панель управления -> Свойства браузера;
2. Щелкните по вкладке Содержание;
3. Нажмите на кнопку Очистить SSL (Clear SSL State);
4. Должно появится сообщение “SSL-кэш успешно очищен”;
5. Осталось перезапустить браузер и проверить, осталась ли ошибка ERR_SSL_PROTOCOL_ERROR.

Отключите сторонние расширения в браузере

Рекомендуем отключить (удалить) сторонние расширения браузера, особенно всякие анонимайзеры, прокси, VPN, расширения антивируса и другие подобные Addon-ы, которые могут вмешиваться в прохождение трафика до целевого сайта. Посмотреть список включенных расширения в Chrome можно, перейдя в Настройки -> Дополнительные инструменты -> Расширения, или перейдя на страницу chrome://extensions/ . Отключите все подозрительные расширения.

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

Если на вашем компьютере установлены антивирусная программа или межсетевой экран (часто он встроен в антивирус), возможно доступ к сайту блокируется именно ими. Чтобы понять, ограничивают ли доступ к сайту антивирусы или файрволы, попробуйте на время приостановить их работу.
Во многих современных антивирусах по-умолчанию присутствует модуль проверки SST/TLS сертификатов сайтов. Если антивирус обнаружит, что сайт использует недостаточно защищенный (или самоподписанный) сертификат или устаревшую версию протокола SSL (тот же SSL 3.0 или TLS 1.0), доступ к пользователя к такому сайту может быть ограничен. Попробуйте отключить сканирование HTTP/HTTPS трафика и SSL сертификатов. В различных антивирусах эта опция может называть по-разному. Например:

• В Dr.Web блокировать доступ к сайтам может встроенный сетевой экран (SpIDer Gate);
• В ESET NOD32 нужно отключить опцию «Включить фильтрацию протокола SSL/TLS»;
• В Avast опция называется «Включить сканирование HTTPs» (находится в разделе Настройки -> Активная защита -> Веб экран -> Настройки -> Основные настройки).
• В Kaspersky Internet Security нужно перейти в Настройки -> Дополнительно -> Сеть -> добавьте сайт в исключения или выберите опцию Не проверять защищенные соединения.

Проверьте настройки даты и времени

Неправильная дата и время (и часового пояса) на компьютере также может быть причиной ошибки при установке защищенного соединения с HTTPS сайтами. Ведь при выполнении аутентификации система проверяет срок создания и дату истечения сертификата сайта и вышестоящего центра сертификации.

Проверьте что у вас установлено правильно время и часовой пояс. Если время постоянно сбивается – смотри статью “Сбивается время на компьютере при выключении: что делать?”.

Обновите корневые сертификаты Windows

Если ваш компьютер находится в изолированном сегменте, давно не обновлялся или на нем совсем отключена служба автоматического обновления, на вашем компьютере могут отсутствовать новые корневые доверенные сертификаты (TrustedRootCA). Рекомендуем выполнить обновление системы: установить последние обновления безопасности и обновления часовых поясов.

Вы можете вручную обновить корневые сертификаты по статье: Как вручную обновить корневые сертификаты в Windows (так же рекомендуем проверить хранилище сертификатов на предмет недоверенных сертификатов, это позволит предотвратить перехват вашего HTTPs трафика и ряд других проблем).

Отключите поддержку протокола QUIC

Проверьте, не включена ли в Chrome поддержка протокола QUIC (Quick UDP Internet Connections). Протокол QUIC позволяет гораздо быстрее открыть соединение и согласовать все параметры TLS (HTTPs) при подключении к сайту. Однако в некоторых случая он может вызывать проблемы с SSL подключениями. Попробуйте отключить QUIC:

1. Перейдите на страницу: chrome://flags/#enable-quic;
2. Найдите опцию Experimental QUIC protocol;

Проверьте версии протоколов TLS, поддерживаемых вашим браузером и сайтом

Проверьте, какие версии протоколов TLS/SSL и методы шифрования (Cipher Suite ) поддерживаются вашим браузером. Для этого просто откройте веб страницу https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html

Онлайн сервис SSL Labs вернет список протоколов и методов шифрования, которые поддерживает ваш блаузер. Например, в моем примере Chrome поддерживает TLS 1.3 и TLS 1.2. Все остальные протоколы (TLS 1.1, TLS 1.0, SSL3 и SSL 2) отключены.

Чуть ниже указан список поддерживаемых методов шифрования.

Cipher Suites (in order of preference)

• TLS_AES_128_GCM_SHA256
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA

Get-TlsCipherSuite | Format-Table -Property CipherSuite, Name

Затем проверьте список протоколов TLS/SSL, которые поддерживает ваш сайт. Для этого воспользуйтесь онлайн сервисом проверки SSL https://www.ssllabs.com/ssltest/analyze.html?d=domain.ru (замените domain.ru на адрес сайта, который вы хотите проверить).

Проверьте, все ли версии TLS/SSL поддерживаемые сайтом доступны в вашем браузере.

В этом примере видно, что сайт не поддерживает TLS 3.1 и SSL3/2. Аналогично сравните список Cipher Suite.

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

Если сайт не поддерживает SSL протоколы, которые требует использовать клиент, то при подключении вы увидите ошибку “ Этот сайт не может обеспечить безопасное соединение”.

Включите поддержку старых версий протоколов TLS и SSL

И самый последний пункт. Cкорее всего для решения проблемы вам достаточно будет включить поддержку старых версий протоколов TLS и SSL. В большинстве случае он окажется самым эффективным, но я намеренно перенес его в конец статьи. Объясню почему.

Старые версии протоколов TLS и SSL отключены не по простой прихоти разработчиков, а в связи с наличием большого количества уязвимостей, которые позволяют злоумышленникам перехватить ваши данные в HTTPS трафике и даже видоизменить их. Бездумное включение старых протоколов существенно снижает вашу безопасность в Интернете, поэтому к этому способу нужно прибегать в последнюю очередь, если все другое точно не помогло.

Современные браузеры и ОС уже давно отказались от поддержки устаревших и уязвимых протоколов SSL/TLS (SSL 2.0, SSL 3.0 и TLS 1.1). Стандартном сейчас считаются TLS 1.2 и TLS 1.3

Если на стороне сайта используется более старая версия протокола SSL/TLS, чем поддерживается клиентом/браузером, пользователь видит ошибку установки безопасного подключения ERR_SSL_VERSION_OR_CIPHER_MISMATCH. Такая ошибка появляется, если клиент на этапе TLS Handshake обнаружил, что на сайте используется протокол шифрования или длина ключа, которая не поддерживается вашим браузером. Выше мы показали, как определить набор протоколов и шифров, поддерживаемых сервером.

Чтобы разрешить использовать старые версии протоколов SSL/TLS в Windows (еще раз отмечаю – это небезопасно!):

1. Откройте Панель Управления -> Свойства браузера;
2. Перейдите на вкладку Дополнительно;
3. Включите опции TLS 1.0, TLS 1.1 и TLS 1.2 (если не помогло, включите также SSL 3.0,2.0).
4. Перезапустите браузер.

Если все рассмотренные способы не помогли избавиться от ошибки «Этот сайт не может обеспечить безопасное соединение» также попробуйте:

1. 1. Проверить, что в файле C:\Windows\System32\drivers\etc\hosts отсутствуют статические записи. Файл hosts может использоваться в Windows в том числе для блокировки доступа к сайтам. Выведите содержимое файла hosts с помощью PowerShell: Get-Content $env:SystemRoot\System32\Drivers\etc\hosts
   2. Попробуйте использовать публичные DNS сервера, например – DNS сервер Google. В настройках сетевого подключения в качестве предпочитаемого DNS сервера укажите IP адрес 8.8.8.8;
   3. В Панели управления -> свойства браузера, убедитесь, что для зоны Интернет выбрана уровень безопасности Выше среднего или Средний. Если выбрана зона Высокий, некоторые SSL подключения могут блокироваться браузером.
   4. Возможно проблема связана с сертификатом сайта. Проверьте его с помощью онлайн утилит SSL Checker;
   5. Если на компьютере используется VPN или задан прокси сервер в Windows, попробуйте отключите их;
   6. В тестовых целях, если вам нужно быстро просмотреть содержимое сайта, можно отключить ошибки проверки SSL сертификатов в Chrome. Для этого нужно запустить его с параметром —ignore-certificate-errors: «C:\Program Files (x86)\Google\Chrome\Application\chrome.exe» —ignore-certificate-errors (не работайте в таком режиме постоянно и не отправляйте конфиденциальные данные пароли/кредитки в такой сессии);
   7. В Chrome проверьте, включен ли протокол TLS 1.3. В адресной строке перейдите в раздел настроек chrome://flags, С помощью поиска найдите параметр TLS 1.3. Убедитесь, что он включен (Enabled) или находится в состоянии Default. Если отключен – его нужно включить;
   8. Если у вас используется одна из старых версий ОС (Windows XP или Windows 7), установите вместо Chrome браузер Mozilla Firefox. В отличии от движков на базе Chromium, Mozilla не использует собственные модули реализации протоколов шифрования SSL/TLS, а не встроенные в Windows.

   Предыдущая статья Следующая статья

   How to Fix the ERR_SSL_PROTOCOL_ERROR

   

   If your WordPress website fails to load over a secure connection due to an error such as ERR_SSL_PROTOCOL_ERROR then you’re in the right place. In this article, we’ll explain what this type of error means and walk you through the steps needed to fix it to get your site back up and running!

   This error can be caused by various issues with your website server or your local computer, or even a combination of both. It’s commonly experienced in Chrome, but it can vary based on the browser you’re using.

   Check Out Our Video Guide to Fixing SSL Connection Errors

   Google Chrome

   In Google Chrome this error will show as ERR_SSL_PROTOCOL_ERROR and will say that the domain sent an invalid response.

   

   ERR_SSL_PROTOCOL_ERROR in Chrome

   Microsoft Edge

   In Microsoft Edge, it will simply show as “Can’t connect securely to this page” (as seen below). However, the next part of the error is what is helpful.

   This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

   

   ERR_SSL_PROTOCOL_ERROR in Microsoft Edge

   Mozilla Firefox

   In Mozilla Firefox ERR_SSL_PROTOCOL_ERROR triggers a warning about the failed secure connection as seen below.

   Warning: Potential Security Risk Ahead

   

   ERR_SSL_PROTOCOL_ERROR in Mozilla Firefox

   Unlike Google Chrome and Microsoft Edge, the Firefox error page offers a little more information about possible courses of action should this type of error occur.

   8 Things to Do When Experiencing ERR_SSL_PROTOCOL_ERROR:

   1. Clear SSL State.
   2. Verify SSL Certificate (DNS settings haven’t fully propagated yet).
   3. Check the System Time and Date.
   4. Clear Browser Cache and Cookies.
   5. Disable Browser Extensions.
   6. Update Browsers to Latest Version.
   7. Update Your Operating System.
   8. Temporarily disable Antivirus and Firewall (Sometimes these software might incorrectly block a secure connection).

   What is a Secure Connection Anyway?

   If you’re wondering what a webpage loading over secure connection is, then a little background information may be helpful.

   You may have noticed that website addresses typically begin with HTTP or HTTPS. These are called protocols which are basically a set of rules for determining how web pages are transmitted from the server (where your website is located) to the browser. HTTPS is a secure protocol based on HTTP and is widely used as it has a number of significant advantages including improved SEO and a high level of security.

   A downside to using HTTPS is that there are strict rules in place that need to be adhered to before a secure webpage can be displayed. This means that there’s more that can potentially go wrong compared to non-secure HTTP connections.

   One of these requirements needed to make a website work with an HTTPS connection is that you must have a valid SSL certificate installed and configured correctly. Invalid SSL certifications can cause problems preventing users from accessing websites. For example, the “Your Connection is Not Private” error.

   When your SSL certificate is working properly then a padlock icon is displayed next to the website address in the browser window. If you click on the padlock a popup window displays a confirmation notice that the website has been loaded over a secure connection and any information sent to the server from your website (e.g. form submissions) will also be transmitted securely.

   

   Secure connection

   Most website visitors these days have come to expect HTTPS connections over the entire site. Long gone are the days when the only secure pages on your site were limited and specific areas such as the admin, login, and shopping cart.

   Traditionally, it was deemed unnecessary (and overkill) to use a secure connection site-wide in-part due to the prohibitive expense of SSL certificates. All that has changed now though with free SSL certificates being readily available, so HTTPS has become standard practice.

   Taking Stock of Your Site

   Before we take a look at some of the possible underlying root causes of ERR_SSL_PROTOCOL_ERROR, it would be useful for you to take a moment and recall any recent changes that may have been made to your site.

   Usually, once you have a secure connection up and running it’s pretty stable. And most of the time, issues occur when something has been changed either on the server side for existing websites, or when setting up your site for the first time. If the requested site does not exist, you can expect to see the DNS_PROBE_FINISHED_NXDOMAIN error.

   Have you recently changed hosts or tried to install a new SSL certificate? This is the most common reason for this error to occur.

   Being aware of recent site changes may give you a strong indication of what could be causing the secure connection issue.

   Solutions to ERR_SSL_PROTOCOL_ERROR

   Work through the solutions in the following sections one-by-one until your secure connection error is fixed.

   This type of error can occur locally, or on the server, and so some steps focus on your local computer/browser settings, while other steps consider problems related to the server setup and how the SSL certificate has been configured.

   Clear SSL State

   The first thing to try is clearing the SSL state in Chrome. The browser stores SSL certificates in a cache to speed up subsequent connections once an initial secure connection has been made to a website.

   This is to optimize page load times as otherwise, every HTTPS request would require the SSL certificate to be downloaded and authenticated which wouldn’t be great for performance.

   When migrating a website to Kinsta, problems may arise when the DNS settings have been updated to point at Kinsta servers and the free SSL certificate from Let’s Encrypt has been installed.

   After the DNS settings have propagated and the site is accessed in a browser a secure connection, the error can sometimes be displayed due to the browser cache storing an outdated version of the SSL certificate.

   To fix this, try clearing the SSL state cache. Once done restart your browser and try connecting to your website again.

   If you’re using macOS see these instructions on how to delete an SSL certificate.

   Verify SSL Certificate

   A similar issue occurs when an SSL certificate is generated but the DNS settings haven’t fully propagated yet. In this case, the SSL certificate won’t be associated with the correct domain at the time of creation.

   If you’re a Kinsta client, you can check if your SSL certificate is installed by visiting the MyKinsta dashboard and making sure there is a green checkmark next to the certificate settings.

   Deploy your application to Kinsta. Get started now with a free trial.

   Run your Node.js, Python, Go, PHP, Ruby, Java, and Scala apps, (or almost anything else if you use your own custom Dockerfiles), in three, easy steps!

   

   SSL certificate properly installed

   You can also perform a site-wide scan with an online SSL checker tool to verify that there are no issues with your SSL certificate. This type of check is pretty reliable and bypasses your browser cache to determine if the certificate is valid.

   We recommend using the SSL check tool from Qualys SSL Labs which is the one we use internally at Kinsta.

   

   SSL Server Test

   Simply enter your domain into the Hostname field and click on the Submit button. Once the scan is complete a report is displayed with the results of the SSL certificate checks. If all is well you should see something like this:

   

   SSL Report Qualys

   You can find more in-depth information in our guide on how to check if your SSL certificate is working properly.

   Check the System Time and Date

   If the SSL certificate is valid and clearing SSL state doesn’t work, then it’s time to look at your local computer to identify the source of your ERR_SSL_PROTOCOL_ERROR.

   (Suggested reading: if you’re using legacy TLS versions, you might want to prevent ERR_SSL_OBSOLETE_VERSION Notifications in Chrome).

   First, check whether the operating system time and date are set correctly otherwise your SSL certificate may have problems being authenticated.

   This is because SSL certificates have a fixed expiry date and, if your current system time and date aren’t correct, then it may conflict with the authentication process.

   A valid time and date is always assumed when a secure connection is made, which is why it’s important to make sure the correct value is retrieved from your local system.

   To check the time and date in Windows 10, press the Windows Key + X keys and select System from the popup context menu. This will bring up the Settings window.

   In the Find a setting text box, start typing “time” and select Change the date and time from the dropdown options. Then, in the Date and time settings window check the time and date are correct before continuing.

   

   Date and time preferences in Windows 10

   On macOS, click the Apple icon in the top left corner of the screen and select System Preferences from the drop-down menu, and select Date and Time from the list.

   

   System preferences in macOS

   You’ll then be able to update your system time as necessary.

   Clear Browser Cache and Cookies

   You can also try deleting your browser cache if it’s been a while since it was last cleared. We recommend that you also delete browser cookies too, but bear in mind that any sites you’re currently logged into will require you to log in again the next time you visit them.

   Disable Browser Extensions

   If you have multiple browser extensions enabled, then this could potentially be the source of the error. Temporarily disable browser extensions one-by-one to see if there’s one causing issues with HTTPS requests.

   To disable Chrome extensions, click the three dots icon located towards the top right of the browser window and select More Tools > Extensions from the popup menu.

   

   Chrome extensions window

   Toggle all the enabled browser extensions one at a time to disable them, accessing your site in-between each one. If an extension appears to be causing the ERR_SSL_PROTOCOL_ERROR issue, then either remove it or leave it disabled until you can find out more information on the nature of the error.

   If no update is available to fix the issue, it’s probably best to remove the extension completely.

   Update Browsers to Latest Version

   The final browser-related step is to update Chrome to its latest version.

   Running older versions of a browser increases the chances that you’ll experience secure connection issues such as ERR_SSL_PROTOCOL_ERROR.

   New and updated security features are always added to modern browsers and bugs are fixed on a regular basis and keeping things up-to-date is a best practice you should follow.

   The Chrome browser makes this easier as it checks for updates automatically every time you launch the software. However, if you keep browser tabs always open, then you should remember to restart the browser from time to time to trigger update checks.

   Update Your Operating System

   Keeping your operating system up-to-date is important as well, especially if it’s been some time since the last update.

   If you have automatic updates turned on for Windows 10, then you don’t need to worry about this so much. But not all operating systems apply updates automatically so it’s worth checking if there are any available for your Operating System.

   On macOS click the apple icon and select About This Mac which will open a tabbed window:

   

   About this Mac

   If a system update is available you’ll see a Software Update button. Click this to install the latest updates. You can also check for macOS updates via the App Store just like you would for any other app.

   If you’re faced with a lengthy operating system update, you might want to just reboot your computer before running it as a quick workaround. This is much quicker than installing full operating system updates and could potentially solve the secure connection issue.

   Temporarily Disable Antivirus and Firewall

   It’s very important to have an antivirus and firewall software active on your system. These tools do a great job of protecting you from all sorts of online security issues.

   As part of this protection, your antivirus software usually checks for issues with HTTPS connections to make sure nothing unexpected is happening. Sometimes, though, the software might incorrectly block a secure connection when it shouldn’t.

   To check this isn’t the case, temporarily disable it and check your website again. If necessary, disable your firewall as well and check your website again.

   Remember to always re-activate your antivirus software and firewall as soon as possible as you don’t want to leave your system unprotected.

   Check Server Log for Error Messages

   If you’ve reached this stage and still haven’t resolved the ERR_SSL_PROTOCOL_ERROR issue, things might be a bit more complicated than what we thought in the beginning.

   To help identify general website issues, including connection errors, it can often help to check your server log and take a look at recent activity. This may well give more insight into what’s causing the issue.

   

   Server log

   If Everything Else Fails

   If you still can’t find what’s causing the issue then it’s time to let us know. We’re here to help as always!

   We’ll need to look deeper into what’s causing the issue so please contact support with as much relevant information as possible to get this issue resolved quickly.

   Get all your applications, databases and WordPress sites online and under one roof. Our feature-packed, high-performance cloud platform includes:

   • Easy setup and management in the MyKinsta dashboard
   • 24/7 expert support
   • The best Google Cloud Platform hardware and network, powered by Kubernetes for maximum scalability
   • An enterprise-level Cloudflare integration for speed and security
   • Global audience reach with up to 35 data centers and 275 PoPs worldwide

   Get started with a free trial of our Application Hosting or Database Hosting. Explore our plans or talk to sales to find your best fit.