HTTPS require the correct time - within a tolerance.
One thing to check is that the date and time (and timezone, daylight savings) are correct on your computer. There is a tolerance which I am unable to determine (I think it is several minutes or more) however it is OK to set the clock manually. You don't need to be set to the second.
You get all kinds of weird error messages reported by the browsers various, rarely helpful, in the event that you should attempt to use https with the time incorrect.
I have my PC set to "Use Internet Time".
When I press the "Update now" button there is often an error reported however the time does usually get adjusted anyway. I at present just point it at "time.windows.com" although I have noticed fewer reported errors with say "0.pool.ntp.org".
Once you have internet time enabled and pointed to a server you can force an update from the command line or a batch file with
w32tm /resync
This is handy since the "update now" button is quite a few clicks away. You may need "Run as administrator".