When I go to one of our development sites, I get this error: Secure connection failed An error occurred during a connection to xxx.xxx.com Peer's certificate has an invalid signature (Error code: sec_error_bad_signature) . I do not have the option to add an excpetion anymore, but we used to be able to navigate there. I'm running 3.6.13.
I'm also using Firefox 3.6.13 and had the same problem. This issue can be solved simply by changing Firefox's configuration - it's NOT necessary to install any Firefox add-ons to do this, even though internet searches will list various add-ons for fixing this problem.
This is how it's done:
- Open a new Firefox window, and type this into the address/URL:
- You'll probably see a warning that changing the config can be dangerous. Click the button to accept the warning and proceed, but BE CAREFUL from here on!
- A table will appear showing various Firefox settings ("Preference Names") and their current values.
- In the Filter box type: broswer.xul
- There should now be a shorter list of settings, including one named browser.xul.error_pages.expert_bad_cert with a value of false.
- Right-click on browser.xul.error_pages.expert_bad_cert and select Toggle. The value will change to true.
- Exit completely from Firefox (i.e. close all windows), and then restart it.
The next time you visit a secure site where there is a problem with its certificate, the certificate error page will show a button that allows the site to be added as an exception, and then you'll be able to proceed and view the site.
WARNING: If Firefox warns that there is a problem with a site's certificate, proceed only if:
a) you are 100% certain that it's safe, or
b) you accept the risks!
Certificate warnings should definitely NOT appear on any sites dealing with money/transactions, e.g. online shopping, online banking, etc.
This doesn't always seem to work. I still get the same error and there is no button to allow me to add this site as an exception I am using version 3.6.18 and followed these instructions carefully but the same error page described here comes up when I tried to access my https site.