but I can't access: http://<IP_ADDPRESS_OF_RASPBERRY_PI>/admin/ on the PI, nor can I access it from another device or computer on my local LAN using any of the methods above (obviously 127.0.0.1 won't work by design).
Re: PiHole web interface is reachable only from the Raspberry Pi itself.
I have a similar problem - Any other machine on the LAN errors out with ERR_CONNECTION_TIMED_OUT. This occurs using either http://pi.hole/admin or http://192.168.0.250/admin (and both of these methods work just fine from the GUI on the Pi itself). All diagnostics show as fine and PiHole blocking works just fine for all clients. SSH connection to the Pi works fine as well.
I was using a Raspberry Pi Zero W with this issue, and after several attempts to fix it (including a wipe/reinstall of Raspbian and PiHole) I switched to a Raspberry Pi 3B+. Same issue here as well.
The following debug token was obtained using SSH from a client machine: lsxkblqr5q
DHCP & Network routing is provided by pfSense 2.5.1 on a different machine, and it is configured to have clients use the PiHole for DNS.
Your debug log shows Pi-hole's network connectivity is flawed:
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.4/24 does not match the IP found in /etc/pihole/setupVars.conf
The PIHole eth0 runs under static IP address 192.168.1.4.
So I assume I have to change:
IPV4_ADDRESS=192.168.1.4 in the script that runs the docker container for pihole (rather point to the localmachine)?