Expected Behaviour:
Dashboard to display.
Actual Behaviour:
Seeing a blank dashboard after upgrading to v5.18.4, other menu items are working. Running on Raspberry Pi 4, bookworm 64-bit. Diagnosis reports "No issues found."
Debug Token:
https://tricorder.pi-hole.net/MQserXLA/
No experience with Bookworm, but I have 2 RPi 4B running Ubuntu Server and both work fine after the update. I know the update was simply to correct an issue with Fedora, so not necessary for my setup, but wanted the “update available” message to go away. Could have ignored it if it did not pulse…
Any chance you made other changes, or perhaps changed Pi-hole config files that indicate they get overwritten on update?
Open the browser console (devtools).
If you see any error messages, post them here.
Also, do you see the same issue using a different browser? or accessing the web interface from a different device?
Only changes to environment were 1) OS updates via apt, 2) Pi-hole update via "sudo pi-hole -up".
I have opened web interface on 1) two seperate machines using Windows 10 and Chrome, 2) same two machines using Edge, 3) Pi 5 system running bookworm 64-bit desktop and Firefox. Same result on all, Dashboard is blank.
On Chrome, opened developer tools and did not see and error messages. Please note, newbie using developer tools.
Please see attached screen shot of Dashboard.
I haven’t used chrome in a while, but if you can see the debug console, and see no errors, that is something.
Hopefully, others have additional ideas on what to check.
Not sure if this is related, its an old post from reddit but you may want to look at it.
https://www.reddit.com/r/pihole/comments/giao0t/comment/fqdpodw/
Are you running NGINX by chance?
I just noticed one thing in your Debug Log.
The gravity database permissions are wrong:
*** [ DIAGNOSING ]: Gravity Database
-rw--w---- 1 pihole pihole 6.8M Dec 30 16:50 /etc/pihole/gravity.db
It should be -rw-rw-r-- (644).
Please execute these commands to fix the permissions and update gravity:
sudo chmod 644 /etc/pihole/gravity.db
pihole -g
I am not using NGINX.
Dashboard still not working after executing the below commands.
$ sudo chmod 664 /etc/pihole/gravity.db
$ sudo ls -l /etc/pihole/gravity.db
-rw-rw-r-- 1 pihole pihole 7032832 Dec 30 16:50 /etc/pihole/gravity.db
$ pihole -g
[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range
[✓] Preparing new gravity database
[✓] Creating new gravity databases
[i] Using libz compression
[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[✓] Status: Retrieval successful
[✓] Parsed 117489 exact domains and 0 ABP-style domains (ignored 1 non-domain entries)
Sample of non-domain entries:
- "0.0.0.0"
[i] List stayed unchanged
[✓] Building tree
[✓] Swapping databases
[✓] The old database remains available
[i] Number of gravity domains: 117489 (117489 unique domains)
[i] Number of exact blacklisted domains: 0
[i] Number of regex blacklist filters: 0
[i] Number of exact whitelisted domains: 0
[i] Number of regex whitelist filters: 0
[✓] Flushing DNS cache
[✓] Cleaning up stray matter
[✓] FTL is listening on port 53
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✓] UDP (IPv6)
[✓] TCP (IPv6)
[✓] Pi-hole blocking is enabled
You mentioned updating the OS and the pihole. Might be good to understand what packages were updated via apt. What does sudo cat /var/log/dpkg.log* | grep "^2024-12-29.*" You will need to adjust the date to the date you did the update.
$ sudo cat /var/log/dpkg.log* | grep "^2025-01-01."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-31."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-30."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-29."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-28."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-27."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-26."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-25."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-24."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-23."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-22."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-21."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-20."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-19."
$ sudo cat /var/log/dpkg.log | grep "^2024-12-18.*"
2024-12-18 19:06:36 startup archives unpack
2024-12-18 19:06:36 upgrade rpi-eeprom:all 26.6-1 26.7-1
2024-12-18 19:06:36 status half-configured rpi-eeprom:all 26.6-1
2024-12-18 19:06:36 status unpacked rpi-eeprom:all 26.6-1
2024-12-18 19:06:36 status half-installed rpi-eeprom:all 26.6-1
2024-12-18 19:06:39 status triggers-pending man-db:arm64 2.11.2-2
2024-12-18 19:06:39 status unpacked rpi-eeprom:all 26.7-1
2024-12-18 19:06:40 startup packages configure
2024-12-18 19:06:40 configure rpi-eeprom:all 26.7-1
2024-12-18 19:06:40 status unpacked rpi-eeprom:all 26.7-1
2024-12-18 19:06:40 status half-configured rpi-eeprom:all 26.7-1
2024-12-18 19:06:42 status installed rpi-eeprom:all 26.7-1
2024-12-18 19:06:42 trigproc man-db:arm64 2.11.2-2
2024-12-18 19:06:42 status half-configured man-db:arm64 2.11.2-2
2024-12-18 19:06:44 status installed man-db:arm64 2.11.2-2
$
Dashboard was working prior to 5.18.4 upgrade.
This is strange because 5.18.4 was just a hot fix for a Fedora 41 issue.
Nothing else was changed.
Just in case we missed something, please open the Chrome console using this key combination: Ctrl + Shift + J
Here are the steps used:
See attached screen shot, no issues detected.
Are there error messages in the "Console" tab?
If there are no errors, please generate a new debug log. The previous one expired.
There are no errors in the console tab.
Thanks for checking.
This is definitely not happening in the browser. The database file permissions are wrong again:
*** [ DIAGNOSING ]: Gravity Database
-rw--w---- 1 pihole pihole 6.8M Jan 2 07:12 /etc/pihole/gravity.db
I have no idea what is changing the permissions.
What happens if you run pihole -g?
Does it fix the permissions or does it fail (in this case, post the error messages)?
$ ls -l /etc/pihole/gravity.db
-rw--w---- 1 pihole pihole 7032832 Jan 2 07:12 /etc/pihole/gravity.db
$ pihole -g
[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range
[✓] Preparing new gravity database
[✓] Creating new gravity databases
[i] Using libz compression
[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[✓] Status: Retrieval successful
[✓] Parsed 117489 exact domains and 0 ABP-style domains (ignored 1 non-domain entries)
Sample of non-domain entries:
- "0.0.0.0"
[i] List stayed unchanged
[✓] Building tree
[✓] Swapping databases
[✓] The old database remains available
[i] Number of gravity domains: 117489 (117489 unique domains)
[i] Number of exact blacklisted domains: 0
[i] Number of regex blacklist filters: 0
[i] Number of exact whitelisted domains: 0
[i] Number of regex whitelist filters: 0
[✓] Flushing DNS cache
[✓] Cleaning up stray matter
[✓] FTL is listening on port 53
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✓] UDP (IPv6)
[✓] TCP (IPv6)
[✓] Pi-hole blocking is enabled
$ ls -l /etc/pihole/gravity.db
-rw--w---- 1 pihole pihole 7032832 Jan 2 20:13 /etc/pihole/gravity.db
$
The dashboard is working now, I have no idea what change fixed the issue.
Thank you all for helping.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.