Our website is not working in Firefox
We started getting calls that our website is not working in Firefox. I checked Chrome and Edge, they work fine. The only thing I am getting is the following error:
An error occurred during a connection to www.utfcu.org. The OCSP server has refused this request as unauthorized. Error code: SEC_ERROR_OCSP_UNAUTHORIZED_REQUEST Our certificate was just renewed last month so I know it is not an SSL issue. Anyone else having a similar problem?
Thanks,
Gekose oplossing
I ended up having to call the company who hosts our website and it is working now. The only thing they said is that it had to do with OCSP stapling. A quick search on google brought this up:
While many web servers advertise support for OCSP stapling, implementations are not always reliable. For example, when Apache queries the OCSP server, in the event of a temporary failure, it will discard the cached good response from the previous request, and start serving bad response.
I hope this helps someone in the future who might have a similar issue.
Lees dié antwoord in konteks 👍 0All Replies (4)
I had no problem with the link.
There is security software like Avast, Kaspersky,
BitDefender and ESET that intercept secure
connection certificates and send their own.
https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can
https://support.mozilla.org/en-US/kb/firefox-and-other-browsers-cant-load-websites
https://support.mozilla.org/en-US/kb/secure-connection-failed-error-message
https://support.mozilla.org/en-US/kb/connection-untrusted-error-message
Websites don't load - troubleshoot and fix error messages
Gekose oplossing
I ended up having to call the company who hosts our website and it is working now. The only thing they said is that it had to do with OCSP stapling. A quick search on google brought this up:
While many web servers advertise support for OCSP stapling, implementations are not always reliable. For example, when Apache queries the OCSP server, in the event of a temporary failure, it will discard the cached good response from the previous request, and start serving bad response.
I hope this helps someone in the future who might have a similar issue.
That was very good work. Well Done.