Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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.

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

"Add an Exception" for purporedly invalid/questionable SSL certifcates does not work in V 37.0.1. How do I get around thgis?

  • 5 majibu
  • 2 wana tatizo hili
  • 6 views
  • Last reply by Mole2015

more options

Accessing admin page of SAN that uses self-signed cert. (from Oracle Corp.), warning dialogue appears, which is OK, bu the "add exception" mechanism no longer works. (Used to in earlier versions of FireFox.)

Accessing admin page of SAN that uses self-signed cert. (from Oracle Corp.), warning dialogue appears, which is OK, bu the "add exception" mechanism no longer works. (Used to in earlier versions of FireFox.)

All Replies (5)

more options

I do not know without investigating the cert, however there are some guides on how to verify self-signed certs:

Add on for work around:

More info:

more options

The website may try to fallback to TLS 1.0 in a way that is no longer allowed in current releases or may be using a deprecated cipher suite.

You can open the about:config page via the location/address bar and use its search bar to locate this pref:

  • security.tls.insecure_fallback_hosts

You can double-click the line to modify the pref and add the full domain to this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). You should only see domains separated by a comma in the value column.


more options

cor-el said

The website may try to fallback to TLS 1.0 in a way that is no longer allowed in current releases or may be using a deprecated cipher suite. You can open the about:config page via the location/address bar and use its search bar to locate this pref:
  • security.tls.insecure_fallback_hosts
You can double-click the line to modify the pref and add the full domain to this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). You should only see domains separated by a comma in the value column.

Maybe this works but it is such an awkward and messy "solution" that it doesn't really qualify.

The real issue here is that FireFox developers have become arrogant and ceased to take note of what users do and need as opposed to their latest fancy theories.

I mostly prefer to use FireFox but if developments continue as at present - lots of unnecessary eye-candy and visual changes but no improvements in the fundamentals such as proper support for multi-processing - then Chrome is what I will have to use.

more options

guigs2 said

I do not know without investigating the cert, however there are some guides on how to verify self-signed certs: Add on for work around: More info:
more options

The add-on works as expected.

Thank you for your help.