We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

Secure Connection Failed Firefox 33.0.2 (Secure Connection Failed Issuer certificate is invalid. (Error code: sec_error_ca_cert_invalid) )

  • 2 replies
  • 18 have this problem
  • 1 view
  • Last reply by bpainter77

more options

Upgraded to 33.0.2 and now on certain self-signed sites that my internal networked servers use I receive the Secure Connection Failed Firefox 33.0.2 (Secure Connection Failed Issuer certificate is invalid. Error code: sec_error_ca_cert_invalid). The sites are used to administer my internal servers and have current certs. Is there a work around or fix for this issue? I should have stayed on older versions of FF.

Thank you.

Upgraded to 33.0.2 and now on certain self-signed sites that my internal networked servers use I receive the Secure Connection Failed Firefox 33.0.2 (Secure Connection Failed Issuer certificate is invalid. Error code: sec_error_ca_cert_invalid). The sites are used to administer my internal servers and have current certs. Is there a work around or fix for this issue? I should have stayed on older versions of FF. Thank you.

Modified by bpainter77

Chosen solution

hello bpainter77, i think this issue will be addressed in an upcoming update - setting an exception for pages with a sec_error_ca_cert_invalid error may work with firefox 34 beta already: http://www.mozilla.org/firefox/beta/

Read this answer in context 👍 1

All Replies (2)

more options

Chosen Solution

hello bpainter77, i think this issue will be addressed in an upcoming update - setting an exception for pages with a sec_error_ca_cert_invalid error may work with firefox 34 beta already: http://www.mozilla.org/firefox/beta/

more options

That did fix the issue. Thanks. The browser is a little sluggish after the update but I can certainly live with that.