Q: Wrong SSL Certificate for Websites
I had an SSL certificate installed (for example.com) on my server and recently decided to change my server's hostname (to ch.ex.com). I added an additional SSL certificate for the new hostname and setup the server to use this new SSL certificate for server management and most of the other services. For websites, I still want host sites at both hostnames (different sites for different host names by the way, not duplicate sites) so in the certificates section of the Server.app I set the server to use the example.com SSL for all example.com sites and the other SSL certificate for all other services.
I tested this by opening example.com on another computer (on an external network) and it is telling me the certificate is invalid because of a hostname mismatch. After further inspection, it appears to be using the ch.ex.com SSL certificate when I navigate to example.com. I opened the Server.app again and it still is configured to use the example.com certificate for the example.com sites both in the certificate's tab (within the "custom" configuration) as well as in the websites tab in the specific site's certificate settings.
Is there somewhere else I need to configure settings for which certificate is used for a Website? Or is there something I am doing wrong?
Posted on Mar 12, 2016 7:10 PM