Pi-hole Issues


#1

Hello
I have done a fresh install of Pi-Hole and from diagnostic all is good.
Real probables list :stuck_out_tongue: :slight_smile:
1 FTL offline
2 No graph is loaded the loading circle never ends :frowning:


3 It dos not block
I have set rooter to distribute Pi-Hole DNS , also set it manually and also tested on installed device…

Debug info:
*** [ INITIALIZING ]
[i] 2019-02-12:08:29:03 debug log has been initialized.

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

*** [ DIAGNOSING ]: Core version
[i] Core: v4.2.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.2.1-0-ge967fe2

*** [ DIAGNOSING ]: Web version
[i] Web: v4.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.2-0-g347994d

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.2.1

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

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

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

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

*** [ DIAGNOSING ]: Processor
[✓] armv7l

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

[✓] IPv6 address(es) bound to the wlan0 interface:
   fe80::208:22ff:feb6:adfb does not match the IP found in /etc/pihole/setupVars.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/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.100.1
   * Pinging 192.168.100.1...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) pihole-FTL (IPv4)
(LISTEN) pihole-FTL (IPv6)
(LISTEN) pihole-FTL (IPv4)
(LISTEN) pihole-FTL (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) sshd (IPv4)
(LISTEN) sshd (IPv6)
(LISTEN) Xtightvnc (IPv4)
(LISTEN) Xtightvnc (IPv4)
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)
(LISTEN) apache2 (IPv6)

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

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

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=wlan0
    IPV4_ADDRESS=192.168.100.27/24
    IPV6_ADDRESS=
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    BLOCKING_ENABLED=true
    DNSMASQ_LISTENING=single
    PIHOLE_DNS_1=208.67.222.222
    PIHOLE_DNS_2=208.67.220.220
    DNS_FQDN_REQUIRED=true
    DNS_BOGUS_PRIV=true
    DNSSEC=false
    CONDITIONAL_FORWARDING=false

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Tue, 12 Feb 2019 06:29:20 GMT
Server: Apache/2.4.18 (Ubuntu)
Last-Modified: Mon, 11 Feb 2019 21:42:09 GMT
ETag: "2c39-581a52e44a1b0"
Accept-Ranges: bytes
Content-Length: 11321
Vary: Accept-Encoding
Content-Type: text/html

