But timedatectl always shows: NTP synchronized: no
timedatectl
Local time: Sun 2020-11-08 12:07:16 EST
Universal time: Sun 2020-11-08 17:07:16 UTC
RTC time: Sun 2020-11-08 22:07:44
Time zone: America/New_York (EST, -0500)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: no
Last DST change: DST ended at
Sun 2020-11-01 01:59:59 EDT
Sun 2020-11-01 01:00:00 EST
Next DST change: DST begins (the clock jumps one hour forward) at
Sun 2021-03-14 01:59:59 EST
Sun 2021-03-14 03:00:00 EDT
ntpdate pool.ntp.org
8 Nov 12:14:32 ntpdate[11866]: no server suitable for synchronization found
ntpdate 64.79.100.196
8 Nov 12:06:24 ntpdate[11104]: no server suitable for synchronization found
I’ve tried rebooting after setting TimeZone in SystemAdmin and it’s also set in asterisk advanced settings.
Any clue on what I’m missing?
This is my first instance using FreePBX 15 and previous versions syncing with NTP required no human intervention.
[solved] Thank you @dicko@Stewart1
The issue was due to blocked services at my VPS provider. They implemented their own ntp servers to help combat the exposure of ntp amplification attacks.
Thanks for the reply, but even if the ISP were blocking
that port, I should still be able to turn on synchronization (which is
not in my subject, I now realize).
I don’t think the ISP is blocking it as I get the same results from my workstation at home.
I will contact my VPS provider to see if they are firewalling anything. I haven’t had
any ports blocked by the provider in the past and this machine was running FreePBX 14 without issues up until a few weeks ago.
Just watch tcpdump port 123 for a few minutes or more, you should see your machine sending packets to request TIME and (not always but sometimes) packets coming in from the same servers you are using sending you TIME.