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!

לאתר זה תהיה פונקציונליות מוגבלת בזמן שאנו מתחזקים אותו לשיפור החוויה שלך. אם מאמר מסויים לא פותר את הבעיה שלך וברצונך לשאול שאלה, קהילת התמיכה שלנו מחכה לעזור לך ב־Twitter תחת ‎@FirefoxSupport וב־Reddit תחת ‎/r/firefox.

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

SSL certificate error - when the site is correct and works fine for other users using the same version - seems to be a random issue with latest build.

  • 3 תגובות
  • 29 have this problem
  • 1 view
  • תגובה אחרונה מאת ktroutman

more options

Gets SSL invalid *This connection is untrusted.

Valid certificate - is a wildcard certificate, name match's destination. Worked without any issues in the older version of FireFox.

Gets SSL invalid *This connection is untrusted. Valid certificate - is a wildcard certificate, name match's destination. Worked without any issues in the older version of FireFox.

כל התגובות (3)

more options

That certificate was just issued on July 16th. I wonder whether there was an old version cached on the problem PC or some other issue with the chain of trust up to the trusted root certificate?

more options

Hello, just wondering if anyone has found a solution for this? I'm running into the same problem with sites that I host with a valid VeriSign SSL wildcard certificate. It doesn't matter if the sites are on Apache or IIS, same error. IE and Chrome see the certificate fine. Firefox versions from 3.5 - 3.6.9 fail on some clients but not others. This appears to have just started happening recently.

Example https://recruitment.haas.berkeley.edu/Posting/FacultyJobs.aspx

השתנתה ב־ על־ידי jonathont

more options

I loaded the root certificate also in our IIS server and after a day the errors went away. My guess is some timing issue FireFox has with their browser - but I have yet to have them respond.