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!

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.

FF6 throws revoked certificate error on chase.com, IE does not

  • 3 răspunsuri
  • 33 au această problemă
  • 2 vizualizări
  • Ultimul răspuns de cor-el

more options

Since the v6 update I can not enter the www.chase.com site with firefox. When I connect I get a revoked certificate error. this happens on a win 7 computer and a win2k computer both running ff 6. Explorer works fine.

Since the v6 update I can not enter the www.chase.com site with firefox. When I connect I get a revoked certificate error. this happens on a win 7 computer and a win2k computer both running ff 6. Explorer works fine.

Toate răspunsurile (3)

more options

Try to remove the VeriSign intermediate certificate that is used for that connection to make Firefox store the certificate that is send by the server.

"VeriSign Class 3 International Server CA - G3"

Stored intermediate certificates show as "Software Security Device" in the "Security Device" column in the Certificate Manager.

  • Tools > Options > Advanced > Encryption: Certificates > View Certificates : Authorities
more options

Hi co-rel,

On another note: After updating to v6, some new certificates entry (untrusted) for many certs issued by the USERTRUST Network has appeared under Options > Advanced > Encryption View Certificates > Servers. Please confirm. Thanks.

I'm assuming this has got to do something with the breach of an intermediate authority under Comodo. But that was some time ago and it was already hard coded into previous releases, isn't it, or is this something new?

Thank you.

Modificat în de Anyt

more options

I've noticed a lot of posts regarding the same problem that you have with the Chase site.

Do you still have that problem or is it already solved?

I'm not seeing any certificate problems with accessing the chase.com site.