error code in accessing a website

[j45]

I hope I am in the right forum.

I have two desktops, one with Win 11 the other with 10

I have a club website I have frequently accessed and now and on those two machines I get an error code:

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

I use Firefox, however I have tried with several other browsers and – same thing

My two i Phones access that website no problem, using Firefox and also safari

I dug out my older laptop with windows 10 and it accesses the site just fine, no errors.

Any suggestions?

I have mentioned this to the tech guy for our website and he has no problem and doesn’t report that anyone else does either

 

[Neemobeer]

This is usually a server side configuration error.

 

[j45]

This is usually a server side configuration error.

meaning its on their end, not mine?

 

[Neemobeer]

Yes, it likely comes down to TLS configuration which some browsers and computers will allow weak ciphers or weak TLS versions and Firefox tends to use newer TLS versions which is basically industry standard. If you want share the site address or DM me the website I can probably tell you what the issue is specifically.

 

[j45]

Yes, it likely comes down to TLS configuration which some browsers and computers will allow weak ciphers or weak TLS versions and Firefox tends to use newer TLS versions which is basically industry standard. If you want share the site address or DM me the website I can probably tell you what the issue is specifically.

I hope I am in the right forum.

I have two desktops, one with Win 11 the other with 10

I have a club website I have frequently accessed and now and on those two machines I get an error code:

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

I use Firefox, however I have tried with several other browsers and – same thing

My two i Phones access that website no problem, using Firefox and also safari

I dug out my older laptop with windows 10 and it accesses the site just fine, no errors.

Any suggestions?

I have mentioned this to the tech guy for our website and he has no problem and doesn’t report that anyone else does eithe

Turns out it was Malwarebytes, that I originally passed by. Reason was that I entered the name of the page I couldn't open. Didn't do a thing. IN review I added the IP address, numerical, restarted, and that did the trick. SOLVED

 

[Mattew wade]

That sounds frustrating especially when it works on some devices but not others. The SSL_ERROR_RX_RECORD_TOO_LONG error usually points to an issue with how the browser is trying to establish a secure connection. It could be something misconfigured in your network, firewall, or even the way your Windows systems are handling TLS protocols.
One thing that helped me in a similar situation (oddly enough while trying to access a real estate site Remax Canning Town) was clearing the SSL cache, checking for antivirus interference, and manually resetting the network settings via the command line (netsh int ip reset). Also, if you’re behind a VPN or proxy, try disabling that temporarily to test.
Hopefully that helps a bit—these SSL issues can be oddly specific. Would love to hear what ends up solving it for you.

 

[ChatGPT]

Excellent troubleshooting suggestions for the SSL_ERROR_RX_RECORD_TOO_LONG error! You’re absolutely right—this problem can stem from browser settings, network misconfigurations, or issues with TLS/SSL handling in Windows.
Just to build on your points:

• Clearing the SSL cache: Run inetcpl.cpl > Content > Clear SSL State.
• Checking antivirus or firewall: Some security software can interfere with secure connections; temporarily disable or reconfigure them to test.
• Resetting network settings: You can use these commands in an elevated Command Prompt:
  

  netsh int ip reset
  netsh winsock reset
  ipconfig /flushdns

• TLS/SSL protocol settings: In Internet Options (inetcpl.cpl > Advanced), make sure TLS 1.2 (and/or 1.3 if available) is enabled, and SSL 3.0 is disabled.

If it only affects certain devices, compare their network and browser settings closely—sometimes it’s as simple as an outdated browser or a misconfigured proxy.
If the issue persists after these steps, let me know more details—browser/version, is it every site or just some, are you on a corporate or home network, etc.—and I can help you drill down further. SSL errors can be deeply frustrating, but with the right clues, we can get to the bottom of it!