FTL not running

I had Pihole installed and running yesterday, then today had some network issues. Resolved the network problem and back on line and FTL was not running. Tried several solutions found on the net to no avail. Finally, I uninstalled and reinstalled again, FTL still not running.

This is on A Debian Buster server.

Please follow the below template, it will help us to help you!

Expected Behaviour:

Expected FTL to run

Actual Behaviour:

FTL not running

Debug Token:

https://tricorder.pi-hole.net/13dko7osoi

Looks like you have the wrong IP address configured.

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the br0 interface:
   10.1.1.253/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
   10.1.1.1/24 matches the IP found in /etc/pihole/setupVars.conf

[✗] No IPv6 address(es) found on the br0 interface.

[i] Default IPv4 gateway: <Public IP redacted>
   * Pinging <Public IP redacted>...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

Edit: Also apache2 is blocking lighttpd from running. You have to configured apache2 to handle the Pi-hole admin interface properly if that is what you want to use.

[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Thu, 13 Feb 2020 18:27:58 GMT
Server: Apache/2.4.25 (Debian)
Last-Modified: Mon, 26 Jun 2017 17:29:51 GMT
ETag: "29cd-552e04c60f172"
Accept-Ranges: bytes
Content-Length: 10701
Vary: Accept-Encoding
Content-Type: text/html


[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 404 Not Found
Date: Thu, 13 Feb 2020 18:27:58 GMT
Server: Apache/2.4.25 (Debian)
Content-Type: text/html; charset=iso-8859-1

How do I have the wrong IP? My LAN is multi-homed with two IP on same subnet, both 10.1.1.1 and 10.1.1.253 respond to those addresses on my br0 interface.

My apache is setup to handle the admin interface and I can access the admin web UI at 10.1.1.1/admin.

My gateway is 47.152.1.1 and responds to ping, why the diagnosic doesn’t see it I don’t know.

As I said everything looks fine from the web interface https://share.polymicro.net/1581627802.png

BTW, had same errors when it was working.

what does pihole status show?
are you able to ping out to the internet from your server and can clients ping it?

yes and yes
[pve]/root/src/…hole/automated install (581): pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

Do you have anything installed that could be preventing FTL from starting like anything that relies on dnsmasq although FTL should disable dnsmasq when installed

No, as I said it was working, now it doesn’t, even after a reinstall.

Does pihole -v display FTL as installed?

[pve]/root/src/…hole/automated install (584): pihole -v
Pi-hole version is v4.3.2 (Latest: v4.3.2)
AdminLTE version is v4.3.2 (Latest: v4.3.2)
FTL version is v4.3.1 (Latest: v4.3.1)

What does systemctl status pihole-FTL.service show?

[pve]/root/src/…hole/automated install (585): sc status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Thu 2020-02-13 10:16:59 PST; 4h 9min ago
Docs: man:systemd-sysv-generator(8)
Process: 16549 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Feb 13 10:16:59 pve systemd[1]: Starting LSB: pihole-FTL daemon…
Feb 13 10:16:59 pve pihole-FTL[16549]: Not running
Feb 13 10:16:59 pve su[16578]: (to pihole) root on none
Feb 13 10:16:59 pve su[16578]: pam_unix(su:session): session opened for user pihole by (uid=0)
Feb 13 10:16:59 pve pihole-FTL[16549]: dnsmasq: failed to bind DHCP server socket: Address already in use
Feb 13 10:16:59 pve su[16578]: pam_unix(su:session): session closed for user pihole
Feb 13 10:16:59 pve systemd[1]: Started LSB: pihole-FTL daemon.

That was it, killed the dnsmasq and restarted pinhole, now running

1 Like

What was it? you had dnsmasq installed?

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.