On Windows 7 with Chrome 30. I have a few websites running on localhost over SSL. Visiting them always displays the standard "The site's security certificate is not trusted!" message from Chrome.
I exported the certificate from one of the sites in question and then, using the Certificate Import Wizard, imported it into Trusted Root Certification Authority. I double-checked in certmgr.msc, and the certificate is there as expected. After restarting Chrome, I still receive the same certificate error message as before.
I've tried different certificate file formats, but all exhibit this behavior. What else could be the problem?
hostname
field in certificates. The hostname (FQDN or IP address) should be specified insubjectAltName
extension field orsubject
field and itsCN
identifier. ------ Browsers usually show reasons for rejecting a certificate. For example Firefox writesadobe.com uses an invalid security certificate. The certificate is only valid for www.adobe.com (Error code: ssl_error_bad_cert_domain)
. In your case the message really shows that the CA which issued the certificate is not trusted. Chrome should use the "Trusted Root Certification Authority" Windows store.subject
field in the cert is the name of the application running the webserver (CN = MyApp
), but the hostname I use to connect islocalhost:9090
. Chrome gives 3 detail errors:Server's certificate does not match the URL, Server's certificate is not trusted, Server's certificate is signed using a weak signature algorithm.
IE10 exhibits the same behavior.