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.

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

SEC_ERROR_OCSP_FUTURE_RESPONSE for any https web page

  • 1 răspuns
  • 29 au această problemă
  • 1 vizualizare
  • Ultimul răspuns de 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.

Soluție aleasă

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.

Citește acest răspuns în context 👍 7

Toate răspunsurile (1)

more options

Soluție aleasă

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.