Dashboard not working (No Data)

Hello everybody,

I've got a problem can anyone please help me?
I'm not quite sure if my pi-hole is working correct because I still see ads (maybe a fewer but they are still there). So I wanted to check if everything is working fine: I opned the dashboard and the only information I see are just the "infinity loading circles".

Here is my debug output:

    > 
    > 
    > *** [ INITIALIZING ]
    > [i] 2018-02-24:21:26:36 debug log has been initialized.
    > 
    > *** [ INITIALIZING ] Sourcing setup variables
    > [i] Sourcing /etc/pihole/setupVars.conf...
    > 
    > *** [ DIAGNOSING ]: Core version
    > [i] Core: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
    > [i] Branch: master
    > [i] Commit: v3.3-0-g1e87850
    > 
    > *** [ DIAGNOSING ]: Web version
    > [i] Web: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
    > [i] Branch: master
    > [i] Commit: v3.3-0-ge48aa29
    > 
    > *** [ 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
    > [βœ“] Raspbian GNU/Linux 9 (stretch)
    > 
    > *** [ DIAGNOSING ]: SELinux
    > [i] SELinux not detected
    > 
    > *** [ DIAGNOSING ]: Processor
    > /opt/pihole/piholeDebug.sh: line 474: $'[\E[32mβœ“\E[0m] \E[32marmv7l\E[0m': comma                                                                                                             nd not found
    > 
    > *** [ DIAGNOSING ]: Networking
    > [βœ“] IPv4 address(es) bound to the eth0 interface:
    >    192.168.2.104/24 matches the IP found in /etc/pihole/setupVars.conf
    > 
    > [βœ“] IPv6 address(es) bound to the eth0 interface:
    >    2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 matches the IP found in /etc/pihole/setu                                                                                                             pVars.conf
    >    fe80::50d0:ac58:4e3d:110d does not match the IP found in /etc/pihole/setupVar                                                                                                             s.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
    > 
    >    ^ Please note that you may have more than one IP address listed.
    >    As long as one of them is green, and it matches what is in /etc/pihole/setupV                                                                                                             ars.conf, there is no need for concern.
    > 
    >    The link to the FAQ is for an issue that sometimes occurs when the IPv6 addre                                                                                                             ss changes, which is why we check for it.
    > 
    > [i] Default IPv4 gateway: 192.168.2.1
    >    * Pinging 192.168.2.1...
    > [βœ“] Gateway responded.
    > [i] Default IPv6 gateway: fe80::1
    >    * Pinging fe80::1...
    > [βœ“] Gateway responded.
    > 
    > *** [ DIAGNOSING ]: Ports in use
    > [] is in use by
    > [22] is in use by sshd
    > [53] is in use by dnsmasq
    > [80] is in use by lighttpd
    > [4711] is in use by pihole-FTL
    > 
    > *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a k                                                                                                             nown ad-serving domain
    > [βœ“] net.35369.9265.302br.net is 192.168.2.104 via localhost (127.0.0.1)
    > [βœ“] net.35369.9265.302br.net is 192.168.2.104 via Pi-hole (192.168.2.104)
    > [βœ“] doubleclick.com is 172.217.22.206 via a remote, public DNS server (8.8.8.8)
    > 
    > *** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a k                                                                                                             nown ad-serving domain
    > [βœ“] protection.lapolice.net is 2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 via localhos                                                                                                             t (::1)
    > [βœ“] protection.lapolice.net is 2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 via Pi-hole                                                                                                              (2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0)
    > [βœ“] doubleclick.com is 2a00:1450:4016:801::200e via a remote, public DNS server                                                                                                              (2001:4860:4860::8888)
    > 
    > *** [ DIAGNOSING ]: Pi-hole processes
    > [βœ“] dnsmasq daemon is active
    > [βœ“] lighttpd daemon is active
    > [βœ“] pihole-FTL daemon is active
    > 
    > *** [ DIAGNOSING ]: Setup variables
    >     PIHOLE_INTERFACE=eth0
    >     IPV4_ADDRESS=192.168.2.104/24
    >     IPV6_ADDRESS=2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0
    >     PIHOLE_DNS_1=208.67.222.222
    >     PIHOLE_DNS_2=208.67.220.220
    >     QUERY_LOGGING=false
    >     INSTALL_WEB=true
    >     LIGHTTPD_ENABLED=1
    > 
    > *** [ DIAGNOSING ]: Dashboard and block page
    > [βœ“] X-Pi-hole: A black hole for Internet advertisements.
    > [βœ“] X-Pi-hole: The Pi-hole Web interface is working!
    > 
    > *** [ DIAGNOSING ]: Gravity list
    > -rw-r--r-- 1 root root 11692399 Feb 24 21:02 /etc/pihole/gravity.list
    >    -----head of gravity.list------
    >    192.168.2.104 0.0.0.0
    >    2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 0.0.0.0
    >    192.168.2.104 0000mps.webpreview.dsl.net
    >    2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 0000mps.webpreview.dsl.net
    > 
    >    -----tail of gravity.list------
    >    192.168.2.104 zzz.clickbank.net
    >    2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 zzz.clickbank.net
    >    192.168.2.104 zz.zeroredirect1.com
    >    2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 zz.zeroredirect1.com
    > 
    > *** [ DIAGNOSING ]: contents of /etc/pihole
    > 
    > -rw-r--r-- 1 root root 633 Feb 24 19:58 /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
    > 
    > -rw-r--r-- 1 root root 142 Feb 24 21:02 /etc/pihole/local.list
    >    192.168.2.104 raspberrypi
    >    2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 raspberrypi
    >    192.168.2.104 pi.hole
    >    2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0 pi.hole
    > 
    > -rw-r--r-- 1 root root 234 Feb 24 20:51 /etc/pihole/logrotate
    >    /var/log/pihole.log {
    >         su root root
    >         daily
    >         copytruncate
    >         rotate 5
    >         compress
    >         delaycompress
    >         notifempty
    >         nomail
    >    }
    >    /var/log/pihole-FTL.log {
    >         su root root
    >         weekly
    >         copytruncate
    >         rotate 3
    >         compress
    >         delaycompress
    >         notifempty
    >         nomail
    >    }
    > 
    > -rw-r--r-- 1 root root 117 Feb 24 19:58 /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
    > 
    > -rw-r--r-- 1 root root 1523 Feb 24 20:51 /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-facility=/var/log/pihole.log
    >    local-ttl=2
    >    log-async
    >    server=208.67.222.222
    >    server=208.67.220.220
    >    interface=eth0
    > 
    > *** [ DIAGNOSING ]: contents of /etc/lighttpd
    > 
    > -rw-r--r-- 1 root root 3027 Feb 24 20:51 /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                 = 80
    >    accesslog.filename          = "/var/log/lighttpd/access.log"
    >    accesslog.format            = "%{%s}t|%V|%r|%s|%b"
    >    index-file.names            = ( "index.php", "index.html", "index.lighttpd.ht                                                                                                             ml" )
    >    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/h                                                                                                             tml", "text/plain" )
    >    include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
    >    include_shell "/usr/share/lighttpd/create-mime.assign.pl"
    >    include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'let                                                                                                             sencrypt.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 1495 Feb 24 20:51 /etc/cron.d/pihole
    >    58 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 loc                                                                                                             al
    >    3 19  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remot                                                                                                             e
    >    @reboot root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote rebo                                                                                                             ot
    > 
    > *** [ DIAGNOSING ]: contents of /var/log/lighttpd
    > 
    > -rw-r--r-- 1 www-data www-data 1017 Feb 24 21:24 /var/log/lighttpd/error.log
    >    2018-02-24 19:46:19: (log.c.217) server started
    >    2018-02-24 19:58:33: (log.c.217) server started
    >    2018-02-24 19:58:33: (server.c.1295) WARNING: unknown config-key: alias.url (                                                                                                             ignored)
    >    2018-02-24 20:25:38: (server.c.1828) server stopped by UID = 0 PID = 1
    >    2018-02-24 20:25:45: (log.c.217) server started
    >    2018-02-24 20:25:45: (server.c.1295) WARNING: unknown config-key: alias.url (                                                                                                             ignored)
    >    2018-02-24 20:37:59: (server.c.1828) server stopped by UID = 0 PID = 1
    >    2018-02-24 20:38:11: (log.c.217) server started
    >    2018-02-24 20:38:11: (server.c.1295) WARNING: unknown config-key: alias.url (                                                                                                             ignored)
    >    2018-02-24 20:51:40: (server.c.1828) server stopped by UID = 0 PID = 1
    >    2018-02-24 20:51:41: (log.c.217) server started
    >    2018-02-24 20:51:41: (server.c.1295) WARNING: unknown config-key: alias.url (                                                                                                             ignored)
    >    2018-02-24 21:24:44: (server.c.1828) server stopped by UID = 0 PID = 1
    >    2018-02-24 21:24:51: (log.c.217) server started
    >    2018-02-24 21:24:51: (server.c.1295) WARNING: unknown config-key: alias.url (                                                                                                             ignored)
    > 
    > *** [ DIAGNOSING ]: contents of /var/log
    > 
    > -rw-r--r-- 1 pihole pihole 41347 Feb 24 21:25 /var/log/pihole-FTL.log
    >    [2018-02-24 20:30:18.148] New forward server: 208.67.220.220 resolver2.opendn                                                                                                             s.com (0/4)
    >    [2018-02-24 20:30:18.148] Notice: Increasing overTime struct size from 0 to 1                                                                                                             00 (464.53 KB)
    >    [2018-02-24 20:30:18.219] New forward server: 208.67.222.222 resolver1.opendn                                                                                                             s.com (1/4)
    >    [2018-02-24 20:30:18.293] New client: 192.168.2.102 (1/10)
    >    [2018-02-24 20:30:18.293] Imported 163 queries from the long-term database
    >    [2018-02-24 20:30:18.294] Reading from /var/log/pihole.log (rw-r--r--)
    >    [2018-02-24 20:37:59.486] FATAL: FTL received SIGTERM from PID/UID 1/0, exiti                                                                                                             ng gracefully
    >    [2018-02-24 20:38:10.904]
    >    [2018-02-24 20:38:10.906] FTL branch: v3.0
    >    [2018-02-24 20:38:10.907] FTL version: v3.0
    >    [2018-02-24 20:38:10.907] FTL commit: a1b2fa03f8f3e3713b57a26a4e9a062fec0573d                                                                                                             7
    >    [2018-02-24 20:38:10.907] FTL date: 2018-02-14 12:45:47 -0800
    >    [2018-02-24 20:38:10.907] FTL user: pihole
    >    [2018-02-24 20:38:10.907] Notice: Found no readable FTL config file
    >    [2018-02-24 20:38:10.907]         Using default settings
    >    [2018-02-24 20:38:10.907] Starting config file parsing (/etc/pihole/pihole-FT                                                                                                             L.conf)
    >    [2018-02-24 20:38:10.907]    SOCKET_LISTENING: only local
    >    [2018-02-24 20:38:10.907]    QUERY_DISPLAY: Show queries
    >    [2018-02-24 20:38:10.907]    AAAA_QUERY_ANALYSIS: Show AAAA queries
    >    [2018-02-24 20:38:10.908]    MAXDBDAYS: max age for stored queries is 365 day                                                                                                             s
    >    [2018-02-24 20:38:10.913]    RESOLVE_IPV6: Resolve IPv6 addresses
    >    [2018-02-24 20:38:10.913]    RESOLVE_IPV4: Resolve IPv4 addresses
    >    [2018-02-24 20:38:10.913]    DBINTERVAL: saving to DB file every minute
    >    [2018-02-24 20:38:10.913]    DBFILE: Using /etc/pihole/pihole-FTL.db
    >    [2018-02-24 20:38:10.913]    MAXLOGAGE: Importing up to 24.0 hours of log dat                                                                                                             a
    > 
    > *** [ DIAGNOSING ]: Pi-hole log
    > -rw-r--r-- 1 dnsmasq root 4494 Feb 24 21:25 /var/log/pihole.log
    >    -----head of pihole.log------
    >    Feb 24 20:30:18 dnsmasq[1537]: read /etc/pihole/gravity.list - 243958 address                                                                                                             es
    >    Feb 24 20:38:00 dnsmasq[1537]: exiting on receipt of SIGTERM
    >    Feb 24 20:38:10 dnsmasq[523]: started, version 2.76 cachesize 10000
    >    Feb 24 20:38:10 dnsmasq[523]: compile time options: IPv6 GNU-getopt DBus i18n                                                                                                              IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
    >    Feb 24 20:38:10 dnsmasq[523]: warning: interface eth0 does not currently exis                                                                                                             t
    >    Feb 24 20:38:10 dnsmasq[523]: warning: ignoring resolv-file flag because no-r                                                                                                             esolv is set
    >    Feb 24 20:38:10 dnsmasq[523]: using nameserver 208.67.220.220#53
    >    Feb 24 20:38:10 dnsmasq[523]: using nameserver 208.67.222.222#53
    >    Feb 24 20:38:10 dnsmasq[523]: read /etc/hosts - 5 addresses
    >    Feb 24 20:38:10 dnsmasq[523]: read /etc/pihole/local.list - 4 addresses
    >    Feb 24 20:38:10 dnsmasq[523]: failed to load names from /etc/pihole/black.lis                                                                                                             t: No such file or directory
    >    Feb 24 20:38:19 dnsmasq[523]: read /etc/pihole/gravity.list - 243958 addresse                                                                                                             s
    >    Feb 24 20:40:07 dnsmasq[523]: read /etc/hosts - 5 addresses
    >    Feb 24 20:40:07 dnsmasq[523]: read /etc/pihole/local.list - 4 addresses
    >    Feb 24 20:40:07 dnsmasq[523]: failed to load names from /etc/pihole/black.lis                                                                                                             t: No such file or directory
    >    Feb 24 20:40:15 dnsmasq[523]: read /etc/pihole/gravity.list - 243958 addresse                                                                                                             s
    >    Feb 24 20:40:48 dnsmasq[523]: exiting on receipt of SIGTERM
    >    Feb 24 20:40:48 dnsmasq[2038]: started, version 2.76 cachesize 10000
    >    Feb 24 20:40:48 dnsmasq[2038]: compile time options: IPv6 GNU-getopt DBus i18                                                                                                             n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
    >    Feb 24 20:40:48 dnsmasq[2038]: warning: ignoring resolv-file flag because no-                                                                                                             resolv is set

Can anyone help me? :slight_smile:

We've seen this with the Chrome browser, are you using this browser, and does the same thing happen with other browsers?

Hi DanSchaper,

thank you for your answer. I've got the same problem with IE, Firefox, Chrome and Safari. I even tried Windows, Linux and iOS. On every device and browser the same problem.

Not sure with my old version of Pi-hole but you seem to be missing the 'log-queries' directive in the dnsmasq config file '/etc/dnsmasq.d/01-pihole.conf' ?????
For diagnosing, you could add a line to that config file with the 'log-queries' directive + run 'sudo service dnsmasq restart' to apply.
Could delete the line again if not solving the issue.

Thank you for the hit. Can you tell my where the log-queries are placed?
I could not find anything about this.:roll_eyes:

With below one you can edit the config file:

sudo nano /etc/dnsmasq.d/01-pihole.conf

Add an extra line at the end of the file with "log-queries".
Save the file by pressing CTRL-x.
And restart the dnsmasq daemon to apply:

sudo service dnsmasq restart

EDIT: Ps. during Pi-hole setup, your asked if you want Pi-hole to log DNS queries, do you remember what you entered ?

EDIT2: Never mind, from the debug log, it seems you entered NO:

Logging is required for any data to be displayed on the dashboard ... I believe ???
If adding that line works, better make it persistent by running below one:

pihole -r

And asnwer yes when asked for loggings.

Edditing the config file changed nothing.

Now I reconfigurated the pi-hole. I entered everything as recomended (queries enabled) but the problem still arises.
Here are the outputmessages:

> `  [i] Reconfigure option selected
>   [βœ“] Disk space check
> 
>   [βœ“] Update local cache of available packages
> 
>   [βœ“] Checking apt-get for upgraded packages... up to date!
> 
>   [i] Installer Dependency checks...
>   [βœ“] Checking for apt-utils
>   [βœ“] Checking for dialog
>   [βœ“] Checking for debconf
>   [βœ“] Checking for dhcpcd5
>   [βœ“] Checking for git
>   [βœ“] Checking for iproute2
>   [βœ“] Checking for whiptail
> 
> 
>   [βœ“] Stopping dnsmasq service...
> 
>   [βœ“] Stopping lighttpd service...
>   [i] Using interface: eth0
>   [i] Using Google DNS servers
>   [i] Static IP already configured
>   [i] Found IPv6 GUA address, using it for blocking IPv6 ads
>   [i] IPv4 address: 192.168.2.104/24
>   [i] IPv6 address: 2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0
>   [i] Web Interface On
>   [i] Logging On.
>   [i] Performing reconfiguration, skipping download of local repos
>   [βœ“] Resetting repository within /etc/.pihole...
>   [βœ“] Resetting repository within /var/www/html/admin...
>   [i] Main Dependency checks...
>   [βœ“] Checking for bc
>   [βœ“] Checking for cron
>   [βœ“] Checking for curl
>   [βœ“] Checking for dnsmasq
>   [βœ“] Checking for dnsutils
>   [βœ“] Checking for iputils-ping
>   [βœ“] Checking for lsof
>   [βœ“] Checking for netcat
>   [βœ“] Checking for sudo
>   [βœ“] Checking for unzip
>   [βœ“] Checking for wget
>   [βœ“] Checking for idn2
>   [βœ“] Checking for lighttpd
>   [βœ“] Checking for php-common
>   [βœ“] Checking for php-cgi
>   [βœ“] Checking for php-sqlite3
> 
> 
>   [βœ“] Enabling lighttpd service to start on reboot
>   [βœ“] Installing scripts from /etc/.pihole
> 
>   [i] Installing configs from /etc/.pihole...
>   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
>   [βœ“] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
> 
>   [i] Creating log and changing owner to dnsmasq... log already exists!
> 
>   [i] Installing blocking page...
>   [βœ“] Creating directory for blocking page, and copying files
>   [βœ—] Backing up index.lighttpd.html
>       No default index.lighttpd.html file found... not backing up
> 
>   [βœ“] Installing sudoer file
> 
>   [βœ“] Installing latest Cron script
> 
>   [βœ“] Installing latest logrotate script
> 
>   [i] FTL Checks...
>   [βœ“] Detected ARM-hf architecture (armv7+)
>   [i] Checking for existing FTL binary...
>   [i] Latest FTL Binary already installed (v3.0). Confirming Checksum...
>   [i] Checksum correct. No need to download!
> 
>   [i] Skipping firewall configuration
>   [i] Restarting services...
> 
>   [βœ“] Starting dnsmasq service
> 
>   [βœ“] Enabling dnsmasq service to start on reboot
> 
>   [βœ“] Starting lighttpd service
> 
>   [βœ“] Enabling lighttpd service to start on reboot
> 
>   [βœ“] Starting pihole-FTL service
> 
>   [βœ“] Enabling pihole-FTL service to start on reboot
> 
>   [i] Preparing to run gravity.sh to refresh hosts...
>   [i] Cleaning up previous install (preserving whitelist/blacklist)
>   [i] Running gravity.sh
>   [i] Neutrino emissions detected...
>   [βœ“] Pulling blocklist source list into range
> 
>   [i] Target: raw.githubusercontent.com (hosts)
>   [βœ“] Status: Retrieval successful
> 
>   [i] Target: mirror1.malwaredomains.com (justdomains)
>   [βœ“] Status: Retrieval successful
> 
>   [i] Target: sysctl.org (hosts)
>   [βœ“] Status: Retrieval successful
> 
>   [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
>   [βœ“] Status: Retrieval successful
> 
>   [i] Target: s3.amazonaws.com (simple_tracking.txt)
>   [βœ“] Status: Retrieval successful
> 
>   [i] Target: s3.amazonaws.com (simple_ad.txt)
>   [βœ“] Status: Retrieval successful
> 
>   [i] Target: hosts-file.net (ad_servers.txt)
>   [βœ“] Status: Retrieval successful
> 
>   [βœ“] Consolidating blocklists
>   [βœ“] Extracting domains from blocklists
>   [i] Number of domains being pulled in by gravity: 146,086
>   [βœ“] Removing duplicate domains
>   [i] Number of unique domains trapped in the Event Horizon: 122,954
> 
>   [i] Number of blocklist source domains being added to the whitelist: 6
>   [i] Number of whitelisted domains: 6
>   [βœ“] Parsing domains into hosts format
>   [βœ“] Cleaning up stray matter
> 
>   [βœ“] Force-reloading DNS service
>   [βœ“] DNS service is running
>   [βœ“] Pi-hole blocking is Enabled
>   View the web interface at http://pi.hole/admin or http://192.168.2.104/admin
> 
>   You may now configure your devices to use the Pi-hole as their DNS server
>   [i] Pi-hole DNS (IPv4): 192.168.2.104
>   [i] Pi-hole DNS (IPv6): 2003:c6:3be1:5778:c4f2:ea1:c1e8:c3f0
>   If you set a new IP address, please restart the server running the Pi-hole
> 
>   [i] The install log is located at: /etc/pihole/install.log
>   Installation Complete!

I'm not sure if this is a problem but maybe it has something todo with the dashboard-problem?

> pi@raspberrypi:~ $ curl -I 192.168.2.104
> HTTP/1.1 200 OK
> X-Powered-By: PHP/7.0.27-0+deb9u1
> Content-type: text/html; charset=UTF-8
> Date: Sun, 25 Feb 2018 18:26:54 GMT
> Server: lighttpd/1.4.45
> 
> pi@raspberrypi:~ $ curl -I 192.168.2.104/admin
> HTTP/1.1 301 Moved Permanently
> Location: http://192.168.2.104/admin/
> Date: Sun, 25 Feb 2018 18:27:10 GMT
> Server: lighttpd/1.4.45

And when pressing CTRL-F5 in the browser when viewing the dashboard or try another browser ?

Maybe run another debug for the devs to have a look ?

pihole -d

That's fine, that's pulling the blockpage if you grab the contents.

This is also as expected, this is a redirect from /admin to /admin/. Try curling 192.168.2.104/admin/ and you should get a 200 and the contents of the admin page.

Similar issue - not workin in Safari but works in Chrome on the same machine. Submitted the logs - not sure where to put the debug token so someone can look at the logs.

If it's working on Chrome, then the logs wont show much since it appears to be a browser specific issue. I don't have any Apple devices to be able to check Safari, but I think @jacob.salmela might have something.

1 Like

I could not reproduce this.

When you did pihole -r > Reconfigure, did you choose to enable logging during the process?

Similar issue here. I'm running Raspbian Jessie v8, and performed

pihole -up

albeit not from root. I seem to have successfully upgraded from quite an old version to:
Pi-hole Version v3.3
Web Interface Version v3.3
FTL Version v3.0

pihole -d

shows no faults, except for the "not backing up my index.lighttpd.html because it doesn't exist" information.

However the webUI now fails to display graphs. I flushed the query logs in case there was some issue in pre-upgrade data, but the statistics still show old summaries and the graphs still seem to have melted (after taking a while to load at all).


Addendum - I ran

pihole -r

as well, to no avail.

Checkout the Jessie part in this blog:

Fixed. You sir, are a genius

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