Issue SSL error when main domain has been changed

[Brian-Dmac]

Hi,

I'm having an issue with an SSL not applying to a standalone domain. Initially the subscription was setup with domain A, but then changed to domain B. We added domain A as an alias but ran into issues with SSL certificates only applying to Domain B. I deleted the alias and added Domain A as a standalone domain with it's own SSL cert, however the SSL certificate for domain B is still applying. All of the settings in plesk look correct and I have tried rebuilding configuration files but domain A still throws up a warning saying the SSL is only valid for domain B

Any ideas?

B

 

[Kaspar]

Based on your post it isn't entirely clear to me how you've exactly setup those domains (and how they relate to each other) in your current configuration. In general however, when you add an alias to an existing domain you'd have to re-issue the certificate to include the domain alias in the certificate too. If you're using Let's Encrypt certificates you can re-issues the certificate in Plesk. If got your certificate somewhere else you have re-issue the certificate with the certificate provider.

If you have now setup these two domains separately in Plesk, you also have need to issue two separate certificates (one for each domain). If you use Let's Encrypt you can do so via Plesk. Otherwise refer to you certificate provider. If you already have issued two separate certificates (one for each domain), but certificate for domain B is used domain A, you might want to check if the right certificate is selected in the Hosting Settings of the domain.

 

[Brian-Dmac]

Hi Kaspar, thanks for the reply

Domain A is the main domain on the subscription and has an SSL with the correct common name.
Domain B is an additional domain on the same subscription with it's own SSL with the correct common name.
When I visit Domain B I get an warning saying the cert is only valid for Domain A - this is persistent on multiple machines across different networks.
I've checked the conf files on the server and both domains reference separate certificate files on the server and I parsed the certificate file for Domain B and it is correct.
Even when I view the SSL manager for Domain B in Plesk it shows a green tick and "Secured" beside the domain

I've managed to workaround the issue for now by removing Domain B from the subscription and adding it as a new subscription with forwarding to Domain A. The server is now serving up the correct SSL cert but having the extra subscription is not ideal.

I think the issue is related to the changing of the subscription domain (as mentioned, initially the client wanted Domain B but changed to Domain A with B as an alias) as I know in the past it was not recommended to do this. At one point there was only one SSL which only covered Domain A and it seems as though there is a conf file which hasn't updated or config which has been cached. I've restarted all services but have not tried a full reboot as there are a lot of sites hosted and that would need to be scheduled

it's puzzling!