the pihole should be operating normally; pihole status returns good status for DNS and FTL
ads aren't blocked on any devices on the network, and the pihole admin shows the "lost connection to API" message
7tfd6m2zjh
Your debug log shows that dnsmasq is running on port 53 - this will keep pihole-FTL from launching and binding to that port. With FTLDNS (as of V4.0), dnsmasq should not be running, as FTLDNS does the work previously done by dnsmasq.
*** [ DIAGNOSING ]: Ports in use
*:53 dnsmasq (IPv4)
*:53 dnsmasq (IPv6)
*:80 lighttpd (IPv4)
*:80 lighttpd (IPv6)
...
If pihole-FTL is running, you should typically see this (or something similar) in this section of the debug log, with pihole-FTL on ports 53 and 4711.
*** [ DIAGNOSING ]: Ports in use
...
*:53 pihole-FTL (IPv4)
*:53 pihole-FTL (IPv6)
127.0.0.1:4711 pihole-FTL (IPv4)
[::1]:4711 pihole-FTL (IPv6)
As a result of this, DNS resolution isn't occurring on the Pi-Hole:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] se-group.de is via localhost (127.0.0.1)
[✓] se-group.de is via Pi-hole (192.168.1.18)
Run this command to see what processes are on these ports and post the results:
sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Thanks! I found a similar suggestion (perhaps even from you?) in another help thread after I posted this, and disabling dnsmasq then restarting pihole-FTL fixed it for me.
Do you have any recommendations for how I can do bypasses for individual devices without dnsmasq?
Chad
Change the individual device's DNS server to something other than Pi-hole.
Changing settings on the devices isn't a viable option here.; they're some else's phone, tablet, and laptop, and they're not always on my network. I had a pretty simple passthrough set up based on mac address before pihole 4, but I don't think it'll work without dnsmasq.
All of the dnsmasq settings will work with FTL, because FTL simply has an embedded dnsmasq inside of it.