Search Support

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

Getting "The OCSP server experienced an internal error" on Google

  • 4 replies
  • 5 have this problem
  • Last reply by shoolie

more options

I've been seeing this error frequently during the past week or so, so often that Google hasn't been accessible roughly one-third of the time. The error:


Secure Connection Failed

An error occurred during a connection to The OCSP server experienced an internal error. (Error code: sec_error_ocsp_server_error)

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

It also errors out on https Bing but not as often. Surprisingly, it has not affected https Yahoo. Any solutions other than toggling off "When an OCSP server connection fails, treat the connection as invalid" option?

FF30.0 w/NoScript on Ubuntu 14.04

All Replies (4)

more options

When you make changes to the default settings then that is your own risk. "When an OCSP server connection fails, treat the certificate as invalid" doesn't have a tick by default, so if you want to use this then you have to accept the consequences. Defaults are always chosen for a reason.

more options

Thank you for replying. It's been working before with the option toggled on and has been a problem more frequently only recently. Did something change that makes this OCSP option no longer valid?

more options
more options

My experience is that after getting this error, reloading the page will frequently succeed. However, today reloading the page does not work and the error recurs time after time. The pages are YouTube and This overall inconsistent flaky behaviour leads me to believe that there is some bug or inconsistency in FF. Is there some way of filing a bug report with Mozilla about this? I am on 31.3.0.