Старая ошибка ssl error rx record too long в Firefox

Troubled by seeing Apache ssl_error_rx_record_too_long on your website? You are not alone!

This error frequently occurs when SSL traffic is not set up properly on the target secure server.

At Bobcares, we often get requests from our customers regarding the Apache SSL certificate error as part of our Server Management Services.

Today, we’ll see how our Support Engineers find fix for our customers.

  • Вопрос задан

    более трёх лет назад

  • 2424 просмотра

Опера ругается так –

Этот сайт не может обеспечить безопасное соединение
Сайт www. learnjavaonline. org отправил недействительный ответ.

Этот сайт не может обеспечить безопасное соединение
Сайт www. learnjavaonline. org отправил недействительный ответ. ERR_SSL_PROTOCOL_ERROR

Ошибка при установлении защищённого соединения
При соединении с www. learnpython. org произошла ошибка. SSL получило запись, длина которой превышает максимально допустимую. Код ошибки: SSL_ERROR_RX_RECORD_TOO_LONG
Страница, которую вы пытаетесь просмотреть, не может быть отображена, так как достоверность полученных данных не может быть проверена. Пожалуйста, свяжитесь с владельцами веб-сайта и проинформируйте их об этой проблеме.

Проблема на всех устройствах, подключенных к сети, т. на телефоне и планшете тоже.

Проверял время, пробовал ipconfig /flushdns, устанавливал dns от гугла/яндекса, интереса ради переустановил винду на моем ПК. За время существования этой проблемы успел сменить роутер, сейчас у меня MI-3 с прошивкой от Padavan, до этого был Asus RT-N12.

В чем может быть проблема? Пора звонить провайдеру?

Secure Connection Failed

An error occurred during a connection to 23. xxx. xxx. xx:8005. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

Старая ошибка «SSL ERROR RX RECORD TOO LONG» совершенно неожиданно появилась в новом Firefox. Буквально сразу после апдейта браузер вдруг сообщает о неудачной попытке подключится к сайту.

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

Табличка с уведомлением об ошибке немного пугает:

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

В предыдущих версиях Firefox ошибка «SSL ERROR RX RECORD TOO LONG» вроде как не случалась. В описании версии 61 компания Mozilla ранее указывала, что в ней используется некий вариант спецификации TLS 1.

Не пропустите: ПРОВЕРКА CAPTIVE PORTAL В БРАУЗЕРЕ FIREFOX: КАК ОТКЛЮЧИТЬ

Проверить, какая именно версия TLS была установлена можно просто по ссылке about:config?filter=security. tls. version. Копируем её в адресную строку браузера, жмем Enter.

Далее в открывшейся табличке ищем строчку security. tls. version. max, ей по умолчанию соответствует значение 4. Начиная с Firefox 61 это новый максимум, раньше было 3:

Старая ошибка ssl error rx record too long в Firefox

Так вот, если для security. tls. version. max вручную прописать значение 3 (двойной клик по цифре 4, пишем 3 и жмем ОК), то ошибка «SSL ERROR RX RECORD TOO LONG» больше не появляется. То есть, Firefox нормально открывает сайты и, собственно, на этом чтение данного поста можно и завершить.

Делается это, напомним, следующим образом:

  • двойным кликом по значку в трее открываем меню Avast и в нем жмем «Настройки«;
  • в колонке слева кликаем «Компоненты«;
  • в списке справа находим строку «Веб-экран» и в ней жмем «Настройки«;

Старая ошибка ssl error rx record too long в Firefox

I had to remove the +CompatEnvVars from

SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire

I’m new to SSL, any advice on what’s going wrong?

asked Mar 29, 2010 at 14:38

by removing the port 80 from the url, the redirect works.

answered Aug 31, 2010 at 13:55

Greg BGreg B

2k18 gold badges82 silver badges137 bronze badges

and it worked like a charm.

answered Aug 6, 2012 at 17:04

3293 silver badges2 bronze badges

I had that same error. I forgot to create a link from sites-enabled/000-default-ssl to the sites-available/default-ssl file.

answered Mar 25, 2011 at 19:58

2653 silver badges6 bronze badges

This seems to be the result you see from Firefox when the server is not configured properly for SSL. Chrome, BTW, just gave a generic “ssl failed” code.

As we can see from the responses here there are many things that can break the SSL configuration but not stop the server starting or give any hints in error. log.

