Firefox Error Code: ssl_error_rx_record_too_long

Not happy with your web hosting service provider?

TRY YOUSTABLE

Firefox Error Code: ssl_error_rx_record_too_long

If you have a Firefox browser that has an error on the screen, while accessing your site after changing from HTTP to HTTPS, then you have a serious problem here. First, try to test the site on the Chrome browser and Edge browser to confirm that the problem persisting from your end.

Step 1: Go to the testing site, and enter the URL of your site, and click on “or just me” to start testing the portal.

ssl_error_rx_record_too_long

Step 2: Our site is up and running, and if you have the same result on the screen, then clean the browser cache.

ssl_error_rx_record_too_long

In case, if the result says “your site is down,” then move on to the next solution.

Other Similar Error ssl_error_rx_record_too_long

  1. (Error code: ssl_error_rx_record_too_long)
  2. An error occurred during a connection to <server-name>.
  3. Secure Connection Failed.
  4. SSL received a record that exceeded the maximum permissible length.

Reason

Firefox browser is expecting HTTPS data from the server, but the wrong configuration is sending HTTP data to the browser. The browser has security responsibilities that they cannot avoid, so they block it, and we have (Error code: ssl_error_rx_record_too_long) on the screen.

Solution

The error happens, when you have not configured the SSL properly in Apache or Tomcat. It is one of the well-known common issues found in Apache or Tomcat as the webserver. Allow us to show you both solutions on both platforms.

Tomcat Web Server:

In Tomcat, open the file “server.xml,” and you should find the code (scheme=”https” secure=” true”) with Keystore file and keystorePass statements.

Now, you have to check, whether port (8443) default is in the file, and then you have to specify it as part of the URL. Tomcat web server might be switching to HTTP/non-secure mode, and the Keystore is corrupted. Create a new Keystore and replace the SSL certificate.

Apache Web Server:

In Apache, the VirtualHost directive and SSLCertificateFile configuration statements should match with each other.  First, check if the “Listen <port> directive” port number matches with the “VirtualHost directive.”

Also check the configuration of “SSLEngine On, SSLCertificateFile <filename>, etc” in the VirtualHost directive. Misconfiguration is the culprit for the Error code: ssl_error_rx_record_too_long!

Leave a Comment