SSL_ERROR_RX_RECORD_TOO_LONG
For the past few days almost every site I try to visit gets the error:
Secure Connection Failed An error occurred during a connection to.... SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
this has happened on and off in the past for one or two sites but usually fixes itself within a day or less but this time it's been days. I tried everything I've seen online: -Try without add ons, - I am using 'system settings' proxy, -Followed an 8-yr-old suggestion of switching security.tls.version.max from 4 to 3 -My AV doesn't have HTTPS scanning that I can disable -It doesn't allow me to toggle the 'enhanced tracking is on' in the address bar -I've tried adding a site as an exception to DNS over HTTPS and turning Enable DNS over HTTPS off
Nothing has helped. These are all sites I've used in the past. I am using Nightly v150 at the moment but obviously same situation with FF or R3dfox.
If anyone can suggest how to bypass this so I don't have to use Edge/Chrome/Supermium (which all display these sites without issue) I'd appreciate it so much!
(*I'm looking for help with THIS issue on a W7 laptop, not about whether I should upgrade the OS.)
Thanks.
All Replies (4)
Try to click the shield icon in the address bar and click Clear cookies and site data.
OTOH that Nightly is now a bit outdated, you'd want to upgrade further to see if anything changes. (Also, Nightly might have some HTTPS-first or TLS intolerance features flipped some way, so watch out for these…)
What's basically a first suspect usually is forcing non-HTTPS service to an HTTPS connection:
I tried clicking the shield.. (there is no toggle on FF shield and the other two are greyed out.).. I have all cookies/cache set to clear every time the browser closes.
with regards to nightly, this is happening with firefox, nightly and r3dfox.. but all of these sites were working fine a few days ago (and there have been no updates since).. I checked yesterday and didn't see a newer version (150) but I'll check again.
My message disappears so if it shows twice my apologies
UPDATE: I checked Github and it seems 150 is the latest [https://github.com/e3kskoy7wqk/Firefo.../150.0] (unless I missed it).. but I did update R3dfox and it made no difference. Nightly might have some HTTPS-first or TLS intolerance features flipped some way, so watch out for these - I'm sorry, not sure I know what this (or the links) means.. all I know is that these sites worked fine two days ago and now don't work on ANY FF/ fork browser.
Modified by M
UPDATE: When I check Nightly on Github it says 150 is the latest [https://github.com/e3kskoy7wqk/Firefo.../150.0] .. maybe I'm missing it but I did update R3dfox and it made no difference. (I've tried everything I can think of - it's never lasted this long in the past). ' might have some HTTPS-first or TLS intolerance features flipped some way, so watch out for these' - I'm sorry I don't know what this means.. all I know is that all sites worked fine 2 days ago and the issue is across all 3 of them.
Modified by M
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.