Logseq "Unable to Start Synchronization, Please Check if the Local Time Is Correct"
Workaround available Windows, Mac, Linux Updated October 21, 2026
Quick answer
This sync error appears when your computer's clock drifts from internet time, even if it looks right. Forcing a time sync in your OS settings and restarting Logseq fixes it.
Most likely fix: Force a time sync.
Symptoms
Logseq Sync refuses to start and shows 'Unable to start synchronization, please check if the local time is correct' although the clock appears correct.
Why it happens
- System clock drifted a few seconds or minutes from internet time
- Automatic time sync turned off
- Wrong time zone setting
How to fix it
Try these in order — the most common fix is first.
1. Force a time sync
- Windows: Settings > Time & language > Date & time > Sync now
- Mac: System Settings > General > Date & Time > toggle Set time automatically off and on
- Linux: enable NTP, e.g. timedatectl set-ntp true
2. Check the time zone
- Make sure the time zone is set automatically or matches your location
- Restart Logseq
3. Restart and log in again
- Quit Logseq completely
- Reopen and start sync
- If it persists, log out and back in to the sync account
This guide also covers
- logseq check if the local time is correct
- unable to start synchronization logseq
- logseq sync local time error
Still not working?
If Logseq keeps failing, you're not alone. See every Logseq problem users report or the alternatives people switch to.