I want to create a self-sign certificate on a Windows Server 2012 R2, just to test and try it.

I have no error on my certificate information but when I browse to http://localhost, I see the browser red bar, meaning something is wrong with the certificate.

Browser warning (red bar)

I tried many references like this, but I can not find my mistake.

Is that a way to see logs or trace errors?

  • 1
    The very nature of a self-signed certificate is that it's untrusted by the browser, because it's not signed by a legitimate CA. You can opt to explicitly trust one on a per-certificate basis. Any difficulties with that process are off-topic here, and should be directed somewhere like SuperUser with specific details on what you've attempted. – ceejayoz Jul 13 '16 at 15:18
  • @ceejayoz ,then why this option is available on windows?when browsers never trust to this types of ssl or.... – motevallizadeh Jul 13 '16 at 15:22
  • 1
    Self-signed certs are perfectly fine for local development work. – ceejayoz Jul 13 '16 at 16:27

The certificate was not issued to localhost. The certificate was issued to WIN-CN2DB9TT88P. Those are not the same. Browsing to http://localhost in your web browser is not the same as http://WIN-CN2DB9TT88P. You can trust a self-signed certificate if you want to, just by importing the cert into your Trusted CAs store, but it's only valid for the very specific name that is on the certificate.

  • When i created this certification there was not any option to select "issued to", how can i handle it? – motevallizadeh Jul 13 '16 at 15:28
  • 1
    @motevallizadeh Just use your favorite search engine. No rocket science involved. – gf_ Jul 13 '16 at 15:32

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