2

I have a webserver and its domain name is foo.com, if I access the site in https://foo.com I will receive the warning from Chomre browser.

NET::ERR_CERT_COMMON_NAME_INVALID

I searched the web and found this link saying domain names should follow the specified CN on the certificate. I checked that my certificates CN is actually www.foo.com so when I access the site using https://www.foo.com I am not shown that warning message.

However I can't advise users or customer who will be accessing this site to just type https://www.foo.com so they won't get the warning message. CAn you suggest a solution so that people accessing this site will not be thrown that warning message? Do I need to get another certificate for this or there is just an internal configuration I need to do. I am running a .net application and its using IIS 7.5.

2

Get a new cert for foo.com (or *.foo.com if you are sending people to other subdomains within foo.com).

| improve this answer | |
  • can I ask comodo or any Certificate authority to issue an *.foo.com certificate? – dimas Jun 8 '15 at 14:36
  • You can. I've never directly worked with our CA, but we use wildcard domains in our certs and use a well-known CA, so I know it's possible. – ztk Jun 8 '15 at 14:38
  • *.example.com does not match example.com – Hyppy Jun 8 '15 at 14:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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