This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

This Connection is Untrusted; Issuer unknown

  • 1 antwoord
  • 4 hierdie probleem
  • 2 views
  • Laaste antwoord deur m60freeman

more options

The site is https://dvd.netflix.com. Entering that into chrome://pippki/content/exceptionDialog.xul gets me the message "The certificate is not trusted because it hasn't been verified as issued by a trusted authority using a secure signature."

The certificate was issued by:

CN = Symantec Class 3 Secure Server CA - G4 OU = Symantec Trust Network O = Symantec Corporation C = US

The validity dates are in range (7/9/2015 - 7/10/2017) and my PC's clock matches my cell phone.

How can I fix this?

The site is https://dvd.netflix.com. Entering that into chrome://pippki/content/exceptionDialog.xul gets me the message "The certificate is not trusted because it hasn't been verified as issued by a trusted authority using a secure signature." The certificate was issued by: CN = Symantec Class 3 Secure Server CA - G4 OU = Symantec Trust Network O = Symantec Corporation C = US The validity dates are in range (7/9/2015 - 7/10/2017) and my PC's clock matches my cell phone. How can I fix this?

Gekose oplossing

Exiting Firefox, deleting cert8.db from the profile folder, and then restarting Firefox seems to have resolved the problem. (I found this in the reply to a post on a similar problem.

Lees dié antwoord in konteks 👍 1

All Replies (1)

more options

Gekose oplossing

Exiting Firefox, deleting cert8.db from the profile folder, and then restarting Firefox seems to have resolved the problem. (I found this in the reply to a post on a similar problem.