up vote 2 down vote favorite
share [g+] share [fb]

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

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

link|improve this question
72% accept rate
feedback

2 Answers

up vote 6 down vote

Use a Subject Alternative Name in the SSL cert to cover the non-subdomain name (mydomain.com). For an example see http://therowes.net/~greg/2008/01/08/creating-a-certificate-with-multiple-hostnames/.

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

link|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
feedback
up vote 3 down vote

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

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

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

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

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