Unable to access dashboard via IP despite ad blocking still working

Help
21

Oh ps, I addressed the wrong Pi while testing above :wink:
Below is what I get when running nc and tailing both webserver and FTL logs:

$ sudo tail -F /var/log/pihole/{webserver,FTL}.log
[..]
==> /var/log/pihole/webserver.log <==
[2026-02-01 22:40:10.578 CET 465] DEBUG: Accepted socket 42 (src/webserver/civetweb/civetweb.c:20617)
[2026-02-01 22:40:10.578 CET 465] DEBUG: queued socket 42 (src/webserver/civetweb/civetweb.c:20301)
[2026-02-01 22:40:10.579 CET 465] DEBUG: grabbed socket 42, going busy (src/webserver/civetweb/civetweb.c:20255)
[2026-02-01 22:40:10.579 CET 465] DEBUG: Incoming connection from 10.0.0.5 (src/webserver/civetweb/civetweb.c:20420)
[2026-02-01 22:40:10.579 CET 465] DEBUG: Start processing connection from 10.0.0.5 (src/webserver/civetweb/civetweb.c:19970)
[2026-02-01 22:40:10.579 CET 465] DEBUG: calling get_request (1 times for this connection) (src/webserver/civetweb/civetweb.c:19976)
[2026-02-01 22:40:10.582 CET 465] DEBUG: http: none, error: No data received (src/webserver/civetweb/civetweb.c:20060)
[2026-02-01 22:40:10.582 CET 465] DEBUG: Done processing connection from 10.0.0.5 (0.000000 sec) (src/webserver/civetweb/civetweb.c:20132)
[2026-02-01 22:40:10.583 CET 465] DEBUG: Connection closed (src/webserver/civetweb/civetweb.c:20529)
[2026-02-01 22:40:10.584 CET 465] DEBUG: going idle (src/webserver/civetweb/civetweb.c:20235)
22

Did a sudo pihole-FTL --config debug.webserver true. While viewing my the webserver log and I did a nc -nzvw5 192.168.1.199 80 from another machine. Said machine shows that the connection is successful, but that makes sense as adblocking and everything but the dashboard are still working. However, nothing shows up in webserver.log, in fact it is completely empty and was last modified at Feb 2nd at 03:30 along with several of the backup logs. Which matches my /etc/cron.d/pihole.

cron setup as follows:

Update Gravity 11th minute of 3rd hour every (7) Sunday.

Flush logs at 30th minute of 3rd hour every day

Grab remote and local set to 16th minute of 13th hour of every day followed by:

@reboot root PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker reboot

last update in pihole_debug.logis from 30th which matches last modified.

webserver.log.1 shows last updates were around when I rebooted. The post reboot nc -nzvw5 192.168.1.199 80 shows up from itself and the other machine as well as dashboard access auth request that redirects to /admin/login from when I logged in.

I’m not sure what is causing the dashboard itself to fail while the DNS sinkhole stays running in the background.

23

Do you really need to reboot the whole Pi to get access again to the webGUI or does restarting of pihole-FTL only also brings back the GUI?

sudo systemctl restart pihole-FTL.service

24

Lighttpd has not been used since V5. V6 has the web server embedded in FTL.

Please upload a fresh debug token, as you old one expired after 48 hours.

1 Like
26

I’ll try this next time.

27

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.