You’re in luck if you’re searching for a way to get around the “Secure Link Failed” page with the “SSL ERROR RX RECORD TOO LONG” error message. We’ll go through nine tried-and-true solutions for site visitors and administrators in this article to help you prevent or repair this mistake.

Let’s start with a couple of fast points:

  • A server-side error is SSL ERROR RX RECORD TOO LONG. As a website visitor, the only choices are to ignore the error or force the browser to trust and open the website for a limited time. Only the owner of a website can have a long-term solution to this problem.
  • Only Firefox encounters this server-side bug. And if you move to a different browser, the error message would be slightly different.
  • An SSL/TLS certificate misconfiguration is to blame for the issue. If you’re the owner of a website, SSL ERROR RX RECORD TOO LONG means you haven’t properly installed your TLS/SSL certificate. Please scroll down to the bottom of the page to see the website owner’s solution.

How to Resolve SSL ERROR RX RECORD TOO LONG as a Site Visitor

These options are only available to website users. You may not have to use any of them. Simply try each one before you find one that works for you and helps you to bypass the SSL ERROR RX RECORD TOO LONG error tab.

Solution 1: Configure the TLS Version Acceptance Level

Some SSL certificates are compatible with older TLS versions including TLS 1.1 and TLS 1.2. Although Firefox’s security settings are set to accept only the most recent TLS update, i.e. TLS 1.3, Firefox displays the SSL ERROR RX RECORD TOO LONG error when it encounters an SSL certificate that supports an older TLS version.

You may make Firefox allow websites that use SSL certificates that support older TLS versions by adjusting the TLS acceptance level. Since you’ll still be accessing a website that uses the HTTPS protocol to encrypt data, this is the best way to avoid the SSL ERROR RX RECORD TOO LONG error.

  • Write “about:config” in the Firefox address bar.
  • Click on the I accept the risk button.
  • Now, search for “security.tls.version.max” and double click on it.
  • Set security.tls.version.max as “3.”
  • Search “security.tls.version.min” in the search box and double click it.
  • Set security.tls.version.min as “0.”

You’re asking Firefox to allow websites that use any TLS version, including TLS 1.1, TLS 1.2, TLS 1.3, and TLS 1.0, by doing this.

If this suggestion doesn’t work, try the next one.

Solution 2: Clear Browsing History and Cache Memory

Often the SSL ERROR RX RECORD TOO LONG error has been fixed on the server side, but Firefox’s cache memory is still showing old details. This problem can be fixed by clearing your browsing history, cookies, and cache memory:

  • Open Firefox and navigate to Options from the top-right drop-down menu.
  • Go to Privacy and Security from the left menu bar.
  • Click on Clear Data in the Cookies and Site Data section.
  • Select Clear History.
  • Select all the options and click on Clear Now.

Note: From this point on, all of the site visitor solutions are risky because you will be accessing the website that has a misconfigured SSL/TLS certificate and is transferring your data using unsecured HTTP channel. Use them only when you are 100% sure that website you are approaching is safe! 

Solution 3: Trusted Sites Configuration

When you add a website to your “trusted sites” list, regardless of its SSL/TLS configuration, all browsers can trust it. To add a website to your trusted sites list, follow these steps:

  • Search Internet Options in your Windows search bar.
  • In the Internet Properties window, click on the Security tab.
  • Select Trusted Sites.
  • Click on the Sites button — a new window will pop-up.
  • Manually add the URL of the website that’s displaying the error message. Select Add and then Close.
  • Back in the Internet Properties window, click Apply and OK. That’s it!

Solution 4: Shift to Using the HTTP Protocol

Shifting from HTTPS to HTTP is one of the simplest solutions for the SSL ERROR RX RECORD TOO LONG error. Note: We’re telling you that this is a potential solution to the problem. However, connecting to a website using the unreliable HTTP protocol is not a good idea because it puts you at risk.

