Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Eror: Invalid timestamp - is your computers clock accurate? (Read 229 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Eror: Invalid timestamp - is your computers clock accurate?

 Hello everyone.

I get this error when I go to the site:

Code: [Select]
Error: Invalid timestamp - is your computers clock accurate?

I checked my time, everything shows correctly.

Code: [Select]
$ date

Wed Jan 15 10:14:02 PM CET 2025
What could be the problem and how to fix it?

Re: Eror: Invalid timestamp - is your computers clock accurate?

Reply #1 –
Quote from: tom-a – on
when I go to the site

Which site? Is it only a particular site or seemingly all sites? If it's just one site, probably the server's time is incorrect.

Re: Eror: Invalid timestamp - is your computers clock accurate?

Reply #2 –
Quote from: corysanin – on
Quote from: tom-a – on
when I go to the site

Which site? Is it only a particular site or seemingly all sites? If it's just one site, probably the server's time is incorrect.


Hello. Thank you for your answer.

This is only one site, other sites do not give such errors.

You wrote that it could be the wrong server time, do you mean the server on which the site I visited is located?

Is it possible to somehow fix this on my side? For example, change the time on yours, etc.
 

Re: Eror: Invalid timestamp - is your computers clock accurate?

Reply #3 –
Yes, the server running the site you visited. That server's time is wrong. You can try to contact the administrator or visit over plain http. Otherwise you can try skipping certificate validation. Probably not wise to do so.

Re: Eror: Invalid timestamp - is your computers clock accurate?

Reply #4 –
Quote from: corysanin – on
Yes, the server running the site you visited. That server's time is wrong. You can try to contact the administrator or visit over plain http. Otherwise you can try skipping certificate validation. Probably not wise to do so.

Thank you very much for this lifehack. I thought the problem was on my side or in the browser..