Skip to main content
Solved

Configuring HTTPS using a PFX or P12 Certificate -- localhost insecure

  • December 14, 2022
  • 1 reply
  • 151 views

Forum|alt.badge.img+1

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?

Best answer by mattmatsafe

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.

View original
Did this help you find an answer to your question?

1 reply

mattmatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • Best Answer
  • December 19, 2022

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.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings