Using the instructions, we were unable to use Chrome create the .cer file. We had to use Internet Explorer. In the Verify HTTPS configuration step, localhost produced an insecure connection although using the hostname produced a secure connection. How can this issue be corrected?
Page 1 / 1
Hi @bibold, yes that is expected behavior, because a certificate is for a domain (or all subdomains within a domain, if the certificate is a wild-card certificate). If you click 'certificate is not valid' and view the certificate details, you should be able to see the common name it is issued for. For example, community.safe.com in this site's case. If you want to access localhost on the server machine and don't want to see the warning, you could import the certificate into your Windows Trusted Root Certification Authorities, but generally, it's not an issue, since users are accessing the server from the domain, not localhost.
We realize that UI for Chrome has changed since the HTTPS documentation was last written and plan to update it.