Changing the protocol to HTTPS on unconfigured domains for SSL will lead the server to serve the wrong website.
If a website does not have SSL configured for it but still the user entered HTTPS the request will go to the first VirtualHost accepting requests at that port.
Take a look on this post.
http://forum.i-mscp.net/thread-3547-post-16534.html#pid16534
We will invastigate a solution fpr this problem
The problem is very simple... Use a website where ssl is not activated. Call the website with https and the apache will get the first site with the ip of the this website where the port 443 is activated. Then you will see an incorrect ssl cert.
Your idea should be testet or let us test the idea of Cool
hello ;
Something like this added in 00_master_ssl.conf works:
Here, I've hardcoded the host but of course, I'll replace it with placeholder. I don't see any other solution 
I think this is a good solution.
Will you add this to the templates in the next time or is this only a solution for the exsiting problem?
I think this is a good solution.
Will you add this to the templates in the next time or is this only a solution for the exsiting problem?
Well, I'll surely add this statement in template but still that I must do that for each IP which have SSL enabled.
Thumbs up my friend!
After a discussion with our team on IRC, the solution which will be implemented will be as follow:
The error document will show a specific message which will say: SSL NOT ENABLED
please note that this solution breaks openDKIM plugin (error 404)...
SSLRequire ( %{HTTP_HOST} =~ m/^(www.)wheezy.nuxwin.com/ ) looks like the best workarround for the moment...
best regards, julian