Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've created a self-signed certificate via openssl for *, and it works e.g. for However, when I go to directly in Chrome, I get an error (You are attempting to reach, but instead you actually reached a server identifying itself as *

Should the *. certificate cover the main domain as well? What should I do to resolve?

share|improve this question

Use a Subject Alternative Name in the SSL cert to cover the non-subdomain name ( For an example see

I'm not sure why Jan's answer got downvoted, as it correctly diagnoses the problem, even if it doesn't give a fix.

share|improve this answer
Thanks, I'll give it a try. I didn't downvote @Jan's answer, in any case. – ripper234 Oct 5 '11 at 22:33

You would need to get a cert that supports multiple domains.

* does not cover as it will only cover subdomains of eg.

You could always redirect users who go to to and then the cert will work.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.