DNSMASQ_CONFIG

FTL failed to start due to failed to bind DHCP server socket: Address already in use

You will need to disable the other instance of dnsmasq.

There isn't another instance, I am sure of it

Please upload a debug log and post just the token that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

https://tricorder.pi-hole.net/5hxsffvqrl

I need pihole urgently, It the only DNS on all device on my network

[53] is in use by dnsmasq (https://docs.pi-hole.net/main/prerequisites/#ports)
[53] is in use by dnsmasq (https://docs.pi-hole.net/main/prerequisites/#ports)

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.1.91/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)
   192.168.1.201/24 matches the IP found in /etc/pihole/setupVars.conf

don't know where 192.168.1.91 is from

This is the IP bound to eth0 on your Pi-hole device.

Run pihole -r and choose reconfigure to set the listening IP.


Did you also notice, that you are running a dnsmasq instance on your device as well....

eth0 192.168.1.201 is my listening IP
and eth0:5 192.168.1.205 Vlan

and dnsmasq should just be running under pihole

Pi-hole has dnsmasq "built in". You need to disable and stop dnsmasq and restart Pi-hole.

systemctl mask dnsmasq.service

never had to do that before

but it fixed it

Thank You For you help

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