We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

This Connection is Untrusted; Issuer unknown

  • 1 antwurd
  • 4 hawwe dit probleem
  • 2 werjeftes
  • Lêste antwurd fan m60freeman

m60freeman
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?

Keazen 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.

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (1)

m60freeman
m60freeman Fraacheigener
more options

Keazen 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.