Cannot access pihole web console

Help
1

I've been unable to access the web console from any machine on my network - even running links http://pi.hole from a console on the Pi itself is giving "connection refused". I'm running pi-hole on a Pi 4:

$ uname -a
Linux pihole 6.12.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.20-1+rpt1~bpo12+1 (2025-03-19) aarch64 GNU/Linux

Expected Behaviour:

http://pi.hole/ should load the console

Actual Behaviour:

The connection is refused

Debug Token:

https://tricorder.pi-hole.net/xXfuKxuq/

2

The web server is not starting:

2025-04-26 08:40:29.549 CDT [1119M] ERROR: Start of webserver failed!. Web interface will not be available!
2025-04-26 08:40:29.549 CDT [1119M] ERROR:        Error: Failed to setup server ports (error code 10.0)
2025-04-26 08:40:29.549 CDT [1119M] ERROR:        Hint: Check the webserver log at /var/log/pihole/webserver.log

webserver log:

[2025-04-26 08:25:15.977 CDT 1953580] Initializing HTTP server on ports "8080o,443os,[::]:8080o,[::]:443"
[2025-04-26 08:25:15.982 CDT 1953580] cannot create socket (entry 3)
[2025-04-26 08:25:15.984 CDT 1953580] cannot create socket (entry 4)
[2025-04-26 08:25:15.984 CDT 1953580] Failed to setup server ports
[2025-04-26 08:40:29.544 CDT 1119] Initializing HTTP server on ports "8080o,443os,[::]:8080o,[::]:443"
[2025-04-26 08:40:29.548 CDT 1119] cannot create socket (entry 3)
[2025-04-26 08:40:29.549 CDT 1119] cannot create socket (entry 4)
[2025-04-26 08:40:29.549 CDT 1119] Failed to setup server ports

cannot create socket

This is probably a permission issue.

3

Per V6 web interface can't be loaded, I found the issue: it seems the IPv6 interfaces have disappeared from my system, so the HTTP server could not use them. I changed the ports to "80o,443os" and it's a-ok now. Thank you! (I still need to figure out what happened to ipv6 on my system though... :thinking:)

4

Postscript: it did seem like something was fishy with my ipv6 module:

$ sudo modprobe ipv6
modprobe: ERROR: could not insert 'ipv6': Unknown symbol in module, or unknown parameter (see dmesg)

(nothing useful was in dmesg that I could see)

Reinstalling the kernel Debian package seemed to fix things; in addition, changing the port settings back to the default with ipv6 bindings worked. :slight_smile: