Droplet in Singapore can't sync NTP server.

  • Posted May 30, 2014

Droplet in US can sync time using ntp. But one in Singapore results “Server dropped: no data” and “no server suitable for synchronization found” in the same way. By any chance, Singapore ISP don’t allow NTP connection?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

I recently launched an Ubuntu 14.04.1 LTS Trusty Tahr 32bit droplet. I was able to change my system date and synced to However, just a few minutes ago as I was looking into my database (MariaDB), I noticed that the date was not SGT. So, I added the “default_time_zone = +08:00” into my /etc/mysql/my.cnf’s [mysqld] section. Then, I restarted the MariaDB service and at the same time monitoring the logs written to /var/log/syslog. Unfortunately, the logs written were not the same as the timestamp of the /var/log/syslog file itself.

date && ls -l /var/log/syslog && tail -n 1 /var/log/syslog

Thu Nov 13 12:37:34 SGT 2014 -rw-r----- 1 syslog adm 152802 Nov 13 12:37 /var/log/syslog Nov 12 23:37:32 droplet /etc/mysql/debian-start[24396]: Triggering myisam-recover for all MyISAM tables

This also applies to all the contents of the /var/log/*

recently i can sync ntp with my sg droplet. anyone of you able to do so to confirm ?

Found a good solution. Get your time from Google’s HTTP headers:

date -s "$(wget -S  "" 2>&1 | grep -E '^[[:space:]]*[dD]ate:' | sed 's/^[[:space:]]*[dD]ate:[[:space:]]*//' | head -1l | awk '{print $1, $3, $2,  $5 ,"GMT", $4 }' | sed 's/,//')"


Very simple workaround: date -s “2014-08-23 21:36:00” :) Hopefully the server uses high grade quartz crystal

Same here. Any update?

I think Digitalocean should at least give us an alternative way to sync our time. Time and date are almost the most important factor between servers. How we gonna work with those servers that don’t have synced time? All we need is a “method” not just “Unfortunately, NTP is still filtered” , “Unfortunately, NTP is still block”…what the f… By the way, this issue has been occurred about 3 months ago, and staff still saying “Unfortunately…” until today. Is this how Digitalocean solving critical problem?

Same here. Is there any workaround?

I still can’t sync time for my server. Any solution?

I’ve gone on and on about this with DO customer service, but with no suitable fix or work-around in sight.

DO uses Equinix for their servers in Singapore. What I’ve done is to ask Equinix directly for a local ntp server. Email them at Maybe if they receive enough requests, this will actually be done.

Same problem here – obvious solution seems to be for DO to spin-up, exclusively for customers to sync against, without compromising the upstream efforts to mitigate the NTP reflection attack?