Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
Should just keep working…
- Latest ubuntu, updated
- Hardware is in the log file
-
Actual Behaviour:
Web Interface not accessible after day or two but still blocking. I can ssh in just fine.
If i reboot the pihole the interface works again, and you can see it was still blocking just fine. Its a fresh install with just pihole running, and nothing additional.
Debug Token:
https://tricorder.pi-hole.net/hwvXUmI2/
How did you configure your network to make use of Pi-hole?
Your debug log shows that your router is advertising its own GUA IPv6 as DNS server:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 6 seconds)
Scanning all your interfaces for DHCP servers and IPv6 routers
* Received 112 bytes from fe80::3e<redacted>1 @ wlx<redacted>
Hop limit: 64
Stateful address conf.: No
Stateful other conf.: Yes
Mobile home agent: No
Router preference: Medium
Neighbor discovery proxy: No
Router lifetime: 900 s
(…)
Recursive DNS server 1/1: 2600:<redacted>00::1
That could be a valid configuration, as long as your router would use Pi-hole as its sole upstream DNS server (but note that you won't be able to attribute DNS requests to individual clients in such a configuration).
I just followed the config on the website. After which I configured the router to assign a static ip for the pihole. I manually set clients to the pihole dns, as i dont want all devices going through it.
Then you want to verify your client's IPv6 DNS configuration.
Since your router is advertising itself, an IPv6 capable client may pick that up and prefer to use that instead of Pi-hole.
And if it does so, not only would it by-pass Pi-hole, but you also wouldn't be able to access http://pi.hole, as only Pi-hole knows to resolve pi.hole.
So I thinking about this, i realized i set IPv4 to static for the pihole but the IPv6 changes(made a note of what it was and looked again today), i don’t really see an option on the router to have this be static?
edit * I’ve changed the router from Stateless to Stateful. They’re getting v6 ips now from the router, but still dont see a way to make them static.
My recommendation was to check your clients and configure the IPv6 DNS servers they are using, so they would ignore your router advertisements.
Why did you fiddle with your router's configuration instead?
Since you intend to manually configure the few clients that you want to use Pi-hole, you have to do so for IPv4 as well as IPv6.
Configuring your router would affect all clients, thus contradicting your intention.
The clients ipv6 dns which I’ve put in manually to point to the pi-hole has changed, and I’m assuming this is what is causing the issue? As the Pi-hole would need a static ipv6, this is why i looked into the router settings to try set the pi-hole’s ipv6 to static? Is this not the way to do it?
The client's IPv6 is not required to be fixed.
But you'd have to pick one of your Pi-hole machine's stable IPv6 addresses as DNS server address, so you should avoid its temporary addresses and also GUAs (range 2000::/3).
When run from your Pi-hole machine, the following command lists all its non-temporary IPv6 addresses:
ip -6 address show eth0 -temporary
Substitute eth0 with your Pi-hole machine's actual network interface name as required.
You could then use either one of its ULA (range fd00::/8) or LLA (range fe80::/10) addresses and configure that as DNS server in your client.
I see, I’m now using the fe80 one. That makes sense to me now, thank you for your help!
The alternative is to not use any IPv6 DNS Server at all so your Client uses IPv4 for IPv6 DNS Queries instead 