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.

Avatar for Username

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ää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

when I am trying to run https://apps.facebook.com/candycrush/?fb_source=sidebar_bookmark getting message (Secure Connection Failed The connection to the server

  • 1 vastaus
  • 2 henkilöllä on sama ongelma
  • 3 näyttöä
  • Viimeisin kirjoittaja guigs

Eihab-Elhofy
Eihab-Elhofy
more options

when I am trying to run https://apps.facebook.com/candycrush/?fb_source=sidebar_bookmark getting message (Secure Connection Failed The connection to the server was reset while the page was loading. 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.

when I am trying to run https://apps.facebook.com/candycrush/?fb_source=sidebar_bookmark getting message (Secure Connection Failed The connection to the server was reset while the page was loading. 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.

Kaikki vastaukset (1)

guigs
guigs
more options

I am sorry to hear that the sidebar bookmark of candy crush is giving you a secure connection failure error. Please first make sure that Firefox is up to date to version 40.0.1.

Debbie on the facebook community forum suggested to uncheck the secure certificates which can be a security risk: https://www.facebook.com/help/communi.../?id=10204468353334576

However it might also help to get in contact with the certificate issuer, and since that thread is a year old, it is likely it is not for the same reason you are running into it here/now.