Web interface (or is it admin console?) at pi.hole displays a graphical user interface
Pi-hole blocks ads after setting my internet router to use my RaspberryPi's static IP as a DNS
Hardware: Raspberry PI 4 Model B
Operating System: Debian GNU/Linux 12
Tried connecting to pi.hole(/admin) (and static_ip_address/admin) on LibreWolf, Firefox and Safari
Actual Behaviour:
The web interface displays as simply a HTML file on Safari and a white page with text on LibreWolf/Firefox. The console says:
This page is in Quirks Mode. Page layout may be impacted.
[✗] tcp:*:80 is in use by apache2 (https://docs.pi-hole.net/main/prerequisites/#ports)
Lighttpd is our shipped web server in V5 and earlier. With apache2 sitting on port 80, lighttpd cannot bind to that port.
*** [ DIAGNOSING ]: Dashboard headers
[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Thu, 18 Jul 2024 17:12:42 GMT
Server: Apache/2.4.59 (Debian)
Last-Modified: Thu, 18 Jul 2024 16:30:36 GMT
ETag: "27b2-61d8819435136"
Accept-Ranges: bytes
Content-Length: 10162
*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is failed
[✓] pihole-FTL daemon is active
You have Pi-hole configured for interface eth0, but there is no active interface there:
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
[✗] No IPv6 address(es) found on the eth0 interface.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] sexyplussizetops.com is 0.0.0.0 on lo (127.0.0.1)
[✓] No IPv4 address available on eth0
[✓] sexyplussizetops.com is 0.0.0.0 on wlan0 (192.168.1.150)
[✓] doubleclick.com is 142.250.180.14 via a remote, public DNS server (8.8.8.8)
You do have an active wlan0 interface, and that is how the Pi is connecting to your network.
Run pihole -r and select the reconfigure option to get Pi-hole onto the wlan0 interface.