Why won't Firefox let me add an exception?
Firefox tells me that a site has an invalid security certificate, which I know. It asks if I want to Add an Exception and I click to add one. It pops up the Add Security Exception window and that window tells me that this site has a valid certificate and there is no need to add an exception; but I DO need to add an exception and it won't do it for me. Why? I am working in a secure test lab and use Firefox to login to our systems under test. Each time we change or add hardware we must add exceptions to login to a system. I have done this for years with Firefox but now Firefox 4 seems confused. We now need to use EI, which I would rather not.
Chosen solution
by elangelandI was able to fix this on one machine by clearing my recent history through the Options dialog. On a second occasion, I was able to rule out "Browsing & Download History" and "Form & Search History", so I can say at this point that the problem can be fixed by clearing one or more of Cookies, Cache, "Active Logons", or "Site Preferences".
Oh, in all cases, I selected "Everything" for the time period to clear.
Read this answer in context 8Helpful replies
I use a lot of equipment with internal (untrusted/self-signed) certificates and I face this problem one or two times a month. This has been going on since FF 4.0 came out and has continued with v5 and v6. I know someone said nothing has changed with regard to cert handling - you are wrong.
This issue is nearly crippling to me and is driving me away from FF entirely. Were it not for a couple irreplaceable plugins I use, I would already be gone. No other modern browser is as irritating WRT the handling of untrusted SSL certificates as firefox is, and no other modern browser has a problem like this. I'm facing this issue right now with a system that I *need* to be able to access, and I simply cannot use FF to do so because of this infuriating issue.Go to answer 7
Additional System Details
Sites Affected
http://
Installed Plug-ins
- Yahoo! activeX Plug-in Bridge
- Adobe PDF Plug-In For Firefox and Netscape "9.4.0"
- The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
- Shockwave Flash 10.2 r152
- Next Generation Java Plug-in 1.6.0_21 for Mozilla browsers
- NPRuntime Script Plug-in Library for Java(TM) Deploy
- 4.0.50917.0
- Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
- Npdsplay dll
- DRM Store Netscape Plugin
- DRM Netscape Network Object
Application
- User Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
More Information
I can't give you the URL of the affected sites. It's a secure lab.
I'm having a same problem where firefox complains about the self-signed cert but then when you click on view certificate, it says it's fine. I have an old self-signed cert that was expired which didn't seem to bother firefox until recently. I even tried issues a new valid cert and chrome and IE can see the new cert (new expiration dates) but firefox still gives me the "this connection is untrusted message". Then when I try to view the cert to add an exception it says it fine. One thing I noticed was that view cert in FF still shows the old cert expiration dates, whereas in chrome and IE the new cert shows up.
I have tried deleting the certs out of the certificate manager and adding the FF exception again but it didn't work. I even used IE to install the self-signed root cert again. IE and chrome will now open as a trusted page but FF still has the "this connection is untrusted" -> view -> cert is valid message.
I'm going to try a few of the suggestions above hopefully something will reset FF's cert exception/cache or something.
Thanks
I overinstalled FF 7.0 and FF 6.0.2 but it didn't help. I said heck with it and created a new profile and copied my profile over from a working machine. It's working ok now. upgraded back to FF 7.0.1
Chosen Solution
I was able to fix this on one machine by clearing my recent history through the Options dialog. On a second occasion, I was able to rule out "Browsing & Download History" and "Form & Search History", so I can say at this point that the problem can be fixed by clearing one or more of Cookies, Cache, "Active Logons", or "Site Preferences".
Oh, in all cases, I selected "Everything" for the time period to clear.