Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

I keep getting this error message, (Error code: sec_error_ocsp_invalid_signing_cert)... Why?

  • 1 odgovor
  • 48 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od cor-el

Cursed_Tenno93
Cursed_Tenno93
more options

Recently, I've been using Firefox to get onto the site Fanfiction.net. But recently I've been getting an error message

(Error code: sec_error_ocsp_invalid_signing_cert)

I've tried the solutions people with the same or similar problems have and nothing has worked. Fanfiction.net works fine on IE 11, but it messes up on FireFox 31. What can i do to fix this so that i can get back onto this website?

Recently, I've been using Firefox to get onto the site Fanfiction.net. But recently I've been getting an error message (Error code: sec_error_ocsp_invalid_signing_cert) I've tried the solutions people with the same or similar problems have and nothing has worked. Fanfiction.net works fine on IE 11, but it messes up on FireFox 31. What can i do to fix this so that i can get back onto this website?

Svi odgovori (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

That could be a problem with the usage of libPKIX in the Firefox 31 and later releases.

It is possible to disable this new feature by disabling libPKIX support, but this is not recommended for security and vulnerability reasons.

  • about:config page: security.use_mozillapkix_verification = false

It is possible that the website will fix this issue shortly, so make sure to check regularly if this workaround is still required by resetting the pref and see if it works. You may have to reload and bypass the cache via Ctrl+F5.

You can contact the website and bring this article under their attention: Behavior Changes and Things for CAs to Fix: