Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

How do you diagnose an OCSP failure?

  • 4 respostas
  • 1 tem este problema
  • 14 visualizações
  • Última resposta por cor-el

I had Firefox 56.0.2 on Linux set for hard OCSP failures. I started having problems connecting to some Google services recently and I finally found this: https://support.mozilla.org/en-US/questions/1200716. The problem appears to be Google's OCSP responder and setting security.ocsp.require to false fixed it. In older versions of Firefox, you would actually get a message that OCSP failed. I could not find any indication of that in this case. Is there a place you can see that? There seems to be a trend in Firefox to remove useful information from error messages.

I had Firefox 56.0.2 on Linux set for hard OCSP failures. I started having problems connecting to some Google services recently and I finally found this: https://support.mozilla.org/en-US/questions/1200716. The problem appears to be Google's OCSP responder and setting security.ocsp.require to false fixed it. In older versions of Firefox, you would actually get a message that OCSP failed. I could not find any indication of that in this case. Is there a place you can see that? There seems to be a trend in Firefox to remove useful information from error messages.

Todas as respostas (4)

In Firefox 57.0.4 I get this:

Secure Connection Failed

An error occurred during a connection to www.google.com. The OCSP server experienced an internal error. Error code: SEC_ERROR_OCSP_SERVER_ERROR

Not sure why you don't see that.

As with the linked issue, my error was SEC_ERROR_UNKNOWN_ISSUER

N3PB said

As with the linked issue, my error was SEC_ERROR_UNKNOWN_ISSUER

Yes, I don't know why you get that message instead of the one I get.

I'm currently seeing a valid response from the google OCSP server if I check this in the Browser Console.