I have the same issue. However it was temporary fixed when I typed "pihole checkout master" in terminal. The DNS service and FTL will run after that, however upon restart, the problem will come back and every restart scheduled or not, I will always have to run terminal and do the checkout master command to get it to work. Can this be permanent?
Am running Ubuntu 16.04
Please post the token generated by
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Your debug log shows a dnsmasq process on port 53, which prevents pihole-FTL from binding to this port.
[53] is in use by dnsmasq (https://discourse.pi-hole.net/t/hardware-software-requirements/273#ports)
I see. So port 53 has a process on it. As a Linux noob, how do I either find out what is using port 53, and or can I change the port ?
This command will show you all the processes running on ports used by Pi-hole and programs frequently installed alongside Pi-hole.
sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:5335 \|:8953 \|:67 \|:80 \|:471'
From there, we can figure out what's running and stop it.
I did as suggested and ran the command line after I restarted pihole. The DNS service and FTL is not running. The command line output was this:
jocasta@jocasta:~$ sudo netstat -nltup | grep 'Proto|:53 |:5053 |:5353 |:5335 |:8953 |:67 |:80 |:471'
[sudo] password for jocasta:
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 1450/lighttpd
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1791/dnsmasq
tcp6 0 0 :::80 :::* LISTEN 1450/lighttpd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1247/avahi-daemon:
udp 0 0 127.0.1.1:53 0.0.0.0:* 1791/dnsmasq
udp6 0 0 :::5353 :::* 1247/avahi-daemon:
Had to run "pihole checkout master" then I re visited the command again and got this:
jocasta@jocasta:~$ sudo netstat -nltup | grep 'Proto|:53 |:5053 |:5353 |:5335 |:8953 |:67 |:80 |:471'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 5944/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 5792/lighttpd
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 5944/pihole-FTL
tcp 0 0 192.168.1.183:53 0.0.0.0:* LISTEN 5944/pihole-FTL
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1791/dnsmasq
tcp6 0 0 ::1:4711 :::* LISTEN 5944/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 5792/lighttpd
tcp6 0 0 ::1:53 :::* LISTEN 5944/pihole-FTL
tcp6 0 0 fe80::9921:591d:f2f3:53 :::* LISTEN 5944/pihole-FTL
tcp6 0 0 fe80::e453:9181:63c4:53 :::* LISTEN 5944/pihole-FTL
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1247/avahi-daemon:
udp 0 0 127.0.0.1:53 0.0.0.0:* 5944/pihole-FTL
udp 0 0 192.168.1.183:53 0.0.0.0:* 5944/pihole-FTL
udp 0 0 127.0.1.1:53 0.0.0.0:* 1791/dnsmasq
udp6 0 0 :::5353 :::* 1247/avahi-daemon:
udp6 0 0 ::1:53 :::* 5944/pihole-FTL
udp6 0 0 fe80::9921:591d:f2f3:53 :::* 5944/pihole-FTL
udp6 0 0 fe80::e453:9181:63c4:53 :::* 5944/pihole-FTL
The common denominator seems to be the DNSmasq 127.0.1.1
Could not figure what was on port 53. I removed and re-installed a fresh copy of Pihole V5, changed the port to another one and it works. Thanks for your help. This version seems to be faster at blocking ads and runs very smoothly with Ubuntu 16.04.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.