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.

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

This Connection is Untrusted; Issuer unknown

  • 1 răspuns
  • 4 au această problemă
  • 2 vizualizări
  • Ultimul răspuns de 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?

Soluție aleasă

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.

Citește acest răspuns în context 👍 1

Toate răspunsurile (1)

more options

Soluție aleasă

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.