[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Tue, 12 Feb 2019 06:29:20 GMT
Server: Apache/2.4.18 (Ubuntu)
Set-Cookie: PHPSESSID=9u2foh8k8hf1tldhr50op9lgu6; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8


*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 2641111 Feb 12 08:28 /etc/pihole/gravity.list
   -----head of gravity.list------
   0.0.0.0
   0.r.msn.com
   0.start.bz
   000.0x1f4b0.com

   -----tail of gravity.list------
   zzz.clickbank.net
   zzzezeroe.fr
   zzzpooeaz-france.com
   zzzrtrcm2.com

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

-rw-r--r-- 1 root root 381 Feb 12 00:18 /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 0 Feb 12 01:20 /etc/pihole/blacklist.txt

-rw-r--r-- 1 root root 48 Feb 12 08:28 /etc/pihole/local.list
   192.168.100.27 localhost
   192.168.100.27 pi.hole

-rw-r--r-- 1 root root 238 Feb 12 00:20 /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 root root 0 Feb 12 01:20 /etc/pihole/whitelist.txt

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

-rw-r--r-- 1 root root 1626 Feb 12 01:57 /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
   dhcp-name-match=set:wpad-ignore,wpad
   dhcp-ignore-names=tag:wpad-ignore
   server=208.67.222.222
   server=208.67.220.220
   domain-needed
   bogus-priv
   interface=wlan0

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

-rw-r--r-- 1 root root 3102 Feb 12 00:20 /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 1704 Feb 12 00:20 /etc/cron.d/pihole
   50 4   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
   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
   41 16  * * *   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

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

-rw-r--r-- 1 root root 24614 Feb 12 08:28 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2019-02-12 00:20:36.967] Using log file /var/log/pihole-FTL.log
   [2019-02-12 00:20:36.968] ########## FTL started! ##########
   [2019-02-12 00:20:36.968] FTL branch: master
   [2019-02-12 00:20:36.968] FTL version: v4.2.1
   [2019-02-12 00:20:36.968] FTL commit: 5f98312
   [2019-02-12 00:20:36.968] FTL date: 2019-02-06 18:36:55 -0800
   [2019-02-12 00:20:36.968] FTL user: root
   [2019-02-12 00:20:36.968] WARNING: Starting pihole-FTL as user root is not recommended
   [2019-02-12 00:20:36.968] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2019-02-12 00:20:36.969]    SOCKET_LISTENING: only local
   [2019-02-12 00:20:36.969]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2019-02-12 00:20:36.969]    MAXDBDAYS: max age for stored queries is 365 days
   [2019-02-12 00:20:36.969]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2019-02-12 00:20:36.969]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2019-02-12 00:20:36.969]    DBINTERVAL: saving to DB file every minute
   [2019-02-12 00:20:36.969]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2019-02-12 00:20:36.969]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2019-02-12 00:20:36.969]    PRIVACYLEVEL: Set to 0
   [2019-02-12 00:20:36.969]    IGNORE_LOCALHOST: Show queries from localhost
   [2019-02-12 00:20:36.969]    BLOCKINGMODE: Null IPs for blocked domains
   [2019-02-12 00:20:36.969]    REGEX_DEBUGMODE: Inactive
   [2019-02-12 00:20:36.969]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2019-02-12 00:20:36.969]    DBIMPORT: Importing history from database
   [2019-02-12 00:20:36.970]    PIDFILE: Using /var/run/pihole-FTL.pid
   [2019-02-12 00:20:36.970]    PORTFILE: Using /var/run/pihole-FTL.port
   [2019-02-12 00:20:36.970]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2019-02-12 00:20:36.970]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2019-02-12 00:20:36.970]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2019-02-12 00:20:36.970]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2019-02-12 00:20:36.970]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2019-02-12 00:20:36.970]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2019-02-12 00:20:36.970]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2019-02-12 00:20:36.970] Finished config file parsing
   [2019-02-12 00:20:36.970] INFO: No whitelist file found
   [2019-02-12 00:20:36.970] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)

   -----tail of pihole-FTL.log------
   [2019-02-12 01:57:03.983]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2019-02-12 01:57:03.983]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2019-02-12 01:57:03.983]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2019-02-12 01:57:03.983]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2019-02-12 01:57:03.983]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2019-02-12 01:57:03.983]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2019-02-12 01:57:03.983]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2019-02-12 01:57:03.983] Finished config file parsing
   [2019-02-12 01:57:03.983] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
   [2019-02-12 01:57:03.985] Database successfully initialized
   [2019-02-12 01:57:03.986] New forward server: 8.8.4.4 (0/4096)
   [2019-02-12 01:57:03.987] New forward server: 8.8.8.8 (1/4096)
   [2019-02-12 01:57:03.988] Imported 241 queries from the long-term database
   [2019-02-12 01:57:03.988]  -> Total DNS queries: 241
   [2019-02-12 01:57:03.988]  -> Cached DNS queries: 50
   [2019-02-12 01:57:03.989]  -> Forwarded DNS queries: 115
   [2019-02-12 01:57:03.989]  -> Exactly blocked DNS queries: 76
   [2019-02-12 01:57:03.989]  -> Unknown DNS queries: 0
   [2019-02-12 01:57:03.989]  -> Unique domains: 130
   [2019-02-12 01:57:03.989]  -> Unique clients: 3
   [2019-02-12 01:57:03.989]  -> Known forward destinations: 2
   [2019-02-12 01:57:03.989] Successfully accessed setupVars.conf
   [2019-02-12 01:57:03.998] PID of FTL process: 12405
   [2019-02-12 01:57:03.999] Listening on port 4711 for incoming IPv4 telnet connections
   [2019-02-12 01:57:04.000] Listening on port 4711 for incoming IPv6 telnet connections
   [2019-02-12 01:57:04.001] Listening on Unix socket
   [2019-02-12 01:57:04.003] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
   [2019-02-12 01:57:04.003] /etc/pihole/black.list: parsed 0 domains (took 0.1 ms)
   [2019-02-12 01:57:05.301] /etc/pihole/gravity.list: parsed 112857 domains (took 1297.3 ms)
   [2019-02-12 01:58:00.166] New forward server: 208.67.220.220 (2/4096)
   [2019-02-12 01:58:00.254] New forward server: 208.67.222.222 (3/4096)
   [2019-02-12 07:50:52.440] Resizing "/FTL-strings" from 4096 to 8192
   [2019-02-12 08:28:53.886] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
   [2019-02-12 08:28:54.073] /etc/pihole/black.list: parsed 0 domains (took 0.1 ms)
   [2019-02-12 08:28:54.922] /etc/pihole/gravity.list: parsed 112843 domains (took 849.7 ms)