What I did was systematically check down all the answers until I finally found the right one, right at the bottom.

Here is what I had in the access logs:

answered Oct 9, 2016 at 1:40

Старая ошибка ssl error rx record too long в Firefox

This error also occurs when you have enabled the SSL module (i. you have run e. a2enmod ssl) but not yet enabled any SSL site entries (i. e you have not run e. a2ensite default-ssl).

answered Dec 13, 2012 at 13:04

5,74839 silver badges57 bronze badges

I got this error when I was trying to access a url using curl:

answered Mar 21, 2019 at 6:13

Старая ошибка ssl error rx record too long в Firefox

3,1883 gold badges35 silver badges44 bronze badges

In my case, I needed to install mod_ssl first

yum install mod_ssl

answered Aug 11, 2016 at 20:29

4,0395 gold badges32 silver badges57 bronze badges

answered Feb 15, 2016 at 19:33

a codera coder

7,20420 gold badges79 silver badges126 bronze badges

answered Dec 28, 2020 at 8:33

1,6521 gold badge19 silver badges20 bronze badges

In my case I accidentally used SSL in the Virtualhost configuration for port 80, instead of 443.

answered Aug 19, 2012 at 7:57

3,0623 gold badges28 silver badges38 bronze badges

In my case, an Ubuntu system, in ports. conf I had

NameVirtualHost *:80
NameVirtualHost 192. 168. 79
Listen 80

And then, inside , I had

NameVirtualHost *:443
Listen 443

All I had to do was remove the line NameVirtualHost 192. 168. Restarted apache and problem solved.

214k98 gold badges444 silver badges487 bronze badges

answered Nov 9, 2012 at 21:25

271 bronze badge

I know this isn’t APACHE related, but it is definitely a page that people with that error will find.

answered Oct 7, 2015 at 14:50

If you are upgrading from an older version of apache2, make sure your apache sites-available conf files end in. conf and are enabled with a2ensite

answered Jun 4, 2019 at 9:57

1211 silver badge5 bronze badges

Below Solution worked for me :

Type About:Config in the Address Bar and press Enter.

“This Might void your warranty!” warning will be displayed, click on I’ll be careful, I Promise button.

Type security. ssl. enable_ocsp_stapling in search box.

The value field is true, double click on it to make it false.

Now try to connect your website again.

answered Oct 23, 2019 at 20:18

On My side, Error if nginx. conf like

curl: (35) SSL received a record that exceeded the maximum permissible length.

answered Apr 7 at 15:06

Старая ошибка ssl error rx record too long в Firefox

Nanda ThotaNanda Thota

1252 silver badges6 bronze badges

I’ve got a customer trying to access one of my sites, and they keep getting this error > ssl_error_rx_record_too_long

They’re getting this error on all browsers, all platforms. I can’t reproduce the problem at all.

My server and myself are located in the USA, the customer is located in India.

Can anyone tell me how I can fix this, or how I can reproduce this???

Turns out the customer had a misconfigured local proxy!

Hope that helps anyone finding this question trying to debug it in the future.

asked Sep 23, 2008 at 6:07

4,3283 gold badges23 silver badges18 bronze badges

The link mentioned by Subimage was right on the money for me. It suggested changing the virtual host tag, ie, from to

Below are some things we recommend trying.

  • If SSL is using a non-standard port then FireFox 3 can sometimes give this error. Ensure SSL is running on port 443.
  • Make sure you do not have more than one SSL certificate sharing the same IP. Please ensure that all SSL certificates utilise their own dedicated IP.

That fixed my problem. It’s rare that I google an error message and get the first hit with the right answer! 🙂

In addition to the above, these are some other solutions that other folks have found were causing the issue:

  • Make sure that your SSL certificate is not expired
  • Try to specify the Cipher:

answered Jan 21, 2011 at 19:31

2,6241 gold badge19 silver badges22 bronze badges

The solution for me was that default-ssl was not enabled in apache 2. just putting SSLEngine On

I had to execute a2ensite default-ssl and everything worked.

answered Mar 30, 2010 at 19:01

7k105 gold badges300 silver badges472 bronze badges

In my case I had to change the back to (which is the default on Ubuntu). Otherwise, the port 443 wasn’t using SSL and was sending plain HTML back to the browser.

answered May 20, 2009 at 11:13

6798 silver badges8 bronze badges

answered Nov 18, 2010 at 12:36

