Fix clock errors on a self-hosted server
If the host computer's clock is wrong, sign-in still works on GameVox time, but message times stay wrong until you fix the clock.
Log lines starting with [SelfHosted] CLOCK: mean the host computer's clock is wrong. Fix the clock. Until you do, members can still sign in, but message times are wrong.
Why this happens
Members connect with sign-in tokens that last 5 minutes. A clock that is far off, from a dead CMOS battery, a virtual machine restored from an old snapshot or Windows Time turned off, makes every token look expired and members see "token is expired".
The server gets the correct time from GameVox with every heartbeat. When the host clock is more than 30 seconds off, it checks sign-ins against GameVox time instead. On Windows it also asks Windows to resync the clock.
Fix the clock
Windows
- Open Settings > Time & language > Date & time.
- Turn on Set time automatically and click Sync now, or set the time by hand.
The server's own resync needs administrator rights. The Windows service has them, the tray app does not. It also fails if Windows Time is disabled. The log says when it fails.
Linux
sudo timedatectl set-ntp true Docker
Fix the clock on the host machine. Containers use the host's clock.
Within about a minute of the fix, the log says the system clock is back in sync with GameVox.