Firefox has been giving Chrome some heavy competition despite the browser being comparatively lesser-known. The team behind it have made significant improvements to the browser in recent times.
However, just like everything tech, it also runs into problems. In this article, we’re talking about the SSL_ERROR_RX_RECORD_TOO_LONG error in Firefox.
Why does it happen?
The error happens exclusively on Firefox and is relatively standard. The leading cause behind it is issues with your site’s SSL certificate. It mainly occurs when a client tries to connect to an open port on the server, but the SSL certificate doesn’t allow the connection due to incorrect configuration settings.
How to fix SSL_error_rx_record_too_long?
Luckily, resolving the error is rather simple. Here are a few fixes you can try out.
If you’re using HTTP to connect to the server, try switching it to HTTPS. These days most SSL certificates don’t allow HTTP as it’s less secure and more prone to attacks.
Get a reliable SSL certificate
If you’re getting your certificates from a not-so-popular issuing authority, chances are your SSL certificate is at fault. We recommend using LetsEncrypt or ZeroSSL to get SSL certificates that don’t cause such problems.
Clear your browser’s cache
Corrupt files in your browser’s cache can cause all sorts of problems, including this one. Here’s how you can clear out the cache in Firefox.
Step 1: Click on the hamburger menu icon in the top right and click Options.
Step 2: Head over to the Privacy & Security tab.
Step 3: Scroll down to Cookies and Site Data and click on the Clear Data… button.
Step 4: Check Cookies and Site Data as well as Cached Web Content and click on Clear.
Restart your browser and try accessing the site again. This should resolve the SSL_error_rx_record_too_long issue.
Also read: AirPods case not charging: 6 Fixes
Remove any third-party firewalls
If you’re using any other firewalls apart from the default Windows one, chances are it’s sending an RST to Firefox to terminate the attempted connection between the browser and the webserver.
Try disabling or removing the firewall to check if the browser works without one. If it does, either remove the firewall for good or add an exception for Firefox in the firewall settings.
Disabling any proxies or VPNs that you might be using
Another rather common reason people run into this issue is when they’re trying to connect to a host through a proxy or a VPN connection, and the host keeps on denying the connection request.
Several high profile sites, especially streaming ones like Netflix and Amazon Prime Video, detect and disable proxies or VPNs these days. In such cases, the solution is pretty straightforward. You disable your proxy or VPN client and try again.
Updating your browser to the latest version available can also help resolve any security issues. To update Firefox, head over to the Settings page, scroll down to the Firefox Updates section and check for any available updates.
If any updates are available, install them, restart the browser and try again.
Also read: Hulu error 5003: 6 Fixes
The error can also be caused by a faulty extension interfering with Firefox’s functionality. Head over to Firefox’s Addons page and disable any active extensions.
Once they’re all disabled, restart the browser and try connecting to the site again. If you can, enable extensions one at a time until you get the error again. The latest extension that you enabled here is causing the issue.
Use the Safe mode
In conjunction with the last solution, try restarting Firefox in safe mode with any add-ons disabled to see if you can access the site.
Step 1: Head over to Firefox and click the hamburger menu icon in the top right. Click on Help.
Step 2: Click on Troubleshoot mode.
Your browser will now restart in the safe mode. Try accessing your site again. The SSL_error_rx_record_too_long issue should be fixed.
Someone who writes/edits/shoots/hosts all things tech and when he’s not, streams himself racing virtual cars. You can reach out to Yadullah at [email protected], or follow him on Instagram or Twitter.