Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Learn More

This Connection is Untrusted; Issuer unknown

  • 1 απάντηση
  • 4 έχουν αυτό το πρόβλημα
  • 2 προβολές
  • Τελευταία απάντηση από 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?

Επιλεγμένη λύση

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.

Ανάγνωση απάντησης σε πλαίσιο 👍 1

Όλες οι απαντήσεις (1)

more options

Επιλεγμένη λύση

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.