I have a strange problem with all the domain-names on my server. When visiting the domain-names url with https://www.sitename.someting they are now all matched to the latest added ssl domain (hocom-advies.nl).
Before they were working fine. Also before adding the new hocom-advies.nl ssl, the server ip-address was resolving tot a standard html-page living in /var/www/ or to phpmyadmin. piwik location
like this: 126.96.36.1997/phpmyadmin/ now ending up at hocom-advies.nl ?
So for instance if you visit https://www.pizzajolly.nl it says not secure and the certificate is matched to:
www.hocom-advies.nl . just www.pizzajolly.nl or https://pizzajolly.nl or pizzajolly.nl are fine!
HocomAdvies is the latest ssl certificate generated. Searching for a solution or something that causes this behaviour some questions came up:
I’m sure my vhosts in apache2 are all good. Could there be an problem in the DNS record? For hocom-advies.nl there is an A record holding: *.hocom-advies.nl
Can that make the other domains redirect to hocom-advies.nl ? giving the certificate error?
Also I am wondering if the order of domain names when creating the ssl certificate matters?
This is what I used for generating the latest domain-name and for all the others generated before:
certbot certonly --webroot -w /var/www/www.hocom-advies.nl/www -d hocom-advies.nl -d www.hocom-advies.nl
My apache2 vhosts 80 are holding a redirect to https://
So what is the problem here? The DNS setting? Any idea how to solve this en having the url for all individual domains working again without matching to the wrong certificate!