Dashboard not updating

v3-3

#1

I am currently trying to install PiHole on my synology using docker. After a couple rounds of the various instructions I have settled on using this docker run command
sudo docker run -d --name=pihole -v “/volume1/docker/pihole/:/etc/pihole/”
-v “/volume1/docker/dnsmasq.d/:/etc/dnsmasq.d/”
–net=host
-e ServerIP=192.168.1.99
–restart=always
-e DNS1=8.8.4.4
-e DNS2=8.8.8.8
-e IPv6=False
-e VIRTUAL_SERVER=192.168.1.99
-e WEB_PORT=37337
-e DNSMASQ_LISTENING=all
-e WEBPASSWORD=randomLetters!
diginc/pi-hole:latest

I have also set up Webstation to serve the pihole reject image.

Everything appears to work well from a functionality sense, it is serving dns addresses and blocking appropriate ones, but the web UI looks like the following.

Any ideas on how I can get the web UI to function correctly?


#2

Have you tried this:


#3

I’ve tried shift + f5 multiple times, and just for good measure I just emptied chrome’s cache. Neither resulted in any results. When I examine the json coming back from the server it is all 0s except the # of domains blocked.


#4

I also have this problem after updating pi-hole via ssh. I’m not using Synology. I have generated a debug log
"Your debug token is:" o39j3sxtgt

DNS is working, just the dashboard not showing any more queries, query log is blank. I looked around at other posts which suggested that the logs might be “full”. I deleted some old archived logs but I believe var is in the main SD partition so I don’t see it as a likely problem. I could go back to an old pi-hole image from last July but I’ll stick with this update for a little while in the hope of resolution.

Update:
I decided to reinstall from scratch using the latest Debian stretch lite. All working fine, so I don’t need anyone to look at the debug log.


#5

I have exactly the same problem since the last release. However, I’m running it on a raspberry pi 3.
No statistics are shown on the dashboard and no long-term logs are available - “Query log” throws a popup message indicating “An unknown error ocurred while loading the data”. Everything was working before the update.

“pihole -d” shows nothing special.
Interesting is that I’m somehow running pihole core 3.2.1 and I cannot update to 3.3 (“pihole -up” shows everything up to date) while FTL & Adminpage have updated themself to v3.3 and v3.0.
Edit: “cd /etc/.pihole && git fetch --tags” fixed the version mismatch like described here.

I’m running dnsmasq v2.76 so that should not be the problem why it does not update the core to v3.3.

I’ve read it a couple of times here in the last hours that more people have the same problem like I have.
Do you want me to send a debug log aswell?


#6

pihole -d has some more interesting results for me.

TERM environment variable not set.
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2018-02-28:17:30:12 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf…

*** [ DIAGNOSING ]: Core version
[i] Core: v3.3 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3-0-g1e87850

*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa295

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0

*** [ DIAGNOSING ]: dnsmasq version
[i] 2.76

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45

*** [ DIAGNOSING ]: php version
[i] 7.0.27

*** [ DIAGNOSING ]: Operating system
[✓] Debian GNU/Linux 9 (stretch)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
[i] x86_64

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.

[✗] No IPv6 address(es) found on the eth0 interface.

[i] Default IPv4 gateway: 192.168.1.1

