Web Interface not showing any queries

#1

Please follow the below template, it will help us to help you!

Expected Behaviour:

Actual Behaviour:

the pihole web interface is not showing any queries even though it is blocking contents just fine. the log files are empty in /var/log

Debug Token:

Use netcat.

0 Likes

#2

Is that the exact output?

0 Likes

#3

yes that’s the one. i have tried reinstalling and reconfiguring but nothing seems to work.

0 Likes

#4

I mean, is that the whole output from pihole -d?

0 Likes

#5

[i] Reconfigure option selected
[✓] Disk space check

[✓] Update local cache of available packages

[✓] Checking apt-get for upgraded packages… 1 updates available
[i] It is recommended to update your OS after installing the Pi-hole!

[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 [i] Static IP already configured
[i] Unable to find IPv6 ULA/GUA address, IPv6 adblocking will not be enabled
[i] IPv4 address: 192.168.1.6/24
[i] IPv6 address:
[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 (v2.13.2). 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: 132,923
[✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 109,800

[i] Number of blocklist source domains being added to the whitelist: 6
[i] Number of whitelisted domains: 6
[i] Number of blacklisted domains: 0
[i] Number of wildcard blocked domains: 0
[✓] 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.1.6/admin

You may now configure your devices to use the Pi-hole as their DNS server
[i] Pi-hole DNS (IPv4): 192.168.1.6
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!
bukka@orangepizero:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=254 time=0.586 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=254 time=0.591 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=254 time=0.532 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=254 time=0.525 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=254 time=0.508 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=254 time=0.504 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=254 time=0.501 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=254 time=0.483 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=254 time=0.493 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=254 time=0.543 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=254 time=0.443 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=254 time=0.530 ms
^C
— 192.168.1.1 ping statistics —
12 packets transmitted, 12 received, 0% packet loss, time 11417ms
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-01-24:21:35:59 debug log has been initiated.

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

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

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

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v2.13.2

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

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

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

*** [ DIAGNOSING ]: Operating system
[✓] Ubuntu 16.04.3 LTS

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

*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: line 474: $’[\E[32m✓\E[0m] \E[32marmv7l\E[0m’: command not found

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.6/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
fe80::42:a3ff:fe09:ece4 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

^ 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/setupVars.conf, there is no need for concern.

The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.1.1

  • Pinging 192.168.1.1…
    [✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[139] is in use by smbd
[] is in use by
[22] is in use by sshd
[445] is in use by smbd
[61213] is in use by transmiss
[80] is in use by lighttpd
[] is in use by
[4711] is in use by pihole-FTL
[53] is in use by dnsmasq
[53] is in use by dnsmasq

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

*** [ 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.1.6/24
IPV6_ADDRESS=
PIHOLE_DNS_1=218.248.112.193
PIHOLE_DNS_2=
QUERY_LOGGING=true
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 3822327 Jan 24 20:36 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.1.6 0.0.0.0
192.168.1.6 0000mps.webpreview.dsl.net
192.168.1.6 0001.2waky.com
192.168.1.6 000dom.revenuedirect.com

-----tail of gravity.list------
192.168.1.6 zzsyw.com
192.168.1.6 zztxdown.com
192.168.1.6 zzz.clickbank.net
192.168.1.6 zz.zeroredirect1.com

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

-rw-r–r-- 1 pihole pihole 633 Jan 22 20:07 /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 pihole pihole 0 Jan 22 20:26 /etc/pihole/blacklist.txt

-rw-r–r-- 1 pihole pihole 45 Jan 24 20:36 /etc/pihole/local.list
192.168.1.6 orangepizero
192.168.1.6 pi.hole

-rw-r–r-- 1 pihole pihole 238 Jan 24 20:35 /etc/pihole/logrotate
/var/log/pihole.log {
su root syslog
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root syslog
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}

-rw-r–r-- 1 pihole pihole 117 Jan 22 20:09 /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 1495 Jan 24 20:35 /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=218.248.112.193
interface=eth0

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

-rw-r–r-- 1 root root 3027 Jan 24 20:35 /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.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/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 ‘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 1630 Jan 24 20:35 /etc/cron.d/pihole
49 4 * * 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
29 14 * * * 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 2462 Jan 24 20:35 /var/log/lighttpd/error.log
2018-01-22 23:37:57: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-22 23:38:18: (log.c.164) server started
2018-01-22 23:45:37: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-22 23:45:59: (log.c.164) server started
2018-01-23 00:15:56: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-23 00:16:18: (log.c.164) server started
2018-01-23 00:23:07: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-23 00:24:51: (log.c.164) server started
2018-01-23 00:26:26: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-23 00:26:50: (log.c.164) server started
2018-01-23 00:35:04: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Notice: Undefined index: l in /var/www/html/admin/scripts/pi-hole/php/header.php on line 391
2018-01-23 00:35:04: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Notice: Undefined index: l in /var/www/html/admin/scripts/pi-hole/php/header.php on line 395
2018-01-23 00:35:11: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Notice: Undefined index: l in /var/www/html/admin/scripts/pi-hole/php/header.php on line 391
2018-01-23 00:35:11: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Notice: Undefined index: l in /var/www/html/admin/scripts/pi-hole/php/header.php on line 395
2018-01-23 00:35:11: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Notice: Undefined index: l in /var/www/html/admin/list.php on line 10
2018-01-23 09:50:44: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-01-23 09:50:44: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-01-24 02:48:22: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-24 02:48:46: (log.c.164) server started
2018-01-24 03:10:58: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-24 03:11:23: (log.c.164) server started
2018-01-24 03:13:18: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-24 03:13:41: (log.c.164) server started
2018-01-24 03:38:24: (server.c.1558) server stopped by UID = 0 PID = 1
2018-01-24 03:39:12: (log.c.164) server started

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

-rw-r–r-- 1 pihole pihole 4096 Jan 24 20:36 /var/log/pihole-FTL.log
[2018-01-22 23:37:57.522] FATAL: FTL received SIGTERM from PID/UID 1/0, scheduled to exit gracefully
[2018-01-22 23:37:57.523] Shutting down…
[2018-01-22 23:37:57.527]
[2018-01-22 23:38:16.595]
[2018-01-22 23:38:16.595] FTL branch: v2.13.2
[2018-01-22 23:38:16.595] FTL version: v2.13.2
[2018-01-22 23:38:16.596] FTL commit: 1de2b99c8a812d4d2dbe6b1e4644e20a4b14bb1e
[2018-01-22 23:38:16.596] FTL date: 2018-01-07 17:34:24 -0800
[2018-01-22 23:38:16.596] FTL user: pihole
[2018-01-22 23:38:16.596] Notice: Found no readable FTL config file
[2018-01-22 23:38:16.596] Using default settings
[2018-01-22 23:38:16.596] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2018-01-22 23:38:16.596] SOCKET_LISTENING: only local
[2018-01-22 23:38:16.596] TIMEFRAME: Rolling 24h
[2018-01-22 23:38:16.596] QUERY_DISPLAY: Show queries
[2018-01-22 23:38:16.596] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2018-01-22 23:38:16.596] MAXDBDAYS: max age for stored queries is 365 days
[2018-01-22 23:38:16.596] RESOLVE_IPV6: Resolve IPv6 addresses
[2018-01-22 23:38:16.596] RESOLVE_IPV4: Resolve IPv4 addresses
[2018-01-22 23:38:16.597] DBINTERVAL: saving to DB file every minute
[2018-01-22 23:38:16.597] DBFILE: Using /etc/pihole/pihole-FTL.db
[2018-01-22 23:38:16.597] Finished config file parsing
[2018-01-22 23:38:16.604] Found no other running pihole-FTL process
[2018-01-22 23:38:16.609] PID of FTL process: 864
[2018-01-22 23:38:17.480] Gravity list entries: 109727

*** [ DIAGNOSING ]: Pi-hole log
-rw-r–r-- 1 dnsmasq root 0 Jan 24 20:35 /var/log/pihole.log
-----head of pihole.log------

cat: write error: No space left on device



[✓] ** FINISHED DEBUGGING! **

* The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
* For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
* If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.

[?] Would you like to upload the log? [y/N] y
* Using openssl for transmission.



[✓] Your debug token is: Use netcat.



  • Provide the token above to the Pi-hole team for assistance at
  • https://discourse.pi-hole.net
  • Your log will self-destruct on our server after 48 hours.
  • A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log

bukka@orangepizero:~$

0 Likes

#6


i set up pihole on orangepizero(static ip) with TP-LINK adsl router as default getaway.

0 Likes

#7

Check if disk is full with below one ?

df -h

1 Like

#8

sorry for the late reply.
it seems my /var/log directory was full due to syslog logging some recurring error. fixed it up, cleaned the backup files and now everything is running fine. thanks.

1 Like