I updated the certificate on an IIS server. Edge accepts the site, but Chrome still shows Not Secure even though it displays the new certificate. What should I check?
Why does Chrome still say not secure after an SSL update?
Answers
Start with the exact warning Chrome gives you. A certificate trust error and a page that loads over HTTP or includes insecure content are different problems, even if both end up looking like a security warning.
Check that the address is using HTTPS and that the certificate covers the hostname you opened. If the page loads, look for mixed content warnings in Chrome's developer tools. Seeing the new certificate alone doesn't tell you why the page is marked insecure.
Reply to this answer
Check the certificate chain, not just the leaf certificate. IIS needs the appropriate intermediate certificates installed so it can send a usable chain to clients. Edge working doesn't prove that Chrome can build and trust the same chain.
If the site is publicly reachable, run it through a public TLS testing service and look at the chain it receives. For a GoDaddy or Starfield certificate, check the issuer's current IIS instructions carefully. An R1 root and cross-signed chain can require particular attention, and an installed self-signed root can affect which chain Windows builds. Don't change the trust store blindly. Compare the chain being served with the issuer's instructions first.
Reply to this answer
Try a fresh private Chrome session, then restart Chrome completely if the warning changes. Cached browser or SSL state can muddy the picture after a certificate replacement, but I wouldn't assume caching is the cause without checking the actual error.
Reply to this answer
Is there a load balancer or another TLS endpoint in front of IIS? Check the certificate and chain at the address users actually visit, not only on the server. Different endpoints could be serving different configurations.
Reply to this answer
Add your answer
Answers are reviewed before publication.
b.782!claymaraca:
Also check the certificate dates and hostname in the test results. That helps distinguish a chain problem from the wrong certificate being served.