New virtual servers with ssl enabled cause all other virtual servers to use the new virtual server's ssl certificate

Hi there,

Since last week, a problem has occurred which brings down all the secure virtual servers on my web server.

Steps to reproduce: 1. Create a new virtual server with ssl feature enabled

Result: All secure virtual servers use the newly created virtual server's ssl certificate, instead of their own.

Last week, I cloned the server to a new instance, made some changes to the new instance and then repointed the elastic IP address at the network card of the new instance. It seems that since then this problem is occurring but I am not sure it is relevant.

Thanks, L

Comments

Do the other virtual servers have SSL enabled? Because if you use an https: URL to access a domain that doesn't have SSL on in Virtualmin, you will get the website of the first domain that does have SSL enabled.

VuOnline's picture
Submitted by VuOnline on Wed, 01/11/2017 - 04:13 Pro Licensee

Yes, the virtual servers which have SSL enabled are the only ones affected.

If a new virtual server is created, with SSL enabled, all other virtual servers with SSL enabled will go down because they will start using the SSL certificate of the new virtual server, which will be invalid for them.

Mostafa's picture
Submitted by Mostafa on Wed, 01/11/2017 - 11:32

There might be an IP mismatch here, what do you get by running:

Debian:

grep -R "443" /etc/apache2 | grep -i "virtualhost\|listen"

Centos:

grep -R "443" /etc/httpd | grep -i "virtualhost\|listen"