Submitted by Dr. Moe on Thu, 07/18/2013 - 01:21
OS: Debian 7.0 / Wheezy
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.
Virtualmin actually creates a NameVirtualHost entry upon site creation, using whichever address is found in the Virtualmin Module Configuration / Network Settings page.
Is there any way to configure Virtualmin so that SSL virtual servers are created using a wildcard, as in 'VirtualHost *:443' ?
I did ask for help in the forums (https://www.virtualmin.com/node/28838), but the advice I received did not survive testing :-(
Status:
Closed (fixed)
Comments
Submitted by andreychek on Thu, 07/18/2013 - 07:57 Comment #1
I've responded to your forum post.
Submitted by Dr. Moe on Thu, 07/18/2013 - 08:57 Comment #2
Hi,
Thanks for the answer.
Unfortunately, the workaround will not do. I explained the reasons in my reply to your comment on the forum post. It just has to be '*.443' :-(
Can this be achieved ?
Submitted by andreychek on Thu, 07/18/2013 - 09:11 Comment #3
I'll respond in to your Forum thread -- let's continue the discussion over there.
Submitted by JamieCameron on Fri, 07/19/2013 - 03:54 Comment #4
If you add the line
NameVirtualHost *:443
to your Apache config before creating a domain, Virtualmin should use *:443 in theVirtualHost
block.Submitted by Dr. Moe on Fri, 07/19/2013 - 04:32 Comment #5
Hi Jamie,
Thanks for taking the time to answer.
As you say, it should. I believe the reason why it didn't is mostly due to my environment, as explained in the forum posts.
Eric helped me work out the problem, by adapting the advice he gave in his reply to the post.
It wasn't '*:443' in the end, but full functionality is back :-)
There also remains a side-issue, once more probably environment related, and as suggested before I assume we can pursue this conversation in the forum.
Thanks again for all the help :-)
Cheers