*** [ DIAGNOSING ]: Ports in use
[53] is in use by dnsmasq
[] is in use by
[4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ad.doubleclick.net.71154.9418.302br.net is 192.168.1.99 via localhost (127.0.0.1)
[✓] ad.doubleclick.net.71154.9418.302br.net is 192.168.1.99 via Pi-hole (192.168.1.99)
[✓] doubleclick.com is 172.217.0.174 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is
[✗] lighttpd daemon is
[✗] pihole-FTL daemon is

*** [ DIAGNOSING ]: Setup variables
PIHOLE_DNS_1=8.8.4.4
PIHOLE_DNS_2=8.8.8.8
IPV4_ADDRESS=192.168.1.99
IPV6_ADDRESS=
PIHOLE_INTERFACE=eth0

*** [ DIAGNOSING ]: Dashboard and block page
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 28 Feb 2018 17:30:21 GMT
Content-Type: text/html
Content-Length: 1474
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding
Last-Modified: Tue, 27 Feb 2018 13:49:57 GMT
ETag: "5c2-56631e6eb0bff"
Accept-Ranges: bytes
Vary: Accept-Encoding

[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 404 Not Found
Server: nginx
Date: Wed, 28 Feb 2018 17:30:21 GMT
Content-Type: image/svg+xml
Content-Length: 396
Connection: keep-alive
Keep-Alive: timeout=20
Last-Modified: Mon, 13 Nov 2017 20:46:10 GMT
ETag: "18c-55de35c3cc880;5663204e16f26"
Accept-Ranges: bytes

*** [ DIAGNOSING ]: Gravity list
-rwxr-xr-x 1 root root 4374448 Feb 28 12:03 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.1.99 0.0.0.0
192.168.1.99 0.r.msn.com
192.168.1.99 0.start.bz
192.168.1.99 000.gaysexe.free.fr

-----tail of gravity.list------
192.168.1.99 zzsyw.com
192.168.1.99 zztxdown.com
192.168.1.99 zzz.clickbank.net
192.168.1.99 ɢoogle.com

*** [ DIAGNOSING ]: contents of /etc/pihole

-rwxr-xr-x 1 root root 633 Feb 22 19:21 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt

-rwxr-xr-x 1 root root 45 Feb 28 12:03 /etc/pihole/local.list
192.168.1.99 doodleserv
192.168.1.99 pi.hole

-rwxr-xr-x 1 root root 117 Feb 26 16:53 /etc/pihole/whitelist.txt
raw.githubusercontent.com
mirror1.malwaredomains.com
sysctl.org
zeustracker.abuse.ch
s3.amazonaws.com
hosts-file.net

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rwxr-xr-x 1 root root 1516 Feb 28 12:03 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=8.8.4.4
server=8.8.8.8
except-interface=nonexisting

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r–r-- 1 root root 2967 Feb 28 12:03 /etc/lighttpd/lighttpd.conf
server.modules = (
“mod_access”,
“mod_accesslog”,
“mod_auth”,
“mod_expire”,
“mod_compress”,
“mod_redirect”,
“mod_setenv”,
“mod_rewrite”
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( “/var/cache/lighttpd/uploads” )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 37337
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( “index.php”, “index.html”, “index.lighttpd.html” )
url.access-deny = ( “~”, “.inc”, “.md”, “.yml”, “.ini” )
static-file.exclude-extensions = ( “.php”, “.pl”, “.fcgi” )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( “application/javascript”, “text/css”, “text/html”, “text/plain” )
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell “find /etc/lighttpd/conf-enabled -name ‘*.conf’ -a ! -name ‘letsencrypt.conf’ -printf ‘include “%p”
’ 2>/dev/null”
$HTTP[“url”] =~ “^/admin/” {

   setenv.add-response-header = (
       "X-Pi-hole" => "The Pi-hole Web interface is working!",
       "X-Frame-Options" => "DENY"
   )
   $HTTP["url"] =~ ".ttf$" {

       setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
   }

}
$HTTP[“url”] =~ “^/admin/.(.*)” {
url.access-deny = ("")
}
include_shell “cat external.conf 2>/dev/null”

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r–r-- 1 root root 1496 Feb 23 06:18 /etc/cron.d/pihole
50 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
58 17 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r–r-- 1 www-data www-data 506 Feb 28 12:03 /var/log/lighttpd/error.log
2018-02-27 13:31:14: (log.c.217) server started
2018-02-27 13:36:40: (server.c.1534) logfiles cycled UID = 0 PID = 1156
2018-02-27 13:36:41: (server.c.1828) server stopped by UID = 0 PID = 1156
2018-02-27 13:36:53: (log.c.217) server started
2018-02-28 12:02:46: (server.c.1534) logfiles cycled UID = 0 PID = 21901
2018-02-28 12:02:46: (mod_fastcgi.c.3580) child signaled: 1
2018-02-28 12:02:47: (server.c.1828) server stopped by UID = 0 PID = 21901
2018-02-28 12:03:42: (log.c.217) server started

*** [ DIAGNOSING ]: contents of /var/log

-rw-r–r-- 1 root root 12377 Feb 28 12:03 /var/log/pihole-FTL.log
[2018-02-27 13:31:14.286]
[2018-02-27 13:31:14.286] FTL branch: v3.0
[2018-02-27 13:31:14.286] FTL version: v3.0
[2018-02-27 13:31:14.286] FTL commit: a1b2fa03f8f3e3713b57a26a4e9a062fec0573d7
[2018-02-27 13:31:14.286] FTL date: 2018-02-14 12:45:47 -0800
[2018-02-27 13:31:14.286] FTL user: root
[2018-02-27 13:31:14.286] Warning: Starting pihole-FTL directly is not recommended.
[2018-02-27 13:31:14.286] Instead, use system commands for starting pihole-FTL as service (systemctl / service).
[2018-02-27 13:31:14.286] Notice: Found no readable FTL config file
[2018-02-27 13:31:14.286] Using default settings
[2018-02-27 13:31:14.286] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2018-02-27 13:31:14.287] SOCKET_LISTENING: only local
[2018-02-27 13:31:14.287] QUERY_DISPLAY: Show queries
[2018-02-27 13:31:14.287] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2018-02-27 13:31:14.287] MAXDBDAYS: max age for stored queries is 365 days
[2018-02-27 13:31:14.287] RESOLVE_IPV6: Resolve IPv6 addresses
[2018-02-27 13:31:14.287] RESOLVE_IPV4: Resolve IPv4 addresses
[2018-02-27 13:31:14.287] DBINTERVAL: saving to DB file every minute
[2018-02-27 13:31:14.287] DBFILE: Using /etc/pihole/pihole-FTL.db
[2018-02-27 13:31:14.287] MAXLOGAGE: Importing up to 24.0 hours of log data
[2018-02-27 13:31:14.287] Finished config file parsing
[2018-02-27 13:31:14.287] PID of FTL process: 569
[2018-02-27 13:31:14.331] Gravity list entries: 123424
[2018-02-27 13:31:14.332] No blacklist present
[2018-02-27 13:31:14.332] No wildcard blocking list present

*** [ DIAGNOSING ]: Pi-hole log
-rw-r–r-- 1 dnsmasq root 4184513 Feb 28 17:30 /var/log/pihole.log
-----head of pihole.log------
Feb 27 13:31:04 dnsmasq[216]: started, version 2.76 cachesize 10000
Feb 27 13:31:04 dnsmasq[216]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
Feb 27 13:31:04 dnsmasq[216]: using nameserver 8.8.8.8#53
Feb 27 13:31:04 dnsmasq[216]: using nameserver 8.8.4.4#53
Feb 27 13:31:04 dnsmasq[216]: read /etc/hosts - 4 addresses
Feb 27 13:31:04 dnsmasq[216]: read /etc/pihole/local.list - 2 addresses
Feb 27 13:31:04 dnsmasq[216]: failed to load names from /etc/pihole/black.list: No such file or directory
Feb 27 13:31:05 dnsmasq[216]: bad name at /etc/pihole/gravity.list line 92047
Feb 27 13:31:05 dnsmasq[216]: bad name at /etc/pihole/gravity.list line 123422
Feb 27 13:31:05 dnsmasq[216]: read /etc/pihole/gravity.list - 123422 addresses
Feb 27 13:31:14 dnsmasq[216]: read /etc/hosts - 4 addresses
Feb 27 13:31:14 dnsmasq[216]: read /etc/pihole/local.list - 2 addresses
Feb 27 13:31:14 dnsmasq[216]: failed to load names from /etc/pihole/black.list: No such file or directory
Feb 27 13:31:14 dnsmasq[557]: started, version 2.76 cachesize 10000
Feb 27 13:31:14 dnsmasq[557]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
Feb 27 13:31:14 dnsmasq[557]: using nameserver 8.8.8.8#53
Feb 27 13:31:14 dnsmasq[557]: using nameserver 8.8.4.4#53
Feb 27 13:31:14 dnsmasq[557]: read /etc/hosts - 4 addresses
Feb 27 13:31:14 dnsmasq[557]: read /etc/pihole/local.list - 2 addresses
Feb 27 13:31:14 dnsmasq[557]: failed to load names from /etc/pihole/black.list: No such file or directory


#7

Check


#8

That does seem to describe the problem. Looks like I’ll just have to wait for the fix.