Старая ошибка ssl error rx record too long в Firefox

2493 silver badges6 bronze badges

Old question, but first result in Google for me, so here’s what I had to do.

Ubuntu 12. 04 Desktop with Apache installed

All the configuration and mod_ssl was installed when I installed Apache, but it just wasn’t linked in the right spots yet. Note: all paths below are relative to /etc/apache2/

mod_ssl is stored in. /mods-available, and the SSL site configuration is in. /sites-available, you just have to link these to their correct places in. /mods-enabled and. /sites-enabled

cd /etc/apache2
cd. /mods-enabled
sudo ln -s. /mods-available/ssl. /
cd. /sites-enabled
sudo ln -s. /sites-available/default-ssl

answered Apr 16, 2012 at 17:12

3,9462 gold badges22 silver badges33 bronze badges

answered Sep 23, 2008 at 6:12

4,7474 gold badges18 silver badges16 bronze badges

In my case, I had the wrong IP Address in the virtual host file. The listen was 443, and the stanza was but the server did not have the 192. 168. 1 address!

answered Jul 14, 2011 at 22:00

7427 silver badges8 bronze badges

You might also try fixing the hosts file.

Keep the vhost file with the fully qualified domain and add the hostname in the hosts file /etc/hosts (debian)

ip name name. domain. com

After restarting apache2, the error should be gone.

answered Jul 16, 2012 at 13:01

Anna BAnna B

5,5815 gold badges37 silver badges51 bronze badges

Please see this link.

I looked in all my apache log files until I found the actual error (I had changed the from _default_ to my fqdn). When I fixed this error, everything worked fine.

Старая ошибка ssl error rx record too long в Firefox

answered Jul 30, 2010 at 13:21

My problem was due to a LOW MTU over a VPN connection.

netsh interface ipv4 show inter

Idx Met MTU State Name
— — —– ———– ——————-
1 4275 4294967295 connected Loopback Pseudo-Interface 1
10 4250 **1300** connected Wireless Network Connection
31 25 1400 connected Remote Access to XYZ Network

Fix:
netsh interface ipv4 set interface “Wireless Network Connection” mtu=1400

It may be an issue over a non-VPN connection also.

answered May 21, 2009 at 14:07

I had a messed up virtual host config. Remember you need one virtual host without SSL for port 80, and another one with SSL for port 443. You cannot have both in one virtual host, as the webmin-generated config tried to do.

answered Jun 30, 2009 at 14:34

Hope that helps somebody.

4k46 gold badges148 silver badges153 bronze badges

answered Dec 1, 2008 at 14:36

Pushnov IliyaPushnov Iliya

I had the same problem in some browser to access to my SSL site. I have found that I had to give to fireFox the right proxy (FireFox was accessing directly to internet).

Depending of the lan configuration (Tunneling, filtering, proxy redirection), the “direct access to internet” mode for FireFox throws this error.

answered Sep 9, 2009 at 9:18

Старая ошибка ssl error rx record too long в Firefox

For me the solution was that my ddclient was not cronning properly.

answered Sep 26, 2012 at 17:01

1411 silver badge3 bronze badges

Everyone wants their websites to be secure. But, improper implementation of security often results in errors like Apache ssl_error_rx_record_too_long.

Старая ошибка ssl error rx record too long в Firefox

Some possible causes for this error are:

  • SSL traffic is not set up properly on the target server.
  • DNS may not be correct in the DNS name on VirtualHost.
  • Misconfigured proxy not allowing an SSL handshake on port 443 correctly.

What are the Fixes?

In simple terms, the fix for the SSL error involves handling the secure traffic reaching the server correctly. We’ll now take a look at the exact steps involved.

We make sure that SSL is running on port 443. Because if SSL is running on a non-standard port, then Firefox may show this error.

Upon finding the correct port settings, we check and confirm that the SSL certificate is valid and not expired.

Also, we make sure not more than one SSL is sharing the same IP.

On IPv6, our Engineers include the IP Address for eliminating this error.

Similarly, when customers get this error on Windows, we check whether the host file on the Windows server is properly set.

If not, we do it by changing VirtualHost domain. com:443 to VirtualHost _default_:443.

Each server configuration differs and so the troubleshooting will not be identical. However, we check the path of the SSL traffic and make corrections. This solves the problem and makes the SSL version of the website working again.

Читайте также:  Цена в магазине Spliti.ru, Тех. документация

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *