How to FIX SSL_Error_rx_Record_too_long in Firefox
The most common issue on Mozilla Firefox browser happens as a result of wrong configuration of your certificate on the web hosting server. The port a client is trying to connect to is opened on the server, however, no properly configurated SSL certificate found for this port on the server's side. Don't worry, we prepared multiple working solutions to fix SSL_Error_rx_record_too_long error.
You can confirm the problem using OpenSSL command:
openssl s_client -connect domain.tld:*port*
You will receive the following output if error confirms:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:766:
The result shows that the connection is successful, however, handshake failed as no configurated SSL certificate found for the port and connection was terminated. We prepared couple of solutions to fix SSL_Error_rx_record_too_long problem, please follow the article.
Solution 1: Try to reset Firefox browser
The good solution to avoid using unwanted browser programs is resetting Firefox to default settings.
- Type 'about:support' in the address bar;
- You will see a troubleshooting window now;
- Click on Refresh Firefox button and confirm the refresh;
- Move to the next solution if that one doesn't help.
Solution 2: Try to update Firefox
- Click to Open Menu > Help > About
- The new window would show is your Firefox browser is up to date or update requires.
- Click on 'Restart to update Firefox' is the update is available.
- Reload the problematic website after update to check if the error is solved.
- Move to the next solution if still same issue.
Solution 3: Try Disabling Browser Extensions
There are hundreds of extensions and some may block/affect your connection. Try to disable them to fix the issue.
- Go to Open Menu -> Add-Ons;
- Beside each extension, you will see the Disable button that you need to click for all extensions.
- Restart the browser and retry opening the website.
Avoid next solutions!
- Try to NOT bypass the security protocol by replacing the URL with the HTTP:// instead of HTTPS://. That is not a safe solution, as starting at 2018 it is standard to use secured connection for all websites.
- Do not turn off your Anti-virus, that is a really bad idea. It is duty of webmaster to setup website properly, not yours to avoid problems.
Conclusions to summarize
- For website owners. Check your server configuration. Check your SSL certificate and server with SSL Labs online tests, as maybe you need to use a proper and professional SSL certificate.
- For website visitors. Avoid using the website if error not solved even after listed solutions. It is unsafe to use sites like that, the best what you can do is to contact webmasters / site owners and let them fix it.