ntpdate: no server suitable for synchronization found
No usable NTP reply was received
Seen in ntpdate (Linux, BSD, macOS)
ntpdate got no acceptable time reply from any of the servers it queried, so it did not change the clock.
Common causes
- Outbound UDP port 123 is blocked by a firewall, or replies to source port 123 are dropped.
- The NTP server is unreachable or not answering.
- The server is not synchronised itself (stratum 16), so ntpdate rejects it.
How to fix it
- Run `ntpdate -d server` to see whether replies arrive and why a server is rejected.
- Try `ntpdate -u server` to use an unprivileged source port, and allow outbound UDP 123.
- Stop a running ntpd or chronyd before running ntpdate, or use `chronyc tracking` instead.
Got a different message? Paste it into the error explainer.
Related errors
- ECONNREFUSED · Connection refused
- ETIMEDOUT · Connection timed out
- ECONNRESET · Connection reset by peer
- EHOSTUNREACH · No route to host
- getaddrinfo ENOTFOUND · The hostname doesn't exist in DNS
- getaddrinfo EAI_AGAIN · Temporary DNS failure
- ENETUNREACH · Network is unreachable
- Broken pipe · Wrote to a connection or pipe that was already closed
- Software caused connection abort · Your own system aborted the connection
- WSAETIMEDOUT (10060) · Windows connection attempt timed out
- WSAECONNREFUSED (10061) · Windows connection refused
- Request timed out. · Ping got no reply