If you’re using an outdated Firefox issue older than build 47, the issue is most likely being caused by a Mozilla Firefox bug that affects certain CSS elements. In this case, you can fix the issue by updating your browser to the latest version. In case you’re already using the latest version of Firefox, you should investigate whether your date & time are not outdated. And in case you update them to the correct value but the modification doesn’t last in between restarts, you should replace your CMOS battery with a healthy equivalent. However, if you’re trying to visit a website with legitimate OCSP concerns, the only way you will be able to access it without encountering the SEC_ERROR_OCSP_FUTURE_RESPONSE error is to disable OCSP verifications.
Method 1: Update Firefox to the latest version
As it turns out, the issue is much more common on Firefox version v47 or under. As it turns out, the issue can be caused by a Mozilla Firefox bug that affected the rendering of certain CSS elements. Fortunately, Mozilla has already addressed the issue with a hotfix released with version 51. If this scenario is applicable and you’re using an outdated Firefox version, here’s a quick guide on updating Firefox to the latest version: In case the same SEC_ERROR_OCSP_FUTURE_RESPONSE error code is still occurring, move down to the next potential fix below.
Method 2: Set the correct date & time
As it turns out, the error code SEC_ERROR_OCSP_FUTURE_RESPONSE is often times associated with an OSCSP response that is not valid due to the fact that the machine is set to a date in the future. In order words, chances are the issue is appearing due to the fact that the computer clock or time is not set correctly. In case you’re date & time settings are set to a future date and that’s responsible for the SEC_ERROR_OCSP_FUTURE_RESPONSE, you should be able to fix the issue by changing the date & time settings to the correct values. Here’s a quick guide on how to do this: Note: The steps below are universal and should allow you to change the date & time values on Windows 7, Windows 8.1 and Windows 10. In case the same error is still occurring and you notice that the date & time has reverted back to the previous values, move down to the next method below. Note: I case the date & time value remained saved in between restarts but you’re still encountering the SEC_ERROR_OCSP_FUTURE_RESPONSE error, skip Method 3 and move directly to Method 4.
Method 3: Changing the CMOS battery
If the date & time values that you enforced during Method 2 didn’t remain saved in between restarts, it’s clear that you have a problem with your CMOS (Complementary Metal-Oxide Semiconductor) battery. This component is responsible for keeping track of certain BIOS preferences including the system-wide date and time. If this scenario is applicable, you should be able to fix the issue by clearing the CMOS battery or replacing it if necessary. Here’s a quick guide on resolving the issue: In case you’re still encountering the same SEC_ERROR_OCSP_FUTURE_RESPONSE error, move down to the final fix below.
Method 4: Disabling OCSP verifications
If none of the methods above has allowed you to fix the issue, there’s always the option to disable OCSP query altogether. While this will undoubtedly fix the issue since the OCSP check will no longer be performed, it also opens up your computer to some security risks. In case you understand the consequences and you want to go ahead with disabling OCSP verifications, follow the instructions below to do so:
Firefox Quantum, Beta and Nightly Affected by ‘Reap Firefox’ Crash AttackFirefox Monitor: Mozilla Firefox’s New Safety Feature Will Show You…Mozilla Firefox To Ditch Direct3D 11 And Shift Entirely to WebRender Engine with…Fix: Mozilla Firefox Critical Error