Only this solution would work if the website does not have a 301 redirect.

The website you’re trying to open will begin with HTTPS:// in the address bar. Simply delete the letter “s” from HTTPS:// and use HTTP:// to access the website.

However, if the website has already been redirected to HTTPS, this approach does not work. If this is the case, proceed to the next step.

Solution 5: Open the Website in Safe Mode

Protection add-ons don’t often open websites with misconfigured SSL certificates. All add-ons will be disabled when you restart Firefox in safe mode, and you will be able to access the site.

To start Firefox in safe mode, go to the browser menu and select “Safe Mode” (three lines on the right side of the window).

  • Navigate to Help.
  • Select Restart with Add-ons Disabled…
  • Select the Restart Tab Click on Start in Safe Mode.

That concludes our discussion. Congratulations if it succeeded. If not, we’ll move on to the next method.

Solution 6: Change Your Proxy Settings

The SSL ERROR RX RECORD TOO LONG message may also be triggered by incorrect proxy connections. You can disable proxy settings to see if this is the source of the error by doing the following:

  • Go to Firefox menu and click on Options. 
  • Locate Network Settings and click on Settings.
  • Select No Proxy option.
  • Click OK and restart the browser.

Solution 7: Temporarily Disable Your Antivirus and Firewall

SSL scanning is used in most antivirus and firewall applications. As a consequence, even though you’ve told browsers to disregard SSL-related errors, the antivirus software would still block websites with misconfigured SSL certificates.

Simply look for SSL-related settings in your antivirus programme or firewall. It could be called stuff like “HTTPS Scanning,” “Scan SSL,” “show the safe result,” “don’t scan encrypted connections,” and so on. Disable these options. If you can’t find a setting location, you can temporarily disable the antivirus/firewall.

Note: Turning off your antivirus and firewall is a dangerous move that we never advise. If you want to use this form, make sure to reactivate the solution(s) you disabled once you’ve gained access to the desired website.

That’s what there is to it. Now it’s time to focus on assisting site owners and administrators in resolving the problem with their pages.


SSL ERROR RX RECORD TOO LONG is a server-side error, as previously mentioned. This means that you — the website owner or webmaster — are the only one who can address the problem using one of the solutions mentioned below.

Solution 1: Configure the Listening Port

All traffic between a browser and your server is routed via port 80 (also known as the “listening port”) if you don’t have an SSL/TKS licence. When you instal an SSL certificate on your server, it allows you to use the protected HTTPS protocol by enabling port 443 for data transmission.

If your SSL certificate isn’t properly configured to support the use of port 443, any web traffic for the domain would encounter difficulties.

The TLS/SSL certificate can be configured in a number of ways on each server. The links for Apache and Linux are given below.

In Apache, how do you configure the SSL listening port?
In Linux, how do I set up an SSL listening port?

If you’re using another server, try searching for “Port 443 + HTTPS + Your server name” to find more detail.

Solution 2: Update Your TLS/SSL Library

When your server or device does not support your TLS version, SSL ERROR RX RECORD TOO LONG will appear. This problem can be solved by upgrading OpenSSL’s SSL library. TLS 1.3 is now supported by most browsers, and several servers are working to upgrade to support it. As a result, make sure TLS 1.3 is turned on.

At the very least:

Make sure you’re at least supporting TLS 1.2, and switch off any obsolete versions (like SSL 3.0 and TLS 1.0, and TLS 1.1 after March 2020) right away.

A Final Thought

Be vigilant if you are a website user who has chosen to use some unsecured solutions to access the website. On such a website, do not post any financial details, such as credit card numbers or bank account numbers, or any personally identifiable information (PII), such as an email address, phone number, physical address, or social security number.

When you force your browser to ignore SSL ERROR RX RECORD TOO LONG, you’ll be visiting a website that isn’t encrypting your data, rendering it vulnerable to data theft and man-in-the-middle attacks.

Categorized in:

Tagged in: