Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

“Error code ssl_error_rx_record_too_long” in Webmin – How to fix

by | Jun 3, 2021

Wondering how to fix “Error code ssl_error_rx_record_too_long” in Webmin? We can help you!

This error is often seen while trying to log into a newly installed Webmin.

Here at Bobcares, we often handle requests from our customers to fix similar Webmin errors as a part of our Server Management Services. Today we will see how our support engineers fix this for our customers.

How to fix “Error code ssl_error_rx_record_too_long” in Webmin

Before going into the steps for fixing this error we will see what causes this error.

A typical error looks like the one given below:

An error occurred during a connection to
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)


The error can occur if we do not configure SSL for Webmin and enable it.

Steps for fixing “Error code ssl_error_rx_record_too_long”

Now we will see how our Support Engineers install SSL and enable it on Webmin to fix this error for our customers.

To fix this error, we need to Connect to the URL with http and not https.

Installing  SSL

Following are the steps to install SSL for Webmin:

1. Log in to Webmin and enable/install SSL.

2. Then need to download our certificate and CA bundle from the certificate authority.

3. After downloading it we need to upload the above-mentioned files to Webmin.

4. And click Others, then Upload and Download.

5. After that, choose the Upload to server tab in the main window, then select the files to upload.

6. Then specify the path to store them, and click Upload:

Error code ssl_error_rx_record_too_long Webmin

Configuring Apache using Webmin

Now let’s see the steps for configuring Apache using Webmin.

Error code ssl_error_rx_record_too_long Webmin

1. First, click the Apache Webserver entry in the Servers menu and choose the Global configuration tab:

Error code ssl_error_rx_record_too_long Webmin

2. Then press the Configure Apache Modules icon:

Error code ssl_error_rx_record_too_long Webmin

3. From the list of Apache modules, find the SSL entry, check the box and press the Enable Selected Modules button:

Error code ssl_error_rx_record_too_long Webmin

4. After a few seconds, we will be prompted to the Apache Webserver’s main page. We have to choose the Create virtual host tab there.

5. We have to specify port 443 after putting the radio button near the blank field in the Port section, enter the path to the document root folder in Document Root.

6. And type in the domain name in the Server Name section.

7. Then press the Create Now button to add a new virtual host:

Error code ssl_error_rx_record_too_long Webmin

8. In the newly opened Existing virtual hosts tab, we must click on the globe button next to the virtual host that we have just created:

Error code ssl_error_rx_record_too_long Webmin

9. After that, find and click on the SSL Options icon in Virtual Server Options:

Error code ssl_error_rx_record_too_long Webmin

Adjust SSL options

We can adjust the SSL options in the following way:

1. Enable SSL? – select Yes

2. SSL protocols – make sure to uncheck SSLv2 and SSLv3 as these protocols are considered to be unsecure

3. Certificate/private key file – the path to the uploaded example_com.crt file Private key file – the path to the private key file that was initially generated with the CSR code; used for the certificate activation

4. Certificate authorities file – the path to the uploaded file.

5. Press the Save button to update the SSL settings:

Error code ssl_error_rx_record_too_long Webmin

6. In order to apply all of the changes we have made so far, we need to restart Apache.

7. To open the needed page, we can press the Bootup and Shutdown entry under the System menu.

8. From there we can find the apache2 service, and check the corresponding checkbox on the left:

Error code ssl_error_rx_record_too_long Webmin

9. After that, scroll down to the bottom and press the Restart button:

Error code ssl_error_rx_record_too_long Webmin

Enable SSL

For enabling SSL we can use the following steps:

1. Log in to the Webmin dashboard.

2. After that select Webmin, then Webmin Configuration.

3. Then we have to select SSL Encryption.

Error code ssl_error_rx_record_too_long Webmin

4. Now, toggle Enable SSL?

5. Finally click Save and Refresh Webmin then log back into Webmin.

[Still, stuck with the error? We can help you]


In short, we saw how our Support Techs fix “Error code ssl_error_rx_record_too_long” in Webmin.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.