FPP 8.3 on Pi 4B, can't get it to show correct date/time via NTP

[geeman1082]

Hi All.  I'm new at this, so I'm sure I'm missing something simple.  I set up a Raspberry Pi 4B with FPP 8.3 and am able to access it via ethernet.  It has internet access (e.g., it displays the remote Git version), but it's showing a date in September.  The only message in the health check is "Your FPP system date/time is significantly different to the browser, please verify".  Same results if I leave the NTP at the default or use time.google.com.  RTC set to none, time zone set to America\Chicago by using the lookup button.

Note: the date/time isn't critical to my intended application (a stand-alone setup driving a single F16V4, repeating a sequence continuously), but it implies that I don't have something set up correctly.

My F16V4 is able to get the current time/date from time.google.com, which apparently was the default because I didn't change that.

Any suggestions?  Thanks.

[JonD]

There have been some NTP issues with 8.x.  I did not have any with 8.3.  The FPP device would need to have internet and working DNS to update.  What happens if you enter an IP instead of DNS name?  Try using NTP server 132.163.97.2 and see what happens.

[Poporacer]

Same results if I leave the NTP at the default

The default and recommended setting is to leave this blank. You should only set something here in special use cases. It does take a few seconds for the FPP to update when powered up. But I have seen issues getting the correct time when the network settings were not correct (Typically the DNS Server)

[geeman1082]

There have been some NTP issues with 8.x.  I did not have any with 8.3.  The FPP device would need to have internet and working DNS to update.  What happens if you enter an IP instead of DNS name?  Try using NTP server 132.163.97.2 and see what happens.

Thanks for the reply.  It has access to the internet, and current DNS settings are (1) my router and (2) 8.8.8.8.  Using the IP you provided did not change anything, even after a reboot.

[geeman1082]

The default and recommended setting is to leave this blank. You should only set something here in special use cases. It does take a few seconds for the FPP to update when powered up. But I have seen issues getting the correct time when the network settings were not correct (Typically the DNS Server)

I understand about the default, and tried the google site as a troubleshooting step.  DNS is set to (1) my router and (2) 8.8.8.8.  

FYI, I previously had the IP address and DNS set to DHCP with the same results, but I have since set static addresses because I'm going to take this setup to another location for a demo.

[JonD]

There are some NTP issues listed on Github yet.

If you are technical, you might be able to take a look at your ntp.conf file and see what your minsane value is.

https://falconchristmas.com/forum/index.php?topic=16907.msg135260#msg135260

No other suggestions... sorry!

[geeman1082]

No other suggestions... sorry!

Thanks for looking at it.

[JonD]

Thanks for looking at it.

If someone else does not respond you could try re-imaging with an older version of FPP, or stopping by the xLights Zoom Room.

[geeman1082]

Update:  It started working.  I've made several changes based on the above suggestions and things I've found online, so I can't be 100% certain regarding exactly what fixed it (yes, I know, that's not good troubleshooting practice, but I was getting frustrated and lapsed into thrashing), but I believe it was manually changing the DNS settings from what I listed above to (1) 8.8.8.8 and (2) 8.8.4.4, while returning everything else to defaults.

Thanks for the replies.