Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Regularly getting SSL error on https sites in Firefox Developer Edition

  • 3 antwurd
  • 1 hat dit probleem
  • 51 werjeftes
  • Lêste antwurd fan user1517320

more options

New laptop, new installation of my favourite broswer, Firefox Developer Edition. For some reason, I regularly get the following error on various https sites:

'SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)'

It's definitely not an issue with the sites themselves (it's happened with Bugzilla, Google and various other high-profile sites). It occurs when connecting to various WIFI networks, and only on Firefox Developer Editon (vanilla Firefox, Google Chrome, MS Edge all work as expected).

I've reinstalled and tinkered with a couple of the settings in about:config, but not really sure where to start. Has anyone else experienced this recently? Anyone have any insight what might be causing it and how I could go about fixing it?

If not a Fiefox issue, presumably the issue is with the new laptop - is there anything I can do in Windows 10 to help diagnose?

Many thanks.

New laptop, new installation of my favourite broswer, Firefox Developer Edition. For some reason, I regularly get the following error on various https sites: 'SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)' It's definitely not an issue with the sites themselves (it's happened with Bugzilla, Google and various other high-profile sites). It occurs when connecting to various WIFI networks, and only on Firefox Developer Editon (vanilla Firefox, Google Chrome, MS Edge all work as expected). I've reinstalled and tinkered with a couple of the settings in about:config, but not really sure where to start. Has anyone else experienced this recently? Anyone have any insight what might be causing it and how I could go about fixing it? If not a Fiefox issue, presumably the issue is with the new laptop - is there anything I can do in Windows 10 to help diagnose? Many thanks.

Keazen oplossing

hi, thanks for reporting the problem, so far we have heard about this from avast/avg users whose security software is meddling with encrypted connections. firefox 61 introduced the better security protocol tls 1.3 & apparently avast can't cope with that yet.

as a workaround, please try to disable the scanning of https connections as described in https://support.mozilla.org/en-US/kb/secure-connection-failed-error-message#w_avast-and-avg-security-products

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (3)

more options

Hi, this error seems to be intermittent or is fixed in a day.

There is security software like Avast/AVG, Kaspersky, BitDefender and ESET that intercept secure connections and send their own certificate. If you are running any of the above software please their their community forum for a work around to apply settings.

These pages are also for the errors you may have besides relating to the above.

Please let us know if this solved your issue or if need further assistance.

more options

Keazen oplossing

hi, thanks for reporting the problem, so far we have heard about this from avast/avg users whose security software is meddling with encrypted connections. firefox 61 introduced the better security protocol tls 1.3 & apparently avast can't cope with that yet.

as a workaround, please try to disable the scanning of https connections as described in https://support.mozilla.org/en-US/kb/secure-connection-failed-error-message#w_avast-and-avg-security-products

more options

Thank you, both. I'd scoured various support pages but never came across that one for some reason. Turns out Avast was indeed my issue.

I'll report it to Avast too; hopefully they'll prioritise fixing it on their end for a future update.