- Joined
- Apr 3, 2014
- Messages
- 3,460
- Likes received
- 17,809
Just something I'd like to bring to the attention of tehelgee and alethiophile
In the IRC, a few Firefox users mentioned issues with accessing QQ. They received the message as follows:
Doing some research on the issue, it looks to be something with StartCom's responder server, something about it being overburdened. Other users who have reported the issue before have had it resolve itself, anywhere from ~12 hours to a couple days. Unfortunately, this seems to be an ongoing issue with StartCom.
Short-term solution is to go to about:preferences#advanced in Firefox and uncheck "Query OCSP responder servers to confirm the current validity of certificates". However, doing so does present a slight security risk.
Alternatively, another solution is to use a different browser in the meantime. Chrome users and IE users don't seem to be having any issue.
Long-term solution, if this persists (which is unlikely), is to switch SSL providers, but that is both expensive and a hassle.
tl;dr
Our SSL provider is fucking up, Firefox users getting hit. Should resolve within a couple days. Meantime, use a different browser or disable an option.
Can't fix it unless we're willing to spend both time and money to switch providers, and it hasn't happened before, so is unlikely.
In the IRC, a few Firefox users mentioned issues with accessing QQ. They received the message as follows:
Code:
"An error occurred during a connection to forum.questionablequesting.com. The OCSP server has no status for the certificate. (Error code: sec_error_ocsp_unknown_cert)Doing some research on the issue, it looks to be something with StartCom's responder server, something about it being overburdened. Other users who have reported the issue before have had it resolve itself, anywhere from ~12 hours to a couple days. Unfortunately, this seems to be an ongoing issue with StartCom.
Short-term solution is to go to about:preferences#advanced in Firefox and uncheck "Query OCSP responder servers to confirm the current validity of certificates". However, doing so does present a slight security risk.
Alternatively, another solution is to use a different browser in the meantime. Chrome users and IE users don't seem to be having any issue.
Long-term solution, if this persists (which is unlikely), is to switch SSL providers, but that is both expensive and a hassle.
tl;dr
Our SSL provider is fucking up, Firefox users getting hit. Should resolve within a couple days. Meantime, use a different browser or disable an option.
Can't fix it unless we're willing to spend both time and money to switch providers, and it hasn't happened before, so is unlikely.
Last edited:
