Redirect HTTP to HTTPS by default for new domains added

[alexafi]

Hello team,

I don’t know if this is normal but the option to redirect HHTP to HTTPS by default is no longer available as in my screenshot above in: Virtualmin / Systems Settings / Virtualmin Configuration / Tab: Category configuration: SSL Settings / Redirect HTTP to HTTPS by default / check: yes

Do we now have to enable this independently on each virtualmin domain? in: Virtualmin (domain choice) / Server Configuration / Website Options / Redirect all requests to SSL site / Check: Yes

like in the screenshot above:

SYSTEM INFORMATION
OS type and version	Debian 10/11
Virtualmin version	7.5

[Randomz]

Try this: Virtualmin, System Settings, Server Templates, Website for Domain, Redirect all HTTP requests to HTTPS.

You have to scroll down to the very bottom.

[alexafi]

Thank you for your reply,

I saw this parameter as you said

I just tested it works fine with Virtualmin and Apache, but not with Virtualmin NGINX (after installing with the --bundle LEMP option it doesn’t seem to work).

With Vitualmin Apache:
When you activate the box in Virtualmin / System Settings / Server Templates / Website for Domain / Redirect all HTTP requests to HTTPS >> Then >> the “yes” box is activated for a new domain added in Virtualmin / Server Configuration / Website Options / Redirect all requests to SSL site

With Vitualmin NGINX (install option --bundle LEMP):
When you activate the box in Virtualmin / System Settings / Server Templates / Website for Domain / Redirect all HTTP requests to HTTPS >> Then >> the “No” box is always activated for a new domain added in Virtualmin / Server Configuration / Website Options / Redirect all requests to SSL site

I tested this on several Virtualmin Apache and NGINX servers

I don’t know if this is an oversight by the Virtualmin team, but it doesn’t seem normal to me, what do you think?

[Randomz]

I haven’t tried NGINX, so this is probably a question to @staff .

[Joe]

If it’s handled via an htaccess file (I don’t think it is, but it might be), then nginx doesn’t support htaccess files…so, that would explain it.

Might also be a bug, since I don’t think we use htaccess for this.

[Jamie]

This is a bug - that template option isn’t being respected in Nginx. It will be fixed in the next release of the Nginx SSL plugin though…

[alexafi]

Thank you all for your feedback.

@Joe: yes the .htaccess type file is not managed by NGINX that’s a fact.

@Jamie: Thanks for confirming the bug, and I’m glad I identified this for all, do you have an approximate date of the next release that will fix this NGINX SSL bug?

Good day.

[Jamie]

I’ve tagged version 1.19 for release. @Joe will this get build and pushed automatically?