MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING
I've temporarily turned off the two settings for ocsp_stapling but would like to know if anyone else has all of a sudden started getting this error.
I've been working on a website for the past few weeks and have had no problem until today when I tried to access it and received the error...
Secure Connection Failed
An error occurred during a connection to nycc.site. The OCSP response does not include a status for the certificate being verified.
Error code: MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING
The site in question is currently https://nycc.site but this may not be up much longer as it will migrate to a new server in the coming week or two.
Todas las respuestas (2)
No problems here with visiting https://nycc.site.
You can remove all data stored in Firefox for a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History -> Show All History" or "View -> Sidebar -> History").
Using "Forget About This Site" will remove all data stored in Firefox for this domain like history and cookies and passwords and exceptions and cache, so be cautious. If you have a password or other data for that domain that you do not want to lose, make sure to backup this data or make a note.
You can't recover from this 'forget' unless you have a backup of involved files.
If you revisit a 'forgotten' website, data for that website will be saved once again.
See also:
- 1815931 - consider treating stapled OCSP as an optimization
- 1751184 - Our organization is still receiving MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING even after updating Firefox to current levels. Works with all other browsers. thanks.
(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)
Thank you for checking. Interestingly, I was able to hit the site on my iPhone using Firefox.
And thank you for the suggestions. I was all set to try those you, but figured I would turn the staple OCSP settings back to true to see if anything had changed. Sure enough, it's working like it should with no issues.
Chalking this one up to internet voodoo as I used to with Amiga voodoo and SCSI voodoo.
All the best to you.