*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 root root 16384 Feb 12 01:57 /dev/shm/FTL-client-0
-rw------- 1 root root 16384 Feb 12 01:57 /dev/shm/FTL-client-1
-rw------- 1 root root 16384 Feb 12 01:57 /dev/shm/FTL-client-2
-rw------- 1 root root 16384 Feb 12 07:09 /dev/shm/FTL-client-3
-rw------- 1 root root 16384 Feb 12 07:50 /dev/shm/FTL-client-4
-rw------- 1 root root 163840 Feb 12 01:57 /dev/shm/FTL-clients
-rw------- 1 root root 112 Feb 12 01:57 /dev/shm/FTL-counters
-rw------- 1 root root 131072 Feb 12 01:57 /dev/shm/FTL-domains
-rw------- 1 root root 163840 Feb 12 01:57 /dev/shm/FTL-forwarded
-rw------- 1 root root 28 Feb 12 01:58 /dev/shm/FTL-lock
-rw------- 1 root root 212992 Feb 12 01:57 /dev/shm/FTL-overTime
-rw------- 1 root root 229376 Feb 12 01:59 /dev/shm/FTL-queries
-rw------- 1 root root 8192 Feb 12 07:50 /dev/shm/FTL-strings

*** [ DIAGNOSING ]: Locale
    LANG=C

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 146334 Feb 12 08:29 /var/log/pihole.log
   -----head of pihole.log------
   Feb 12 00:20:39 dnsmasq[23283]: started, version pi-hole-2.80 cachesize 10000
   Feb 12 00:20:39 dnsmasq[23283]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify dumpfile
   Feb 12 00:20:39 dnsmasq[23283]: using nameserver 8.8.4.4#53
   Feb 12 00:20:39 dnsmasq[23283]: using nameserver 8.8.8.8#53
   Feb 12 00:20:39 dnsmasq[23283]: read /etc/hosts - 4 addresses
   Feb 12 00:20:39 dnsmasq[23283]: read /etc/pihole/local.list - 2 addresses
   Feb 12 00:20:39 dnsmasq[23283]: failed to load names from /etc/pihole/black.list: No such file or directory
   Feb 12 00:20:40 dnsmasq[23283]: read /etc/pihole/gravity.list - 112857 addresses
   Feb 12 00:20:40 dnsmasq[23283]: read /etc/hosts - 4 addresses
   Feb 12 00:20:40 dnsmasq[23283]: read /etc/pihole/local.list - 2 addresses
   Feb 12 00:20:40 dnsmasq[23283]: failed to load names from /etc/pihole/black.list: No such file or directory
   Feb 12 00:20:41 dnsmasq[23283]: read /etc/pihole/gravity.list - 112857 addresses
   Feb 12 00:20:41 dnsmasq[23283]: query[A] api.github.com from 127.0.0.1
   Feb 12 00:20:41 dnsmasq[23283]: forwarded api.github.com to 8.8.4.4
   Feb 12 00:20:41 dnsmasq[23283]: forwarded api.github.com to 8.8.8.8
   Feb 12 00:20:41 dnsmasq[23283]: query[AAAA] api.github.com from 127.0.0.1
   Feb 12 00:20:41 dnsmasq[23283]: forwarded api.github.com to 8.8.4.4
   Feb 12 00:20:41 dnsmasq[23283]: forwarded api.github.com to 8.8.8.8
   Feb 12 00:20:41 dnsmasq[23283]: reply api.github.com is NODATA-IPv6
   Feb 12 00:20:41 dnsmasq[23283]: reply api.github.com is 192.30.253.117


********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

token is: 8zhxah0d2d

Any Idea?


#2

Your debug log shows that Pi-Hole is working and processing queries. This section tests DNS resolution:

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

This section shows the query activity for the 24 hours prior to the time shown in the log:

   [2019-02-12 01:57:03.988] Imported 241 queries from the long-term database
   [2019-02-12 01:57:03.988]  -> Total DNS queries: 241
   [2019-02-12 01:57:03.988]  -> Cached DNS queries: 50
   [2019-02-12 01:57:03.989]  -> Forwarded DNS queries: 115
   [2019-02-12 01:57:03.989]  -> Exactly blocked DNS queries: 76
   [2019-02-12 01:57:03.989]  -> Unknown DNS queries: 0
   [2019-02-12 01:57:03.989]  -> Unique domains: 130
   [2019-02-12 01:57:03.989]  -> Unique clients: 3
   [2019-02-12 01:57:03.989]  -> Known forward destinations: 2

