Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I am having a problem with understanding/setting up wildcard SSL certificate. The scenario is this:

example.com(HTTP) domain is hosted by third party company and as it does not provide specific features I have set up separate box a.example.com(HTTPS). This box has SSL certificate (for a.example.com) and is working fine. Now, there is a need to have b.example.com(HTTPS), c.example.com(HTTPS) etc. all working as SSL. They all will be sitting on the same box (a.example.com).

As I don't have any access and control to example.com server I have generated wildcard SSL request for *.example.com from a.example.com server. I have received certificate but I'm unable to apply it to b.example.com because "RSA server certificate CommonName does NOT match server name" which in a way makes sense because server name is set to a.example.com. Now, I can't change server name to example.com because this resides beyond my control and I'm not sure if/how to resolve my issue.

Is it possible to have such a scenario where certificate was requested from a.example.com as wildcard *.example com and then applied to a.example.com to be able to handle b.example.com, c.example.com? I am using Apache on Linux and VirtualHost for *.example.com subdomains.

Thanks, Greg

share|improve this question
Is the certificate self signed/own ca, or provided by an external CA? And: are you sure you did not use the parameter *.example.com unescaped in some command line used to generate the csr... and have the shell glob it into something unexpected? –  rackandboneman Jan 11 '13 at 10:50
I've never seen Apache refuse to apply a certificate because it differs from the ServerName in the configuration. When and where exactly does that happen? –  Jenny D Jan 11 '13 at 11:02
After more digging it seems the issue I am having is the fact (apart from lack of the knowledge ;) that I had ssl certificate for a.example.com alreday working, but when I tried to add another I was trying to use both certificates and it seems like I shouldn't do this. So I think that the error was actually something else. What I am doing now is making sure a.example.com is using wildcard certificate as opposed to the specific one and this seems to be working. So I'm trying to create b.example.com which will also use wildcard certificate and hopefuly this will resolve my issue. –  Greg Jan 11 '13 at 12:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.