Clever Geek Handbook

Error ssl error rx record too long: reason

After installing the SSL certificate, when connecting to the server using a browser, the following error message may appear: “Failed to establish a secure connection. Error connecting to <server-name>. SSL received a record that exceeded the maximum allowable length. SSL_error_rx_record_too_long. ”

Cause

The web server sends insecure HTTP data that expects secure HTTPS data. This can be confirmed by going to the address “http: // server-name: 443” instead of “https: // server-name”. A valid web address is very important.

ssl error rx record too long

SSL_error_rx_record_too_long: setting permissions

Check the server configuration to verify that SSL is configured correctly. This is most often the case when using Apache or Tomcat as a web server, although this can happen on other types of servers.
Questions to consider when resolving this error in Apache or Tomcat:

  • In Apache, verify that the Listen <port> directive matches the port number in the VirtualHost directive for the secure website and that the configuration instructions (Engine On, CertificateFile <file name>) appear in the VirtualHost directive for the website or in the configuration file for the server.

  • In Tomcat, verify that the connector in server.xml is configured to use SSL (there must be a scheme = "https" secure = "true", as well as the keystoreFile and keystorePass statements) and that the port number specified in the connector is what is expected. If you use the default port (8443), you must specify it as part of the URL or redirect it to the server. Tomcat can also switch to unsafe mode for a socket where the keystore is damaged. Try creating a new keystore and replace the certificate.

    ssl error rx record too long

Error ssl error rx record too long. Different variants

Also in the browser you can see the ssl_error_rx_record_too_long message when visiting a website via HTTPS. It comes down to an error in the implementation on the server.

To fix this problem, you must carefully study the following options as prerequisites:

  • Port 443 must be open and accessible on the web server.

  • Firefox 3 may show this error when using a different port than 443.

  • Apache 2.x must be configured to use port 443.

  • Each site using SSL must have its own IP address or use SNI.

The ssl_error_rx_record_too_long message may occur when using a proxy server that is configured incorrectly.

More articles:


All Articles