97

I am maintaining a few web applications. The development and qa environments use invalid/outdated ssl-certificates.

Although it is generally a good thing, that Firefox makes me click like a dozen times to accept the certificate, this is pretty annoying.

Is there a configuration-parameter to make Firefox (and possibly IE too) accept any ssl-certificate?

EDIT: I have accepted the solution, that worked. But thanks to all the people that have advised to use self-signed certificates. I am totally aware, that the accepted solution leaves me with a gaping security hole. Nonetheless I am to lazy to change the certificate for all the applications and all the environments...

But I also advice anybody strongly to leave validation enabled!

Leniel Maccaferri
  • 97,176
  • 43
  • 357
  • 461
Mo.
  • 14,575
  • 13
  • 44
  • 57
  • 1
    I will point out that this question applies to web servers that have valid certificates for their domains, but can only (at some given time) be reached via IP address. Being able to visit https ://123.45.67.89/ without clicking 4 extra times is a great blessing to me. – Sparr Sep 27 '10 at 23:05

10 Answers10

71

Try Add Exception: FireFox -> Tools -> Advanced -> View Certificates -> Servers -> Add Exception.

henryc2323
  • 751
  • 1
  • 5
  • 2
  • 20
    Can't add exception when "HTTP Strict Transport Security (HSTS)" is specified, so answer won't always work. – rveach Mar 22 '16 at 14:57
  • I'm getting "This site provides a valid, verified identification. There is no need for an exception" for the SAME site that gives me this error: "SSL Certificate Hostname Mismatch ssl_domain_invalid" – Katie Aug 10 '16 at 22:06
  • +1 for much better answer, accepted answer is incredibly insecure. I encounter this often using self-signed certificates for local development and it's much better to add exceptions on a case-by-case basis. Related Q/A on mozilla's support forum: https://support.mozilla.org/en-US/questions/1055526 – munsellj Jan 05 '17 at 13:58
  • Just for fun, here is a little shortcut to get to the same screen that @henryc2323 points you to: "chrome://pippki/content/exceptionDialog.xul" Just paste that into Firefox's address field. For reference, I found that here: https://support.mozilla.org/en-US/questions/1094104 – AlienFromCA May 25 '17 at 21:05
30

I ran into this issue when trying to get to one of my companies intranet sites. Here is the solution I used:

  1. enter about:config into the firefox address bar and agree to continue.
  2. search for the preference named security.ssl.enable_ocsp_stapling.
  3. double-click this item to change its value to false.

This will lower your security as you will be able to view sites with invalid certs. Firefox will still prompt you that the cert is invalid and you have the choice to proceed forward, so it was worth the risk for me.

Bryan Focht
  • 930
  • 1
  • 10
  • 10
  • *THIS* is the real correct answer. When you are on a public WLAN which redirects to a registration page and all you have is Firefox, then you *KNOW* the page is *not* https://www.google.com/ncr and *want* to be given the possibility to accept temporarily the ISP wrong certificate. *without* configuring a permanent exception in the certificates configuration. Then you uncheck the "Permanently store this exception" checkbox and off you go. – Alain Pannetier Oct 05 '15 at 13:41
  • 7
    Not working for me in Firefox 53.0 for Mac. Probably because they change entirely how this browser works every few weeks. – sudo May 08 '17 at 17:55
  • 1
    I am trying to use https on localhost for development. I tried this but it didnt work. Screenshot - https://i.imgur.com/1LVqLQw.png – Noitidart Sep 15 '18 at 17:01
26

Go to Tools > Options > Advanced "Tab"(?) > Encryption Tab

Click the "Validation" button, and uncheck the checkbox for checking validity

Be advised though that this is pretty unsecure as it leaves you wide open to accept any invalid certificate. I'd only do this if using the browser on an Intranet where the validity of the cert isn't a concern to you, or you aren't concerned in general.

