Error after Windows 10 Update: The certificate is not trusted because the issuer certificate is unknown.
I came into work this morning to find my Windows 10 computer had restarted due to some updates. I also found that my network adapter wasn't working properly. I managed to get on the network, but I'm having trouble with Firefox. Specifically, one site is giving me trouble: https://store.ancientfaith.com/ This site works fine on other computers running Firefox. Other secure sites work fine on the affected computer (so far). What I get is a message that states:
Your connection is not secure The owner of store.ancientfaith.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.
When I look at Advanced, I see: store.ancientfaith.com uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported. (Error code: sec_error_unknown_issuer)
When I view the certificate, the only item in the certificate hierarchy is the site's cert. When I view it from another computer, or in another browser on the same computer, the hierarchy appears. Otherwise, the certificate information is identical across all computers and browsers.
I've deleted the cert8.db file, and I've done a Firefox refresh. Can anyone suggest a next step?
פתרון נבחר
cor-el said
You can copy the cert8.db file from a working computer to a not working profile or possibly export the involved intermediate certificate and import this certificate.You can use this button to go to the current Firefox profile folder:
- Tools > Options > Advanced > Certificates: View Certificates
- Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
- http://kb.mozillazine.org/Profile_folder_-_Firefox
- https://support.mozilla.org/kb/Recovering+important+data+from+an+old+profile
- http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
This worked. Thank you.
I also alerted the Web site owner to the problem. Thank you both.
Read this answer in context 👍 0כל התגובות (3)
hi, that is indeed an error with the certificate chain that isn't properly implemented by this website: https://www.ssllabs.com/ssltest/analyze.html?d=store.ancientfaith.com
you should get in contact with them and report this issue, as at the moment it will depend on chance if it works when you visit the site with firefox (or to be more clear, it depends on if a particular firefox installation has come across another site before, that has properly implemented the "RapidSSL CA " intermediate cert, as this would get stored in the cert8.db file)...
You can copy the cert8.db file from a working computer to a not working profile or possibly export the involved intermediate certificate and import this certificate.
- Tools > Options > Advanced > Certificates: View Certificates
You can use this button to go to the current Firefox profile folder:
- Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
- http://kb.mozillazine.org/Profile_folder_-_Firefox
- https://support.mozilla.org/kb/Recovering+important+data+from+an+old+profile
- http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
פתרון נבחר
cor-el said
You can copy the cert8.db file from a working computer to a not working profile or possibly export the involved intermediate certificate and import this certificate.You can use this button to go to the current Firefox profile folder:
- Tools > Options > Advanced > Certificates: View Certificates
- Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
- http://kb.mozillazine.org/Profile_folder_-_Firefox
- https://support.mozilla.org/kb/Recovering+important+data+from+an+old+profile
- http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
This worked. Thank you.
I also alerted the Web site owner to the problem. Thank you both.