SSL certificate on the website allows visitors to securely access.

In other words, by typing domain.com in a web-browser, a user should redirect to https://domain.com securely.

For this, there is an advanced feature in Webmin to redirect HTTP to HTTPS by default.

At Bobcares, we often get requests from our customers to set up “Webmin redirect HTTP to HTTPS” as part of our Server Management Services.

Today, we’ll see how our Support Engineers configure redirection in Webmin and fix the top 2 common issues.

How we redirect HTTP to HTTPS in Webmin

To redirect the non-SSL site to SSL site becomes quite easy with the advanced feature in Webmin control panel.

Let’s take a closer look at how we configure redirection to HTTPS in Webmin.

1. First, we logged into Webmin panel.

2. Next, go to Webmin > Webmin Configuration > SSL Encryption .

3. Then, selected Redirect non-SSL requests to SSL mode? to Yes.

4. After that, we go to Virtualmin > System Settings > Virtualmin Configuration.

5. And in the SSL settings column, we selected Yes on the Redirect HTTP to HTTPS by default?.

6. Finally, saved the file.

Now, the users could automatically access the URL without typing http or https in front of the URL.

The top 2 common problems after setting redirection to HTTPS in Webmin

Even after setting HTTPS redirection properly, we often see errors.

Let’s see the top 2 common errors and how our Support Engineers fixed it.

1. Incorrect .htaccess rule in Apache

Recently, one of our customers reported that after setting the redirection and when he tried to access the Webmin URL, it doesn’t seem to work properly. Also, he mentioned that he was using the Apache web server.

So, to fix the problem we took the following steps.

1. First, we logged into Webmin.

2. And we navigated to Virtualmin section.

3. Then we located Configure Websites under Services.

4. Next, we clicked Edit Directives and looked for RewriteEngine On.

5. Then under RewriteEngine On we pasted the rule like

RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [R]

6. Finally, we restarted apache to save the changes made.

/etc/init.d/apache2 restart

Now, the user could automatically access the URL without any failure.

2. Bad settings in Nginx configuration file

Likewise, another customer approached us with the problem after redirection in Webmin has set and when he tried to access the URL it resulted in an error like this

This error normally arises when you do not properly configure Nginx settings to handle both HTTP and HTTPS requests.

So, to solve this error we performed the following steps.

1. First, we opened the Nginx configuration file in vi editor.

vi /etc/nginx/conf.d/default.conf

2. And then we added the following line of codes to the file.

server {
listen 80;
server_name  www.example.com x.x.x.x;
return 301 https://$server_name$request_uri;}

3. Finally, we restarted the Nginx service.

systemctl restart nginx

Now, the user could access Webmin and he no more gets an error like “400 Bad Request: The plain HTTP request was sent to HTTPS port”.

That’s how we fixed the problem.

[Having trouble with Webmin redirect HTTP to HTTPS? We’ll fix it for you.]

Conclusion

To be more precise, for secure websites there is an advanced feature in Webmin to redirect HTTP to HTTPS by default. Today, we saw the top 2 common issues related to Webmin redirection and how our Support Engineers fixed them.