Dan Herbert
  • 94,622
  • 47
  • 184
  • 218
  • 5
    I'm confused: I can't find that option on FF2 or FF3. There is only an option to switch the use of OCSP. In what version of FF did see what you describe? – sleske May 15 '09 at 22:54
  • @sleske OCSP is how certificates are checked. Switching the use of this will turn on or off the check for certificates depending on what you prefer. – Dan Herbert May 16 '09 at 01:02
  • 9
    This seems like a Very Bad Idea. – Greg Hurlman Nov 06 '09 at 15:49
  • @Greg, I agree. I would definitely recommend your solution over mine as the correct practice. – Dan Herbert Nov 06 '09 at 16:30
  • 8
    OCSP is how certificate *revocation* is checked, not how certificates are checked. – Bruno Sep 11 '12 at 19:39
  • Is this option set permanently in the profiles? Is there any documentation for it? I need to set it programmatically. – CMCDragonkai Mar 31 '14 at 06:12
  • @CMCDragonkai I really hope it's not able to be changed programmatically. Certificates checks should not be able to get disabled automatically as it's a huge security vulnerability. – Dan Herbert Apr 01 '14 at 07:37
  • 1
    Well I really hope they can. I need to program the browser to do automated scraping. Security by obscurity is not security anyway. – CMCDragonkai Apr 01 '14 at 12:04
  • Is there a solution for the Latest Firefox? (44 and above)? Thank You. – Royi Mar 13 '16 at 08:44
  • 8
    @Drazick The option is now a checkbox under `Preferences -> Advanced -> Certificates`, it's labeled `"Query OCSP responder servers to confirm the current validity of certificates"` – bruchowski Apr 19 '16 at 03:13
2

If you have a valid but untrusted ssl-certificates you can import it in Extras/Properties/Advanced/Encryption --> View Certificates. After Importing ist as "Servers" you have to "Edit trust" to "Trust the authenticity of this certifikate" and that' it. I always have trouble with recording secure websites with HP VuGen and Performance Center

2

Instead of using invalid/outdated SSL certificates, why not use self-signed SSL certificates? Then you can add an exception in Firefox for just that site.

Forgotten Semicolon
  • 13,382
  • 1
  • 47
  • 61
2

Using a free certificate is a better idea if your developers use Firefox 3. Firefox 3 complains loudly about self-signed certificates, and it is a major annoyance.

rudle
  • 101
  • 1
  • 5
1

Create some nice new 10 year certificates and install them. The procedure is fairly easy.

Start at (1B) Generate your own CA (Certificate Authority) on this web page: Creating Certificate Authorities and self-signed SSL certificates and generate your CA Certificate and Key. Once you have these, generate your Server Certificate and Key. Create a Certificate Signing Request (CSR) and then sign the Server Key with the CA Certificate. Now install your Server Certificate and Key on the web server as usual, and import the CA Certificate into Internet Explorer's Trusted Root Certification Authority Store (used by the Flex uploader and Chrome as well) and into Firefox's Certificate Manager Authorities Store on each workstation that needs to access the server using the self-signed, CA-signed server key/certificate pair.

You now should not see any warning about using self-signed Certificates as the browsers will find the CA certificate in the Trust Store and verify the server key has been signed by this trusted certificate. Also in e-commerce applications like Magento, the Flex image uploader will now function in Firefox without the dreaded "Self-signed certificate" error message.

Fiasco Labs
  • 6,429
  • 3
  • 31
  • 43
1

For a secure alternative, try the Perspectives Firefox add-on

If this link doesn't work try this one: https://addons.mozilla.org/en-US/firefox/addon/perspectives/

otonglet
  • 3,130
  • 21
  • 36
1

In the current Firefox browser (v. 99.0.1) I was getting this error when looking at Web Developer Tools \ Network tab:

MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT

enter image description here

I was trying to debug an Angular app which is served at https://localhost:4200... however the real port it's pointing to and being debugged from in Visual Studio 2022 is 44322.

I had to follow these steps to fix the issue:

  1. Open Firefox Settings;

  2. Look for Privacy & Security tab on the left;

  3. Scroll down to the bottom and look for Certificates;

  4. View Certificates;

  5. In this window you must click Add Exception and enter the location. In my case it was:

    https://localhost:44322

  6. Click Get Certificate button;

  7. Click Confirm Security Exception button.

After that, try reloading your page.

enter image description here

Leniel Maccaferri
  • 97,176
  • 43
  • 357
  • 461
0

The MitM Me addon will do this - but I think self-signed certificates is probably a better solution.

palmsey
  • 5,774
  • 3
  • 33
  • 40
  • 2
    Error: "This add-on has been disabled by an administrator." on the Mozilla Addons site. – KERR Mar 14 '18 at 04:26