Token Expired

If signing in to Lords Bot shows Token expired - Click here for help, your PC’s clock is wrong. The Lords Bot server refuses a sign-in when the PC’s time is more than 5 minutes behind the real time. Fix the clock and sign in again.

The check uses world time (UTC), so the time zone matters too. A PC can show the right local time and still fail if its time zone is wrong. This is common on cloud servers.

Fix it in Windows Settings (Windows 10 and 11) #

1. Right-click the clock on the taskbar and choose Adjust date and time (or open Settings > Time & language > Date & time).
2. Turn on Set time automatically.
3. Turn on Set time zone automatically, or choose your correct Time zone from the list.
4. Click Sync now.
5. Sign in to Lords Bot again.

Fix it with the classic Date and Time window #

This works on every Windows version, including Windows Server.

1. Press Windows key + R, type timedate.cpl and press Enter.
2. On the Date and Time tab, click Change time zone and check that the time zone is correct.
3. Open the Internet Time tab and click Change settings.
4. Tick Synchronize with an Internet time server, then click Update now.
5. Click OK to close the windows, then sign in to Lords Bot again.

Still failing? #

• If the clock keeps drifting, check that Set time automatically is still on. On a cloud server, ask your provider why the clock isn’t syncing.
• Older versions of Lords Bot called this error Invalid Timestamp. The fix is the same.
• For other sign-in messages, see Sign-In Messages and What They Mean.