Since installing Firefox 33 a "Secure Connection Failed" error is no longer bypassable using the
"I Understand the Risks" button - it's gone!

Is it still somehow possible to ignore certificate errors? (e.g. for lazy use in local environments)
Error code: sec_error_invalid_key


  • 7
    Are you 100% the two error messages are the same, because in my experience, they are not. – Ramhound Oct 14 '14 at 18:26
  • I'm leaning towards "different error" also. Just updated to Firefox 33 and the "Connection is Untrusted" dialog is unchanged for me. A change like you're suggesting (removal of user choice for invalid certificates) would break so much on web interfaces across corporate intranets, many parts on the Internet, and especially SOHO devices like cable modems and WiFi routers. It's more likely that there's an actual problem connecting to the server or something. Have you tried other HTTPS sites which have known-invalid certificates? – Iszi Oct 15 '14 at 7:04
  • It's also possible you're encountering a known bug which appears to have been around since FF 31. – Iszi Oct 15 '14 at 7:09
  • 2
    You conveniently obscured the actual error code, I believe. Also, the image is small. – Daniel B Oct 15 '14 at 7:27
  • 4
    I can confirm that FF33.0 fails with (Error code: sec_error_invalid_key) on the same site that 32.0 worked on prior to upgrade, on the same client computer. It also still works on Ubuntu/Canonical FF30.0 as always. (same as the screenshots). – MattBianco Oct 15 '14 at 15:04

Open Firefox's about:config

Set security.tls.insecure_fallback_hosts = www.domain.com (substitute the domain you're having the problem with)

Reload the page

  • 2
    This is the answer that actually answers the question. Some of the higher voted answers are quite beside the point (giving no solution for the question, and giving solutions for webmin problems)... – pgr Aug 24 '15 at 12:27
  • 12
    This did not work for me in Firefox 48.0 (GNU/Linux OS, if it makes a difference). – code_dredd Aug 25 '16 at 13:34
  • 2
    Not working in Firefox 53.0 Mac. Maybe has to do with me trying to whitelist an IP address,, and not a domain name. – sudo May 8 '17 at 17:58
  • 2
    This is an extremely old question. The current (2017) solution was impossible when the original question was posted, and the question has been edited/enhanced since it was originally asked. – MattBianco Jun 9 '17 at 9:06
  • 2
    So what version of FF is this answer applicable to? And how are you meant to add more than one website? Concatenate with commas, semi-colons? Surprising number of up-votes for a weak answer. – Adam Jun 14 '17 at 9:06

This problem has been reported to Mozilla in their support forum.

The reason is that Firefox 33 has fully switched to the more strict libPKIX and you can no longer disable this library and fall back to the previous NSS code.

See related Mozilla blog post and bug:

Bug 975229 - Remove NSS-based certificate verification

It appears that they will not change this behavior.

If your problem is like mine, on a webmin site, try recreating the certificate from inside webmin. It helped me get back the "make security exception" in FF 33.0!

  • 2
    I can confirm, that the recreation of the certificate brought back the old dialog as known from FF32 and below. Thank you Matt! For everybody else affected by this, here's a nice guide on how to recreate your certificate. – RienNeVaPlu͢s Oct 15 '14 at 16:17
  • Also, Firefox will show the standard untrusted certificate error if you create a self-signed certificate with the CN set to your domain name. – Toothbrush Mar 7 '15 at 11:48
  • 7
    Thanks for providing a solution, but in any case this is GODDAMN COMPLICATED! Firefox is less usable every day, it is like if they were trying hard to force everyone into Chrome. – Mephisto May 30 '15 at 23:02
  • 3
    This is ridiculous indeed. – Erwin Jun 26 '15 at 19:12

I had the same issue with Webmin and firefox 33. When I looked at the SSL certificate that Webmin was using, I found that it was using a 512 bit key! This must have been the default key size when I installed Webmin a couple of years ago.

Firefox 33 no longer supports keys less than 1024 bits (with good reason). See site compatibility

You can fix this right from Webmin if you use another browser that lets you bypass this type of error or if you temporarily disable SSL in webmin by setting ssl=0 in /etc/webmin/miniserv.conf and restart webmin with "/etc/init.d/webmin restart". Just login to the Webmin web UI and select: Webmin -> Webmin Configuration -> SSL Encryption -> Self Signed Certificate. Fill in the form (or leave the defaults) and then click the Create Now button. If you temporarily disabled ssl enable it with ssl=1 in /etc/webmin/miniserv.conf and restart webmin with "/etc/init.d/webmin restart". This will update your self-signed certificate for Webmin and you will now be able to access the page from Firefox 33 (With the usual browser warning about an untrusted connection).

  • 1
    So, there's no way to accept those certs anyways? – Geremia Mar 1 '15 at 3:07

Tried suggestion by @wisbucky but needed browser restart to bypass "Secure Connection Failed" error.

Steps followed were -

Open Firefox's config by typing following in address bar -


Search for security.tls.insecure_fallback_hosts and set it to

security.tls.insecure_fallback_hosts = hostname of site throwing error


For messages about a weak DH key, try toggling the following preferences (in Firefox's about:config):

  • security.ssl3.dhe_rsa_aes_128_sha
  • security.ssl3.dhe_rsa_aes_256_sha

This solved a "Secure Connection Failed" error I was seeing:

SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)

  • 1
    Thank you! Since the last FF update I couldn't access my router anymore due to that error message. Works fine now! On the other hand I wish the company of said router wouldn't be so damn lazy and just update the firmware with new certificates, since they're already an year over their validity date. – rfreytag Jul 15 '15 at 10:49

The webmin initial self ssl key is 512 byte

Solutions: using chrome or firefox , login in webmin , in webmin configuration ->SSL Encryption->Self-Signed Certificate

create a new SSL key and certificate for your Webmin server , the RSA key select default (2048), and make sue 'Use new key immediately'

then you can using IE access Webmin


Another potential fix worth noting: In your about:config, your user profile may have some settings that have been corrupted.

One in particular that was noted here: security.tls.version.max

In particular, the discussion at the linked site points out that somehow the security.tls.version.max setting had been changed from its original value (3) to the new value of 1, and after that change, the user was not able to connect to certain sites that needed the newer Transport Layer Security.

One easy way to check if this is happening without first mucking around with your about:config is to try creating a fresh profile, by running firefox -P and then creating a new profile, and see if you can successfully visit the site.

protected by Community Oct 28 '14 at 3:50

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.