0

I have created a self-signed certificate that works with https://*.blah.com (for example www.blah.com works). I have blah.com listed as a SAN but https://blah.com doesn't work with my web browser.

What's wrong with my cert?

Here's a screenshot of the error:

enter image description here

burnt1ce85
  • 229
  • 4
  • 6
  • how to actually added the SAN on the existing certificate? Or need to reissue back the CSR private key before we generate the certificate. – SUHAIDA SENEN Jun 02 '21 at 08:15

2 Answers2

3

I don't think you added the SAN value properly to your cert. It's not just a string field in the Subject. It's a separate extension that would be listed further down in the cert details like this: enter image description here

Additionally as Rob-d mentioned, the error message the browser gave you is basically telling you that your Common Name (CN) field is invalid (probably because you tried to add an invalid field to the Subject called "Subject Alternative Name").

Ryan Bolger
  • 16,755
  • 4
  • 42
  • 64
0

the error says it has a problem with the common name and not the SAN, the common name is * - this is a wildcard certificate, also you would not need to name any subject alternative names when using a wildcard cert.

Sum1sAdmin
  • 1,934
  • 1
  • 12
  • 20