The issue I am facing:
I am unable to access the Pi-hole web interface via http://pi.hole or http://pi.hole/admin. I am able to access the web interface via IP address.
Details about my system:
Pi-hole is hosted on a Raspberry Pi 3 B+ that is running Bullseye, tested access to web interface via a Windows PC on LAN, a Windows PC on WiFi, and an Android phone on WiFi.
What I have changed since installing Pi-hole:
I have updated Pi-hole any any installed packages.
This is a good indicator that the client on which you are running the browser and trying to access the web admin GUI is not using Pi-hole for DNS. Only Pi-hole can resolve the pi.hole domain name to the Pi-hole IP.
From that client, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of
nslookup pi.hole
nslookup flurry.com
The IP address that it returns for pi.hole is odd, because it's not part of the ranges that I generally see on my internal network.
$ nslookup pi.hole
Server: 172.21.64.1
Address: 172.21.64.1#53
Name: pi.hole
Address: fe80::56ab:3749:3ea8:d494
$ nslookup flurry.com
Server: 172.21.64.1
Address: 172.21.64.1#53
Name: flurry.com
Address: ::
Are you running Pi-hole in Docker, or on bare metal?
I'm running on bare metal.
Please upload a debug log and post just the token URL 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
Debug Token: https://tricorder.pi-hole.net/R81dKuTo/
(I appreciate the amount of effort that was put into developing a method of debugging issues without needing the user to publicly post personal information. That is awesome.)
Your interfaces on the Pi have an unusual setup - both wlan0 and eth0 have the same IP.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] onfize-seth.cainus.teradatadmc.com is 0.0.0.0 on lo (127.0.0.1)
[✓] onfize-seth.cainus.teradatadmc.com is 0.0.0.0 on eth0 (192.168.1.10)
[✓] onfize-seth.cainus.teradatadmc.com is 0.0.0.0 on wlan0 (192.168.1.10)
[✓] doubleclick.com is 142.251.40.142 via a remote, public DNS server (8.8.8.8)
Pi-hole is configured for the eth0 interface:
*** [ DIAGNOSING ]: Setup variables
...
PIHOLE_INTERFACE=eth0
Is there a reason you have two interfaces with the same IP?
What are the outputs of the following from a client other than the Pi? Use the command prompt or terminal on the device, and not via a ssh session to the Pi.
nslookup pi.hole 192.168.1.10
nslookup flurry.com 192.168.1.10
I think the problem is that on the Pi I had designated a static IP for eth0, and on my router I reserved the router for the device. At some point, the ethernet cable became disconnected and it seems like it just switched the IP address over to wlan0 since the router wanted to assign it anyway. What's really odd is that this disconnect must have happened months ago, yet I only recently started to have problems with reaching the web interface.
In an effort to see if the problem was related to being on the wrong interface, I reconnected the ethernet cable last night and before making this post, confirmed that eth0 was now using the correct IP address, and confirmed that it had not resolved the issue.
$ nslookup pi.hole 192.168.1.10
Server: 192.168.1.10
Address: 192.168.1.10#53
Name: pi.hole
Address: 192.168.1.10
Name: pi.hole
Address: fe80::56ab:3749:3ea8:d494
$ nslookup flurry.com 192.168.1.10
Server: 192.168.1.10
Address: 192.168.1.10#53
Name: flurry.com
Address: 0.0.0.0
Name: flurry.com
Address: ::
Is there any way to fully flush the assignment of the IP address to the wlan interface? Would that help?
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.