The issue I am facing:
NTP error
Using latest Pihole beta, and keep getting this NTP error! Just no idea how to fix. Pihole is plugged into a TP-Link switch which is plugged into a UDM Pro. The switch is getting time fine from NTP servers. Why is the Pihole kicking up a fuss!?
Attached screenshots of my settings too. I’ve tried pool.ntp.gov instead of uk.pool and same problem.
When I type in Date in SSH it is correct and exact.
Details about my system:
Homebridge and Pihole setup.
We've meanwhile heard about several routers that block upstream NTP traffic and don't really have a good solution for this right now. We may have to check for NTP servers broadcasted by the local DHCP server first and default to this if the user didn't configure anything specific.
Please log into your Pi-hole and run
pihole-FTL ntp 1.uk.pool.ntp.org
manually.
What is the output?
How does it look like if you use your local router's IP address instead of the pool server?
Hi. Thanks for the reply.
Output:
pi@homebridge:~ $ pihole-FTL ntp 1.uk.pool.ntp.org
Using NTP server: 1.uk.pool.ntp.org
Config file /etc/pihole/pihole.toml not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.1 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.2 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.3 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.4 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.5 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.6 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.7 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.8 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.9 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.10 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.11 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.12 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.13 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.14 not available: Permission denied
No config file nor backup available, using defaults
No readable FTL config file found, using default settings
Migrating config from /etc/pihole/setupVars.conf
Could not move /etc/pihole/setupVars.conf to /etc/pihole/setupVars.conf.old
Initialised webserver ports at 80 (HTTP) and 443 (HTTPS), IPv6 support is enabled
Config file /etc/pihole/pihole.toml.tmp not available: Permission denied
Cannot write to FTL config file (No error information), content not updated
Cannot open /etc/pihole/dnsmasq.conf.temp for writing, unable to update dnsmasq configuration: Permission denied
Cannot open /etc/pihole/custom.list.tmp for writing, unable to update custom.list: Permission denied
........
Received 8/8 valid NTP replies from 1.uk.pool.ntp.org
Time offset: -1.840557e+00 ms (excluded 1 outliers)
Round-trip delay: 1.804985e+01 ms (excluded 1 outliers)
pi@homebridge:~
And using router ip (Unifi Dream Machine Pro)
pi@homebridge:~ $ pihole-FTL ntp 10.0.0.1
Using NTP server: 10.0.0.1
Config file /etc/pihole/pihole.toml not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.1 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.2 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.3 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.4 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.5 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.6 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.7 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.8 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.9 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.10 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.11 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.12 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.13 not available: Permission denied
Config backup file /etc/pihole/config_backups/pihole.toml.14 not available: Permission denied
No config file nor backup available, using defaults
No readable FTL config file found, using default settings
Migrating config from /etc/pihole/setupVars.conf
Could not move /etc/pihole/setupVars.conf to /etc/pihole/setupVars.conf.old
Initialised webserver ports at 80 (HTTP) and 443 (HTTPS), IPv6 support is enabled
Config file /etc/pihole/pihole.toml.tmp not available: Permission denied
Cannot write to FTL config file (No error information), content not updated
Cannot open /etc/pihole/dnsmasq.conf.temp for writing, unable to update dnsmasq configuration: Permission denied
Cannot open /etc/pihole/custom.list.tmp for writing, unable to update custom.list: Permission denied
Could not recv() in reply() (/app/src/ntp/client.c:222): Connection refused
Failed to receive data from NTP server 10.0.0.1: Connection refused
Could not recv() in reply() (/app/src/ntp/client.c:222): Connection refused
Failed to receive data from NTP server 10.0.0.1: Connection refused
Could not recv() in reply() (/app/src/ntp/client.c:222): Connection refused
Failed to receive data from NTP server 10.0.0.1: Connection refused
Could not recv() in reply() (/app/src/ntp/client.c:222): Connection refused
Failed to receive data from NTP server 10.0.0.1: Connection refused
Could not recv() in reply() (/app/src/ntp/client.c:222): Connection refused
Failed to receive data from NTP server 10.0.0.1: Connection refused
Could not recv() in reply() (/app/src/ntp/client.c:222): Connection refused
Failed to receive data from NTP server 10.0.0.1: Connection refused
Could not recv() in reply() (/app/src/ntp/client.c:222): Resource temporarily unavailable
Failed to receive data from NTP server 10.0.0.1: Timeout
Could not recv() in reply() (/app/src/ntp/client.c:222): Connection refused
Failed to receive data from NTP server 10.0.0.1: Connection refused
Warning NTP client: No valid NTP replies received, check server and network connectivity
pi@homebridge:~ $
Thanks for your reply, this looks fine - in principle! The many warnings indicate that you ran pihole-FTL on a system where Pi-hole isn't even installed though - no config files and not even some mandatory directories exist!
This shows time synchronization with 1.uk.pool.ntp.org worked in your testing. Following your configuration, your Pi-hole is trying to sync its time every 3600 seconds (once per hour) - could it be that you haven't had Internet when this warning was generated?
Could you also test whether the warning re-appears after manually deleting it? If so, does it immediately reappear (within one hour after deleting it) or does it take longer to reappear?
Haha that’s odd! It was installed on the Homebridge config menu, and then immediately updated to the V6 beta branch. It seems to be blocking and doing unbound ok. Is those errors something I should be concerned about and need to fix?
I can delete the error message and it might come back next morning or might not even come back till a week later.
This is not supported at all and a third-party integration I'm not even familiar with. I guess - whoever is responsible from the homebridge community - they have missed something and we cannot actually be of much help here. Sorry to say that.
No and from your description
it really sounds like to be generated because the server is not reachable at times from your Internet connection. Nothing really to be worried about.
Ah no way, sounds like something the Homebridge has cooked up. Been using it few years, saves having two Raspberry Pis running.
Ah ok, thank you, makes sense :). Thanks for your help 
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.