Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 1 ответ
  • 48 имеют эту проблему
  • 1 просмотр
  • Последний ответ от cor-el

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?

Все ответы (1)

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: