Here we can see, “How to Fix: SSL_ERROR_RX_RECORD_TOO_LONG”
That’s because the target secure server’s SSL traffic isn’t configured appropriately. This error can also occur if a proxy is set incorrectly to allow SSL handshakes on port 443.
The browser cannot validate the secure data, usually due to an incorrectly installed SSL certificate. This problem is more common on Firefox than on other browsers.
There will be two categories of people reading this article: regular users accessing websites and users running servers and diagnosing the issue. We have given solutions for both types, with “for advanced users” written in front of the title. Look!
Solution 1: Using HTTP to enter the site
The most straightforward approach for users is to use HTTP instead of HTTPS. SSL certificates and a secure handshake are required for HTTPS. If the secure method fails on the server, you can still access the website using HTTP.
- Open your browser and type the website’s address. Most browsers automatically set the protocol to HTTPS.
- Set the address line to HTTP.
- Try again to access the website and see if the error persists.
- Disabling Proxy in Firefox
- The majority of users experiencing this issue are using Firefox. For many users, deactivating all proxies fixed the problem. No proxy does not mean “auto-detect proxies on this network”.
Solution 2: Disabling Proxy in Firefox
- Open Firefox, select “Options” from the menu in the top-right corner.
- Go to the menu and select “Network Proxy”. Click it and choose “No proxy”.
- Save and relaunch Firefox. Inspect the problem now.
Solution 3: Disabling AV
Antivirus software on your computer may cause this error. It also monitors network traffic and verifies all certifications.
This approach requires you to go into your antivirus settings to determine if they provide these services. For example, “HTTP scanning in AVG”. Disable all protections and reconnect to the website.
If you can’t fix the problem, you can disable the antivirus. Check out our post on Disabling Antivirus. After disabling, restart your computer and check if you can access the sites.
Solution 4: Disable TLS 1.3 (for advanced users)
Another solution is to disable TLS 1.3 in Firefox. If this doesn’t work, you can change the settings.
- Type about:config in Firefox’s address bar.
- Now, look for “tls.version.max”. Change 4 to 3.
- TLS 1.3 is represented by 4 and TLS 1.2 by 3. Restart the browser to see if that helps.
Solution 5: Additional Firefox Troubleshooting
You can also attempt the remedies for your Firefox browser given below. Our website shows you how to do it.
- Clear your cache and update Firefox.
- Disable all Firefox add-ons.
- Restart your browser. Note that your bookmarks may be lost now.
- Set tls.version.max to 0
- If none of the above procedures works for your Firefox, try using a different browser like Chrome.
Solution 6: Changing the Certificate (advanced users)
A simple fix for this issue is to change specific server certificate values. We’ve given some code as an example.
Here you have to change the default:443 to example.dev:443.
Solution 7: Changing nginx.conf files (for advanced users)
You may also try altering the nginx.conf file to fix the error. This approach is for sites running on Nginx. The same technique applies when adjusting the 443 port.
To assist you in understanding below is a bit of code containing the workaround.
Change listen 443 to listen 443 ssl. Remove the line “ssl on;”. Inspect the problem now.
If this link is missing and you wish to compel phpmyadmin to utilise SSL/https, use a2ensite default-ssl.
Solution 8: Extra checks (for advanced users)
Along with the above solutions, you must additionally verify the following.
- The server should have port 443 open. This is the https standard port.
- Firefox may show this error if the SSL isn’t standard. Make sure it’s on port 443.
- If you are using Apache2, make sure the SSL port is 443. Set the httpd.conf file as follows:
- 80 Listen 43 https
- Verify that the SSL certificates are valid.
- Apache2 users should examine their vhost.conf. Changing _default_ to _virtualHost> fixed the error.
- Also, just one SSL certificate per IP is recommended. Assign each SSL certificate its dedicated IP.
- Check that the SSL configuration instructions (SSLEngine On, SSLCertificateFile filename>, etc.) appear in the VirtualHost directive for the website or in the SSL configuration file for the server.
What does SSL Error rx record too long mean?
This issue occurs only in Mozilla Firefox. It’s a typical mistake caused by SSL certificate difficulties. This means a connection was made, but no certificate was configured for the port. So the request fails.
How to fix a secure connection in Firefox.
- Firefox. Enter about:config in the address bar.
- The warning page appears. Click on I accept the risk.
- Security. ssl
- Reconnect to the website to see if the issue has gone.
How to enable sslv3 in Mozilla?
- New Firefox tab
- Type about:config in the address bar.
- Could you take it?
- Then type security.tls in the search bar. Delete security.tls.version.min. Then reduce the value from 1 to 0. Set unrestricted rc4 fallback to true.
What is an SSL certificate?
An SSL certificate authenticates a web site’s identity and enables encrypted communication. An encrypted link between a web server and a web browser is created via SSL (Secure Sockets Layer).
This site cannot provide a secure connection.
Problems with the SSL certificate cause “This site can’t provide a secure connection”. In other words, the site claims to be HTTPS-compliant but either doesn’t provide or uses an incorrect certificate.