Closed
Bug 1369822
Opened 8 years ago
Closed 8 years ago
OCSP: Yahoo.com - blocked
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: therubex, Unassigned)
References
()
Details
Looks like the latest victim of OCSP.
I'll assume its the same issue.
https://mail.yahoo.com/
https://search.yahoo.com/
![]() |
||
Comment 1•8 years ago
|
||
I can't reproduce this issue. Can you provide more details as to how this is happening? (and what is happening?)
Flags: needinfo?(therubex)
Another: https://www.howtogeek.com/
Let me fire up a clean Profile...
Doing nothing more then trying to load the websites noted.
Another: https://support.mozilla.org/kb/what-does-your-connection-is-not-secure-mean
Scratching head now...
/ Secure Connection Failed
/
/ An error occurred during a connection to support.mozilla.org.
/ The OCSP response is not yet valid (contains a date in the / future).
/ Error code: SEC_ERROR_OCSP_FUTURE_RESPONSE
Still have to fire up clean...
New, clean Profile.
Same issue, all sites noted above.
WinXP SP3.
Firefox 52.0.2 (guess I'll pull the latest ESR).
Build ID 20170323110425
User Agent Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0
Flags: needinfo?(therubex)
Ditto, FF 52.1.2 (I'll suppose that's the latest).
Build ID 20170517122419
Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0
And SeaMonkey too.
SeaMonkey 2.49.1 (not a release, but a build by Akalla)
Build ID 20170511042150
User Agent Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1
Ah, ignore, just a screw-up on my end.
Date set incorrectly, showing 05/31/2017 at the moment.
And the Error message even tells me that.
/ The OCSP response is not yet valid (contains a date in the / future).
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Confirmed.
Set the date correct & all is back to normal.
Sorry about the noise.
![]() |
||
Comment 7•8 years ago
|
||
Well, good to hear the issue is solved!
You need to log in
before you can comment on or make changes to this bug.
Description
•