We are currently looking into reports of SEC_ERROR_OCSP_INVALID_SIGNING_CERT errors in Firefox.
Update: 10/15/2017 9:00 am
We are continuing to work on correcting this issue. Very sorry for the inconvenience and frustration.
Update: 10/15/2017 9:20 pm
We are continuing to work on this issue. It appears to be related to the site security certificate. It is valid and being accepted by other browsers, but Firefox is not accepting it as valid. We have reached out to the certificate issuer to have things reissued and checked into. We hope this will resolve the issue that’s occurring on Firefox. In the mean Edge and Internet Explorer should be functioning normally. We’re very sorry for the frustration and inconvenience.
Update: 10/15/2017 11:20 pm
We have been able to determine this is a widespread issue with Firefox and is not specific to SingSnap (see links below showing reports of the same issue). We are still attempting to resolve things from our end, but it may be something Mozilla will have to address in Firefox.
View recent reports via Google
View recent reports via Twitter
Update: 10/16/2017 8:35 pm
This issue is currently still not resolved, but we have seen intermittent periods of no trouble. We hope this is a sign that Mozilla is working on the issue. We are also still continuing to look into things we can do to work around the issue.
We currently recommend using Edge or Internet Explorer browser but if you are unable and want to use Firefox, we have found a temporary workaround. Keep in mind, this does adjust the security settings on your Firefox browser and once you are done logging into SingSnap – we strongly recommend you un-do the change to ensure maximum security on your browser.
1. Type about:config in the URL bar
2. Search for: security.ssl.enable_ocsp_stapling
3. Double click to set to: False
Doing this is at your own risk and once again, it is best to reset this preference to True once you are logged into your account.
Update: 10/17/2017 2:35 pm
We have monitored things since late yesterday evening and it appears Mozilla has corrected this issue. We have however updated our security certificate for good measure. We believe this issue has been fully resolved. Should any further issues arise we will reopen this posting.