為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

SEC_ERROR_OCSP_FUTURE_RESPONSE for any https web page

  • 1 回覆
  • 29 有這個問題
  • 1 次檢視
  • 最近回覆由 anderci

more options

Our PC is running windows 7 pro 64bit. It is trying to use Firefox 5.3.0 (32 bit) We get the SEC_ERROR_OCSP_FUTURE_RESPONSE every time we try to display a https web page.

e.g.:
https://support.mozilla.org/en-US/questions/1154357
https://support.mozilla.org/en-US/questions/new/desktop/other/form?search=SEC_ERROR_OCSP_FUTURE_RESPONSE+for+any+https+web+page&step=aaq-register

We have run malwarebytes anti-malware, superantispyware and adwcleaner eset online one-time scanner. We have uninstalled Firefox and reinstalled Firefox. We do not know why it chooses the 32 bit version. The problem still occurs with Firefox. It does not happen with internet explorer. We seriously prefer to use Firefox, but cannot with this serious problem.

Our PC is running windows 7 pro 64bit. It is trying to use Firefox 5.3.0 (32 bit) We get the SEC_ERROR_OCSP_FUTURE_RESPONSE every time we try to display a https web page. e.g.: https://support.mozilla.org/en-US/questions/1154357 https://support.mozilla.org/en-US/questions/new/desktop/other/form?search=SEC_ERROR_OCSP_FUTURE_RESPONSE+for+any+https+web+page&step=aaq-register We have run malwarebytes anti-malware, superantispyware and adwcleaner eset online one-time scanner. We have uninstalled Firefox and reinstalled Firefox. We do not know why it chooses the 32 bit version. The problem still occurs with Firefox. It does not happen with internet explorer. We seriously prefer to use Firefox, but cannot with this serious problem.

被選擇的解決方法

Sorry for bothering you all. Problem Resolved by:

correcting the PCs system date from 15 april 2017 to 21 april 2017!

I have no idea how the date got messed up.

從原來的回覆中察看解決方案 👍 7

所有回覆 (1)

more options

選擇的解決方法

Sorry for bothering you all. Problem Resolved by:

correcting the PCs system date from 15 april 2017 to 21 april 2017!

I have no idea how the date got messed up.