Admin Panel Timeout After Update

[Ltes]

Expected Behaviour:

Pihole has lived on a raspberry pi 4 for several years now at the local ip of 192.168.0.200. The admin panel is accessible via http://192.168.0.200/admin and has worked in the past.

Actual Behaviour:

After updating to 5.13 navigating to http://192.168.0.200/admin or http://192.168.0.200 times out. Tested on multiple machines, behavior persists through reboots and an execution of 'pihole -r'.

~ $ pihole -v
Pi-hole version is v5.13 (Latest: v5.13)
AdminLTE version is v5.16 (Latest: v5.16)
FTL version is v5.18.2 (Latest: v5.18.2)

DNS requests are being fulfilled and I can ssh into the box without any issues. I see the device as active in my router device table and the ip assignment is still valid.

Curling localhost/admin/ appears to return correctly:

~ $ curl -I http://localhost/admin/
HTTP/1.1 302 Found
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Set-Cookie: PHPSESSID=87bpo0dgmhviti79l5gevgd7a0; path=/; HttpOnly; SameSite=Strict
Location: login.php
Content-type: text/html; charset=UTF-8
X-Pi-hole: The Pi-hole Web interface is working!
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Security-Policy: default-src 'self' 'unsafe-inline';
X-Permitted-Cross-Domain-Policies: none
Referrer-Policy: same-origin
Date: Mon, 31 Oct 2022 17:32:00 GMT
Server: lighttpd/1.4.53

Lighttpd seems to be working:

systemctl status lighttpd.service
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-10-31 11:04:29 MDT; 33min ago
Main PID: 1446 (lighttpd)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/lighttpd.service
├─1446 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
├─1458 /usr/bin/php-cgi
├─1459 /usr/bin/php-cgi
├─1460 /usr/bin/php-cgi
├─1461 /usr/bin/php-cgi
└─1462 /usr/bin/php-cgi
Oct 31 11:04:28 pihole-main systemd[1]: Starting Lighttpd Daemon...
Oct 31 11:04:28 pihole-main lighttpd[1439]: 2022-10-31 11:04:28: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
Oct 31 11:04:29 pihole-main systemd[1]: Started Lighttpd Daemon.

A quick internet search shows that this config-key:alias.url error isn't likely causing any issues, but I don't know that for certain.

I don't appear to have any conflicts on port 80:

sudo lsof -i :80 -S
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
lighttpd 1446 www-data 4u IPv4 27777 0t0 TCP *:http (LISTEN)
lighttpd 1446 www-data 5u IPv6 27778 0t0 TCP *:http (LISTEN)

A repair of the installation using 'pihole -r' made no difference.

I am well and truly out of ideas. Anyone have any clever places to check? Thank you!!

Debug Token:

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

[deHakkelaar]

Could be browser cache not being up to date.
Have you tried clearing cache or test on another device and check with another browser?

[Ltes]

Thank you for the suggestion! Unfortunately, the issue has persisted through different browsers, a cleared cache, and on three different machines.

[jfb]

Something is cycling your lighttpd service:

-rw-r--r-- 1 www-data www-data 1.2K Oct 31 11:04 /var/log/lighttpd/error-pihole.log
   -----head of error-pihole.log------
   2022-10-30 00:00:08: (server.c.1759) logfiles cycled UID = 0 PID = 19927 
   2022-10-31 10:32:26: (server.c.2059) server stopped by UID = 0 PID = 1 
   2022-10-31 10:32:39: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-10-31 10:32:39: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 
   2022-10-31 10:36:27: (server.c.2059) server stopped by UID = 0 PID = 1 
   2022-10-31 10:36:27: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-10-31 10:36:27: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 
   2022-10-31 10:55:48: (server.c.2059) server stopped by UID = 0 PID = 1 
   2022-10-31 10:55:49: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-10-31 10:55:49: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 
   2022-10-31 11:00:44: (server.c.2059) server stopped by UID = 0 PID = 1 
   2022-10-31 11:00:54: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-10-31 11:00:54: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 
   2022-10-31 11:04:28: (server.c.2059) server stopped by UID = 0 PID = 1 
   2022-10-31 11:04:29: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-10-31 11:04:29: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 

Unrelated to this problem, but noted in your debug log: you have multiple regex similar to this, leading with https. These are not going to be effective since https is not going to be part of the domain name (it is part of the URL).

^https?://([A-Za-z0-9.-]*\.)?clicks\.beap\.bc\.yahoo\.com/

[Ltes]

Interesting - thank you! Not sure what's cycling it, but I'll play around with it and/or blow the config away and start again.

And thank you for the note on the regex filters! I will update those accordingly, I didn't know! You've been very helpful!