Pi-hole was working perfectly yesterday when installing fresh on a fresh Raspbian Buster.
Then today there were some problems. Here they are in chronological order:
Unable to open web interface (DNS service was still running fine)
Followed commands at Use IPv6 ULA addresses for Pi-hole as recommended after doing pihole -d but this didn't help, instead made DNS service not run anymore
Tried updating pihole but could not access FTL: [✗] Downloading and Installing FTL Error: Unable to get latest release location from GitHub
Tried re-installing pi-hole but could not access pihole.net or ping anything
There are a couple of problems with your networking. The IPv4 can not ping the gateway / router, IPv6 is not set up correctly (do you have IPv6 from your ISP? Do you need IPv6?). Looking over the debug log it will be easier to just start over fresh with a new SD image of Raspbian.
Thank you. I reinstalled everything and it works as expected. However, when I then do pihole -d I have some IPv6 errors still. Do I need to fix this somehow? I am worried that it will stop working as before. The debug token is below:
Do you need IPv6 enabled? Check jhttps://ipv6-test.com/ and see if IPv6 connectivity is supported. If not, then you won't gain anything by having Pi-hole with a ULA and you'll just add more complexity.
The debug log still shows that IPv4 is not correct:
[i] Default IPv4 gateway: 192.168.1.1
192.168.1.1
* Pinging 192.168.1.1
192.168.1.1...
[✗] Gateway did not respond.
No I don't need IPv6. How can I remove this? And I'm not sure why the IPv4 is not correct, is it an issue with the router or the configuration of the pi?
Undo the steps that you took to enable ULA on the router / network. And I don't know why IPv4 is not working correctly, can you ping 192.168.1.1 from the command line?
I don't think I did anything to enable ULA on my router. I just did a reconfiguration and chose the setting to ignore IPv6 upon installation. However I did pihole -d again and had the same errors as before.
Yes, ping 192.168.1.1 works fine, despite the error on pihole -d.
Could these issues be to do with my router having its own firewall? I also enabled ufw on my pi (although I allowed ssh).
Okay, that looks fine. The IPv6 address won't be used, it is being assigned to the Pi-hole device via the router. If you want to disable it across the entire local network then you would need to disable it at the router itself.
Can you post the output from ip -4 address list and ip route get 192.168.1.1 to see what may be causing the debug script to incorrectly report that the gateway is not responding?
$ ip -4 address list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 192.168.1.7/24 brd 192.168.1.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 192.168.1.5/24 brd 192.168.1.255 scope global noprefixroute wlan0
valid_lft forever preferred_lft forever
$ ip route get 192.168.1.1
192.168.1.1 dev eth0 src 192.168.1.7 uid 1000
cache
pi@pi:~ $
Okay, having both may be what is confusing the debugger, it's not quite smart enough to know and it may be trying to ping via wlan0 instead of eth0. I think everything should be good to go now.
Ok, so I turned wifi off and rebooted. pihole -d no longer has the IPv4 error, but still has some errors (debug token below). It's still working though so I just wondered if you could take a look and see if it's anything of concern? Thanks!