Lost conn to API and FTL

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

Expected Behaviour:

Pi hole admin to show stats

Actual Behaviour:

Lost connection to API and FTL is offline

Debug Token:

suxpevrryn

A few poblems are showing in the debug log - Pi-Hole does not appear to be listening on the IP address.

Did you intend to use a /8 subnet mask for your network? That's what the Pi IP is on.

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the wlan0 interface:
   10.249.157.50/8 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)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] hananokai.tv is 3.115.199.44 via localhost (127.0.0.1)
[✗] Failed to resolve hananokai.tv via Pi-hole (10.249.157.50)
[✓] doubleclick.com is 172.217.3.238 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=wlan0
    IPV4_ADDRESS=10.249.157.50

What is the output of this command from the Pi terminal:

sudo service pihole-FTL status

I didn't...

pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated)
   Active: active (exited) since Fri 2019-11-01 18:38:39 EDT; 25min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4277 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SU

Nov 01 18:38:38 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 01 18:38:38 raspberrypi pihole-FTL[4277]: Not running
Nov 01 18:38:38 raspberrypi su[4306]: (to pihole) root on none
Nov 01 18:38:38 raspberrypi su[4306]: pam_unix(su:session): session opened for u
Nov 01 18:38:39 raspberrypi pihole-FTL[4277]: dnsmasq: failed to create listenin
Nov 01 18:38:39 raspberrypi su[4306]: pam_unix(su:session): session closed for u
Nov 01 18:38:39 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.

This typically indicates a port conflict problem. What is the output of the following command from the Pi terminal:

sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:8953 \|:67 \|:80 \|:471'

When you post the reply, ensure you don't cut off the right side of the reply. You can format it as pre-formatted text with this command tool on the reply window:

That come in correctly?

3 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      507/lighttpd        
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      525/unbound        
tcp6       0      0 :::80                   :::*                    LISTEN      507/lighttpd        
tcp6       0      0 ::1:53                  :::*                    LISTEN      525/unbound        
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           1014/chromium-brows
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           953/libpepflashplay
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 127.0.0.1:53            0.0.0.0:*                           525/unbound        
udp6       0      0 :::5353                 :::*                                371/avahi-daemon: r
udp6       0      0 ::1:53                  :::*                                525/unbound 

Yes, it did, and the line above shows the problem. You have unbound listening on port 53, which does not allow pihole-FTL to launch on that port.

Unbound needs to be on another port, typically 5353 if you use the Pi-Hole setup guide for unbound:

https://docs.pi-hole.net/guides/unbound/

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