On my server with sites, TOR sites stop working every 1-2 days due to the fact that the clock on my server is behind, although the time is correct

Once every 2-3 days, sites are disabled (the Tor browser itself continues to work, sometimes this error pops up when restarting:

(Clock skew -25635 in microdesc flavor consensus from CONSENSUS - ?).
To be treated with another restart of the browser. I also rebooted the server from Windows Server 2019, it did not help.
You can see this in the logs:

5/2/22, 06:19:24.468 [WARN] Our clock is 7 hours, 40 minutes behind the time published in the consensus network status document (2022-05-02 14:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
5/2/22 06:19:24.468 [WARN] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 7 hours, 40 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
5/2/22, 06:19:27.557 [NOTICE] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
5/2/22 06:19:28.160 [NOTICE] Guard UnredactedTelecomix ($7778BBD947C2A5543120891C78F9E4EAE2D2B908) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 152/217. Use counts are 64/64. 154 circuits completed, 1 were unusable, 2 collapsed, and 3 timed out. For reference, your timeout cutoff is 60 seconds.

But on the server, the time and time zone are set automatically and match my clock to the nearest second.

did you set it according to current microsoft instructions?

by the way - why are you using and even paying for an OS, that does not fit your need?

1 Like