Search Support

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.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

After clearing the cache, Firefox 3.6.8 still presents the old certificate

  • 4 uphendule
  • 30 zinale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu dparasam

more options

When the site has a new certificate, there are multiple popups for 'This connection is untrusted'. This is because, Firefox tries to present the cached certificate, but the site is using an updated certificate. I tried clearing the cache (Active logins, cookies) and deleted saved certificates from the 'Encryption' tab. That didn't help much - When the certificate on server has changed, and I have cleared the cache and the certificates from 'Encryption' tab, I still get more than one prompt for trusting the certificate.

The problem goes away when I restart the browser.

When the site has a new certificate, there are multiple popups for 'This connection is untrusted'. This is because, Firefox tries to present the cached certificate, but the site is using an updated certificate. I tried clearing the cache (Active logins, cookies) and deleted saved certificates from the 'Encryption' tab. That didn't help much - When the certificate on server has changed, and I have cleared the cache and the certificates from 'Encryption' tab, I still get more than one prompt for trusting the certificate. The problem goes away when I restart the browser.

All Replies (4)

more options

You can remove old certificates in the certificate manager.

Firefox > Preferences > Advanced : Encryption: Certificates - View Certificates

more options

I tried that. Even after I remove all certificates for the site, the current session seems to continue to use the older once trusted certificate. So when I add an exception to trust the certificate, the popup comes back since the certificate for the site has a newer certificate.

more options

Can you post a link to that site?

You can also check the certificate chain via website like this one:

http://www.networking4all.com/en/support/tools/site+check/
more options

Well, it's an app that I develop on my desktop. I uses self-signed certificates, so I guess we have no option but to add an exception every time the server uses a new certificate.