Hi All,
Hope that some of you have already come across this issue.
It’s 2013 and SNI is now supported by most major browsers.
Yet, Virtualmin will create VirtualHosts that support SSL as: xx.xx.xx.xx:443.
Wile this may be perfectly applicable in most setups, it seems to bring quite some confusion when the Virtualmin host is an Open VZ virtual machine behind DNAT and /or when apache already uses *:443 elsewhere.
In such a setup, where the Virtualmin host is configured with an internal LAN address and the Virtualmin module is configured to create sites over the external IP address ‘DNATed’ to the Virtualmin Host, the first SSL site takes precedence in the order shown by apache2ctl -S.
According to some quick tests, changing all Apache vhosts to use external_ip:443 (and external_ip:80) does not solve the issue.
On the other hand, setting all vhosts to reference *:80 and *:443 works like a charm.
Unfortunately, I have failed so far to find how to configure Virtualmin so that it will automagically create SSL sites as <VirtualHost *:443>.
Does anyone know if such a configuration setting would actually be available ?
If not, might there be a way to modify the xx.xx.xx.xx:443 vhosts created by webmin using some built-in automation ?
Obviously, I would very much prefer not to set up a system-wide shell script in a cron job, since it’as a waste of resources and implies a delay for end users.
Has anyone managed to create SSL sites as ‘*:443’, or may anyone direct me towards the relevant config entries ?