Just upgraded to 33.0.3 and now get "Error code: sec_error_ca_cert_invalid" on Oracle Enterprise Manager
Hi,
Just upgraded to 33.0.3 and I started getting the infamous "Error code: sec_error_ca_cert_invalid" message again. Just like on version 31.x.x, I am getting this whenever I try to get to our internal Oracle Enterprise manager (our database monitoring site).
The fix that I used on verion 31, i.e. changing the parameter "security.diable_button_openCertManager" to "false", doesn't work this time.
I even cleared the cache and all the cookies and that didn't make a difference either.
At this time, my only option is using IE, which I not my preferred browser.
Any help on this is greatly appreciated.
Thanks, Roya
Tüm Yanıtlar (5)
Separate Issue; Update your Flash Player v15.0.0.189 http://get.adobe.com/flashplayer/ Shockwave Director v12.1.3.153 http://get.adobe.com/shockwave/
Remove History For One Site Open the History Manager <Control><Shift> H. In the search bar, enter the name of the site. Right click on one of the listings and select Forget About This Site. This should remove all information, including any passwords / settings.
If there is still a problem, Start Firefox in Safe Mode {web link} While you are in safe mode;
Type about:preferences#advanced<Enter> in the address bar.
Under Advanced, Select General. Look for and turn off Use Hardware Acceleration.
Poke around safe web sites. Are there any problems?
Then restart.
Thanks.
I have already cleaned up the history, so our OEM sites are not in the history.
I tried the safe mod and truned off Use Hardware Acceleration and still got the same error when I tried to go to our OEM site.
Best regards, Roya
Try to rename the cert8.db file (cert8.db.old) and delete the cert_override.txt file in the Firefox profile folder to remove intermediate certificates and exceptions that Firefox has stored.
If that has helped to solve the problem then you can remove the renamed cert8.db.old file. Otherwise you can rename (or copy) the cert8.db.old file to cert8.db to restore the previously stored intermediate certificates. Firefox will automatically store intermediate certificates when you visit websites that send such a certificate.
If that didn't help then remove or rename secmod.db (secmod.db.old) as well.
You can use this button to go to the currently used Firefox profile folder:
- Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
- http://kb.mozillazine.org/Profile_folder_-_Firefox
It is possible that this is an issue with libPKIX.
- https://wiki.mozilla.org/SecurityEngineering/mozpkix-testing
- https://wiki.mozilla.org/SecurityEngineering/Certificate_Verification
You can look out for the special Firefox 33.1 version that is scheduled to be released at the start of next week (Monday, 10th).
You can also try out the current beta release and install the beta version via a custom install in its own installation folder and create a separate profile folder for that version.
See also:
Hi Cor-el,
Thanks for the help. You were right about the new version of Firefox just came out (i.e. 33.1). It fixed my issue.
Best regards, Roya
You're welcome