I just installed a new router at home and everything was working fine except that the Pi had been working for over a year without a reboot. I thought i would be nice to him and clicked on Settings -> restart systems.
Since then it stopped working. I reinstalled with the command pihole -r but to no avail.
Debug Token: https://tricorder.pi-hole.net/vkqbdydr9b
Any assistance would be greatly appreciated.
Many thanks and may we stay strong !
Annales
Welcome to the Pi-hole community, Annales. 
Your debug log shows your Pi-hole has been successfully introduced into your network, with full IPv4 and IPv6 connectivty.
It is also positively receiving, processing, blocking and forwarding DNS queries, if only from two clients (supposedly, your router plus Pi-hole itself):
Imported 32135 queries from the long-term database
-> Total DNS queries: 32135
-> Cached DNS queries: 4275
-> Forwarded DNS queries: 20704
-> Exactly blocked DNS queries: 7156
-> Unknown DNS queries: 0
-> Unique domains: 1899
-> Unique clients: 2
-> Known forward destinations: 2
This is perfectly normal if you configure your router to make use of Pi-hole as its upstream DNS server.
What cause do you have to consider Pi-hole as inoperational?
Thanks for the reply Bucking Horn,
I've been using PiHole for the past 18 months and didn't have any issue until this morning.
When I tell my router to use the pi-hole ip then i end up offline. I'll recheck everything on the router if you say the Pi is fine.
Thanks!
Since when do you use your new router? What's its make and model?
If it is less than 24 hours, the numbers above may actually still show your old router's traffic.
If you do not have name resolution with your new router and Pi-hole, there's a chance that your new router is disagreeing with delegating upstream DNS to a local address like Pi-hole.
Let's take a look at which processes are running on the Pi on ports used by Pi-hole and common Pi-hole companions. Please run the following command from the Pi terminal and post the complete output here:
sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:8953 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3838/lighttpd
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 564/unbound
tcp 0 0 127.0.0.1:8953 0.0.0.0:* LISTEN 564/unbound
tcp6 0 0 :::80 :::* LISTEN 3838/lighttpd
tcp6 0 0 ::1:53 :::* LISTEN 564/unbound
tcp6 0 0 ::1:8953 :::* LISTEN 564/unbound
udp 0 0 127.0.0.1:53 0.0.0.0:* 564/unbound
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1126/librespot
udp 0 0 0.0.0.0:5353 0.0.0.0:* 403/avahi-daemon: r
udp6 0 0 ::1:53 :::* 564/unbound
udp6 0 0 :::5353 :::* 403/avahi-daemon: r
udp6 0 0 :::5353 :::* 1126/librespot
I've just noticed that FTL is also offline.
Tried an uninstall and reinstallation. No change.
I've physically installed the router this morning.
The problem is that another process (unbound) has started on port 53. This process cannot run on port 53, since it conflicts with FTL on that port.
If you previously had unbound setup to work as the upstream resolver, then you will need to revisit your configuration files and put it on an alternate port (the Pi-hole guide puts it on 5353).
If you don't intend for unbound to run, then stop and uninstall it, and restart FTL.
sudo service unbound stop
sudo apt unbound remove
sudo service pihole-FTL start
I've ended up wiping the Pi and reinstalling everything. It seems to work now.
Fun thing is: i kept working on it and messing it up even further. At the end I couldn't even remotely access the Pi and it wouldn't connect to the Wi-Fi. Sometimes it's worth just calling it quits and starting fresh.
Thanks for the help to both of you.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.