ssl_error_rx_record_too_long and Apache SSL

Still need help?

The Atlassian Community is here for you.

Ask the community

Overview

This error appears most commonly in Firefox browsers, though similar errors can occur in other browsers as well. This may be related to SSL or Proxy misconfigured.

Symptoms

After configuring Confluence or JIRA to work over HTTPS, the following error came up when the user tries to access the site:

ERR_SSL_PROTOCOL_ERROR (Chrome)
ssl_error_rx_record_too_long (Firefox)

In order to test this behavior is attempt connecting to the site from outside the current network with a number of different web browsers. See if the error persists. If the error is not shown, the proxy is possibly misconfigured.

Cause

This error often occurs because SSL traffic is not set up correctly on the target secure server. For instance, the DNS is may not be correct in the DNS name on your VirtualHost. This error can also occur if there is a misconfigured proxy that doesn't allow an SSL handshake on port 443 correctly. 

Resolution

Below are some ways to fix this error:

  • Ensure that port 443 is open and enabled on the server. This is the standard port for https communications.
  • If SSL is using a non-standard port then FireFox can sometimes give this error. Ensure SSL is running on port 443.
  • If using Apache2 check that port 443 for SSL is being used. This can be done by setting the httpd.conf file as it follows
		Listen 80
Listen 443 https
  • Make sure you do not have more than one SSL certificate sharing the same IP. Please ensure that all SSL certificates utilise their own dedicated IP.
  • If using Apache2 check your vhost config. Some users have reported changing <VirtualHost>to _default_ resolved the error.
  • Make sure that your SSL certificate is not expired

 

 

 

Last modified on Feb 26, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.