In this post, we provide 6 fixes for the “ssl_error_rx_record_too_long” error.
When you use FireFox, there might be some instances that you’ll come across an error. One of them is the “ssl_error_rx_record_too_long” error. In this article, we’re going to go through the nature of this error, what causes it, and what are the possible fixes you can use.
Anyone else seeing this error on Blogspot?
— Terence Eden is on Mastodon (@edent) November 29, 2016
What is the ssl_error_rx_record_too_long Error?
If you use the latest Microsoft OS versions (e.g. Windows 7, 8, and 10), then there will be instances where you can come across the ssl_error_rx_record_too_long FireFox error.
This error appears when you connect to a website that has an HTTPS protocol using the FireFox browser and the secure connection fails. The problem, however, is that it can be tricky to figure out the exact cause of the problem. There are various factors including:
- Protocol issues
- Browser issues
- Security settings
- Software conflicts
If you’re not tech-savvy, this might sound alarming to you. Fortunately, this problem can be easily fixed by following the fixes mentioned below.
How to Fix the ssl_error_rx_record_too_long Error?
If you find the ssl_error_rx_record_too_long error recurring, then you need to fix it immediately. Here are the following fixes you can follow:
1st Fix: Change the Connection to HTTP Protocol
The very first fix you should try is to connect to the website without the secure protocol. According to Auslogics, the changes are done to the URL so as to bypass a secure connection. To achieve this, you have to follow these steps:
- Open the site with the ssl_error_rx_record_too_long error
- On the address bar, change https:// to http://
- After that, simply reload the page by either clicking on the Refresh icon or pressing the F5 button.
2nd Fix: Update Your Browser
According to Auslogics, your Firefox browser may fail to update itself automatically in accordance with the default settings. Hence it needs to be updated manually, as this may be causing the ssl_error_rx_record_too_long error. Here’s how:
- Open or launch your Firebox browser.
- Head to the upper right corner and look for the Menu icon. Click on it.
- After that, click Help then choose About Firefox from the drop-down.
- This will take you to the browser’s version screen. If your browser is currently outdated, simply update it.
Once you have updated the browser, restart it and check if the problem is fixed. If not, you might want to proceed to the next fix.
3rd Fix: Check Your Browser’s Proxy Settings
Windows Report suggests that the proxy connection might be the cause of the error, and as such recommends that you check its settings. However, there are no specific steps for this. Additionally, the HashedOut blog recommends that you shouldn’t attempt to configure the proxy on your own unless you’re an IT admin, as a misconfigured proxy setting can only lead to more problems.
Video Guide: How To Change Proxy Settings In Google Chrome
4th Fix: Start in Safe Mode
Safe mode can help fix several errors associated with your browser. This means that even the ssl_error_rx_record_too_long error can be solved by activating Firefox’s safe mode. As a matter of fact, the safe mode switches off all add-ons and extensions for a short time before turning back to default. To go to safe mode, follow the steps below as outlined by UGetFix:
- On your Firefox browser, click Open Menu then look for Help.
- From the drop-down list, click Restart with Add-ons Disabled then click Restart.
- Press Start in Safe Mode from the dialogue window that appears.
- After that, check whether the error has been resolved.
Video Guide: Open Google Chrome In Safe Mode
5th Fix: Disable All Add-ons
If the previous fix worked for you, then there’s no longer a need to fix it anymore. However, chances are you’ll still encounter the error when you open the website on a normal browser, and one of the probable cause of this is add-ons.
Add-ons are known to be important, but sometimes, they can also be the cause of the ssl_error_rx_record_too_long error. Thus, they need to be disabled. Here are the steps outlined by Windows Report:
- While still on Safe mode, click on the Menu button.
- Press the Help button from the drop-down menu then choose Restart with Add-ons Enabled.
- After that, in Firefox’s address bar, simply type about:addons then hit Enter.
- Click Disable for each of the add-ons you have added.
- Restart Firefox then visit the website again.
Video Guide: Disabling Chrome Extensions
6th Fix: Disable Your Antivirus Temporarily
In some cases, your antivirus may interpret some SSL certificates as a threat to your browsing activities. Hence, it will block any data from the page. This may be the reason behind the ssl_error_rx_record_too_long error. By disabling your antivirus, you can probably fix this issue.
If you are using a third-party antivirus, it’s best to check its manual so you can disable it. If you are using Microsoft’s Windows Defender, here are how you can do it as what Auslogics suggested (steps will vary depending on your OS version):
- Press the Windows key or simply click on Start Menu.
- Look for the Gear icon to open the Settings page.
- On the Settings page, click Update and Security.
- Go to Windows Security.
- Select Virus and threat protection. Go to its settings.
- Scroll down to the Real-time protection option then switch it off.
- Navigate to the Start menu then look for the Control Panel.
- Enable the Icons view on your Control Panel.
- Look for the Window Defender icon and click on it.
- Head to Settings.
- On the left side, click on Real-time protection then turn it off by unchecking the box.
- Save the changes afterward.
- Go to your Control Panel from the Start menu.
- Click on the Control Panel and enable the Icons view.
- Click on the Windows Defender icon.
- Head to the Tools section then look for Options.
- On the left pane, click on Real-time Turn it off by unchecking the box next to it.
- Save your settings then exit.
Video Guide: How To Disable Or Enable Windows Defender In Windows 10
We looked through different tech forums and support board to find more about the ssl_error_rx_record_too_long message and the problems users have with it. In general, people wanted to know about ssl_error_rx_record_too_long Firefox fix, ssl_error_rx_record_too_long Apache, and ssl_error_rx_record_too_long debian 9. They were also interested in ssl_error_rx_record_too_long Chrome and letsencrypt.
A site owner reported that users couldn’t access the website and that they kept getting the message that ssl_error_rx_record_too_long on all browsers and platforms.
- After he did some research on the subject, he discovered that this error was caused by an incorrect implementation of the SSL on the server side.
- The solution was to check if he had opened and enabled the 443 port on the server.
- He also recommended that you check your vhost config if you’re using Apache2 and that your SSL certificate hadn’t expired.
Another person said that the only thing that solved the ssl_error_rx_record_too_long error was to reinstall the SSL. He also mentioned that you should recheck the SSL configuration to see if you had set the SSLEngine on.
An individual shared that you might get the ssl_error_rx_record_too_long error when the SSL port was speaking in HTTP. The user also commented that the problem could be related to the user’s proxy configuration and that the problem might not be on the server-side at all.
Another computer owner commented that he had problems opening his site using Firefox, but it was working well in Chrome. In Firefox he was getting the ssl_error_rx_record_too_long error, and he was wondering if the issue was related to the SSL certificate or it was a Firefox bug.
A computer expert explains that ssl_error_rx_record_too_long occurs when you haven’t configured a certificate properly on the server’s port. The port is opened to the server, but since the configuration is not correct, users can’t access the website. The person adds that it’s an error that you are likely to encounter in web servers like Apache and Nginx.
Another individual shared that he encountered the ssl_error_rx_record_too_long problem in Apache and that he spent a lot of time researching how to fix it. Finally, he realized that it was related to an issue with the VirtualHost record because he didn’t have a VirtualHost record for the 433 port.
A person pointed out that if you’re a regular user and you can’t access a website because of the ssl_error_rx_record_too_long, you should contact the website’s owner and notify him of the problem.
- The individual states that you can do little on your part to fix the problem because it’s almost always on the server-side.
- What’s more, he warned that turning off your antivirus or switching to HTTP to bypass the issue was dangerous and probably would compromise the security of your online communications.
Another forum poster observes that ssl_error_rx_record_too_long is usually the result of two things – misconfiguration of the listening port or issues with the TSL version. The user recommends that you update your SL/TLS library if you haven’t already done it and that you check that you’re not supporting TLS 1.0 and SSL 3.0.
Another poster pointed out that using an irregular port or not having a trusted certificate would also result in a ssl_error_rx_record_too_long error and that the configuration of the port will depend on the type of server. In addition to this, he advised that you check your certificate once more to ensure that it’s working properly.
A person commented that he was getting the ssl_error_rx_record_too_long error when he was visiting different websites.
- The computer user added that reloading the page sometimes worked but other times didn’t.
- Since it was obvious that the problem was not on the server side, he was wondering what was wrong with his system.
- Other forum members advised him to clear the cache or attempt to load the page in an incognito window.
- They also said that he could write HTTPS before the URL and see if it would solve the problem.
Another user shares that if you’re using Tomcat, you should check if the connector is properly configured to use SSL and that the port number is correct. He also mentions that in Apache you should see if the Listen port matches the numbers in the VirtualHost directive.
An individual also says that you might experience the ssl_error_rx_record_too_long error if Firefox has enabled TLS 1.3 and the security software has an issue with it. You can fix that by going to typing about:config in the address bar and change the value as follows security.tls.version.max = 3.
One of the above fixes might work to resolve your the ssl_error_rx_record_too_long error. However, if nothing ever worked, the last option would be to reinstall your Firefox browser. It’s pretty straightforward, really. You just have to uninstall it from your programs list then download a fresh copy of the browser and install once again.
Ryan is a computer enthusiast who has a knack for fixing difficult and technical software problems. Whether you’re having issues with Windows, Safari, Chrome or even an HP printer, Ryan helps out by figuring out easy solutions to common error codes.