The problem with the admin dashboard is that you are running Apache web server, and this is preventing lighttpd from running on port 80. Lighttpd is the server Pi-Hole uses by default for the web admin page.

[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Tue, 12 Feb 2019 06:29:20 GMT
Server: Apache/2.4.18 (Ubuntu)

#5

Thenks for your replay
I have been busy trying different settings, uninstalling updating and changing different service’s apache, lighttpd, php, mysql at one point I managed to have web interface x and Dash V but I was not connecting to web anymore and was getting results from console (-d)…
So in the end I re-installed fresh OS and run install script (after apt curl )…
Unfortunately same result :frowning:

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Date: Wed, 13 Feb 2019 20:25:10 GMT
Server: lighttpd/1.4.35

[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r–r-- 1 root root 2641125 Feb 13 20:29 /etc/pihole/gravity.list
-----head of gravity.list------
0.0.0.0
0.r.msn.com
0.start.bz
000.0x1f4b0.com

-----tail of gravity.list------
zzz.clickbank.net
zzzezeroe.fr
zzzpooeaz-france.com
zzzrtrcm2.com


token is: 4lgv8lqzwc

Server is working is only web statistics missing and FTL resorting offline …
Any idea ?
Thenks in advance.


#6

Your new debug log shows that Pi-Hole is correctly resolving DNS queries. There are some errors in your lighttpd log, so the problem appears to be limited to the function of the web admin page.

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

  [2019-02-13 22:09:51.636] Imported 560 queries from the long-term database
   [2019-02-13 22:09:51.636]  -> Total DNS queries: 560
   [2019-02-13 22:09:51.636]  -> Cached DNS queries: 158
   [2019-02-13 22:09:51.636]  -> Forwarded DNS queries: 319
   [2019-02-13 22:09:51.636]  -> Exactly blocked DNS queries: 81
   [2019-02-13 22:09:51.637]  -> Unknown DNS queries: 2
   [2019-02-13 22:09:51.637]  -> Unique domains: 194
   [2019-02-13 22:09:51.637]  -> Unique clients: 7
   [2019-02-13 22:09:51.637]  -> Known forward destinations: 3

What are the outputs of the following:

sudo service lighttpd status

journalctl -u lighttpd -l


#7

r@localhost:~$ sudo service lighttpd status

  • lighttpd is running
    r@localhost:~$ journalctl -u lighttpd -l
    No journal files were found.
    – No entries –

What about FTL stat also wrongly flagged because lighttpd passing?

Is there any other way I can pull statistics similar web :D?


#8

That is not the output you would expect from that command. What was the full output? It typically would look something like this:

● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-02-07 12:01:08 CST; 6 days ago
 Main PID: 31901 (lighttpd)
   CGroup: /system.slice/lighttpd.service
           ├─28632 /usr/bin/php-cgi
           ├─28640 /usr/bin/php-cgi
           ├─28699 /usr/bin/php-cgi
           ├─28832 /usr/bin/php-cgi
           ├─31901 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
           └─31915 /usr/bin/php-cgi

Feb 13 11:36:49 Pi-3B sudo[4879]: pam_unix(sudo:session): session closed for user root
Feb 13 11:36:57 Pi-3B sudo[4896]: www-data : TTY=unknown ; PWD=/var/www/html/admin ; USER=root ; COMMAND=/usr/local/bin/pihole status web
Feb 13 11:36:57 Pi-3B sudo[4896]: pam_unix(sudo:session): session opened for user root by (uid=0)
...

#9

Maybe this is all I get because running in chroot?
This is all I get :slight_smile:
r@localhost:~$ sudo service lighttpd status

  • lighttpd is running
    r@localhost:~$ lighttpd -v
    lighttpd/1.4.35 (ssl) - a light and fast webserver
    Build-Date: Apr 18 2016 15:42:23
    r@localhost:~$

#10

I was trying to get the statistics in a some other way especially Top Client and Client (over time) and I see a thread mentioning script gui, if we can get statistics in shell interface with pihole -s the answer was you can get them from admin/api.php?summaryRaw for me this is all that I get:
{“FTLnotrunning”:true}


#11

Have you tried not running it in chroot (that would have been good to know at the start)? You may also be interested in the docker container: https://hub.docker.com/r/pihole/pihole/