It’s a serious mixup that can bring us many problems… Exemple, if we delete or if we have a problem with 3.test.com, all the others that take their certificates from it will stop to work properly.
So, we need your help to make ALL THE VIRTUAL SERVERS THAT WE WANT, to use their certificates from test.com
Seems that the problem came from virtual server backups that we imported into the new servers (restored virtual servers).
Seems that some old values in a database can not be changed.
Anyway, if i edit the directives of a virtual server and i point the ssl stuff somewhere else, it continu to use the old values taken somewhere that i dont know. I need to know where these values are stored to make modification.
Ok, so, we found that we can fix our problem by ourself IF we can know from where the [ssl_same=] value is taken from when we clone or when we create a virtual server.
There could be a bug in how Virtualmin distinguishes certs separately. It’s weird how my server got messed up considering each virtual server has a separate Apache config file. Suddenly, one pre-existing self-signed cert was being given for all websites and subdomains.
I found that Virtualmin retains the corrupted state even after disabling SSL, so it would be nice to see a certificate cleanup/recheck option added so I can start over. I wouldn’t want to cause chaos by doing some manual editing which conflicts with the state Virtualmin stores in it’s database.