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.

Etsi tuesta

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.

Lue lisää

Secure Connection Failed

  • 3 vastausta
  • 1 henkilöllä on sama ongelma
  • 5 näyttöä
  • Viimeisin kirjoittaja cor-el

more options

I have always been able to access my credit union's website, via Firefox. Today, it wont let me: "Secure Connection Failed." What do I do?

I have always been able to access my credit union's website, via Firefox. Today, it wont let me: "Secure Connection Failed." What do I do?

Kaikki vastaukset (3)

more options
more options

I am getting the following message when I try to access my OWN website! I can access all other websites...AND I can access my website from other browsers... only have trouble on Firefox. Do I need to get rid of Firefox as my browser?

I have tried everything recommended on Firefox to fix this and nothing works.


Secure Connection Failed

An error occurred during a connection to www.fredcolby.com. The response from the OCSP server was corrupted or improperly formed.

Error code: SEC_ERROR_OCSP_MALFORMED_RESPONSE

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the website owners to inform them of this problem.

Learn more…

more options

There is a problem with the Stapled OCSP response in the TLS handshake.

Firefox always checks this response as this is a security feature. This needs to be fixed on the server.