Mozilla サポートの検索

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

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

trying to view website but get this message (Error code: sec_error_ocsp_invalid_signing_cert)

  • 1 件の返信
  • 4 人がこの問題に困っています
  • 5 回表示
  • 最後の返信者: cor-el

more options

iv emailed website they say its working fine iv tryed other browser and it works but not with this one and i get this message but get this message


(Error code: sec_error_ocsp_invalid_signing_cert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

iv tryed all your troubleshoots and nothing works iv checked my virus software and thats okay to if you could help it would be really appreciated thank you

iv emailed website they say its working fine iv tryed other browser and it works but not with this one and i get this message but get this message (Error code: sec_error_ocsp_invalid_signing_cert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. iv tryed all your troubleshoots and nothing works iv checked my virus software and thats okay to if you could help it would be really appreciated thank you

すべての返信 (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 to true 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: