0

I've been using a Raspberry Pi 3B (running Raspbian) with OpenVPN and ISC DHCP for about a month now and everything has been great.

I decided to add Pi Hole to block ads network wide and used this video tutorial. The setup was very easy and everything worked very well to start with.

However, I needed to restart my pi and since doing that the Pi Hole seems to have stopped working completely in that no hosts are resolved AND the web interface 192.168.1.15/admin for Pi Hole is no longer available.

When I run pihole status I get the following:

[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

Which suggests the service is running, but for sure it is not resolving host names.

When I run pihole -d I get:

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-06-28:07:23:05 debug log has been initialized.

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

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

*** [ 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
[✓] Default SELinux: permissive
[✓] Current SELinux: Disabled

*** [ DIAGNOSING ]: Processor

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

[✓] IPv6 address(es) bound to the eth0 interface:
   fe80::cd06:9e93:85bd:e6ca 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.1.254
   * Pinging 192.168.1.254...
[✓] 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 known ad-serving domain
[✓] www.kdukvh.com is 192.168.1.15 via localhost (127.0.0.1)
[✓] www.kdukvh.com is 192.168.1.15 via Pi-hole (192.168.1.15)
[✓] doubleclick.com is 172.217.16.238 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.15/24
    IPV6_ADDRESS=
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    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 4550107 Jun 28 03:53 /etc/pihole/gravity.list
   -----head of gravity.list------
   192.168.1.15 0.0.0.0
   192.168.1.15 0.r.msn.com
   192.168.1.15 0.start.bz
   192.168.1.15 000.0x1f4b0.com

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

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

-rw-r--r-- 1 root root 633 Jun 27 18:04 /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 Jun 28 03:50 /etc/pihole/blacklist.txt

-rw-r--r-- 1 root root 46 Jun 28 03:53 /etc/pihole/local.list
   192.168.1.15 raspberrypi
   192.168.1.15 pi.hole

-rw-r--r-- 1 root root 234 Jun 27 18:02 /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 14 Jun 28 03:50 /etc/pihole/whitelist.txt
   s.youtube.com

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

-rw-r--r-- 1 root root 1508 Jun 27 18:04 /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=extra
   log-facility=/var/log/pihole.log
   local-ttl=2
   log-async
   server=8.8.8.8
   server=8.8.4.4
   interface=eth0

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

-rw-r--r-- 1 root root 3027 Jun 27 18:02 /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 1496 Jun 27 18:02 /etc/cron.d/pihole
   53 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
   29 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 533 Jun 28 06:38 /var/log/lighttpd/error.log
   2018-06-27 18:01:10: (log.c.217) server started 
   2018-06-27 18:04:13: (server.c.1828) server stopped by UID = 0 PID = 1 
   2018-06-27 18:04:14: (log.c.217) server started 
   2018-06-28 06:19:30: (server.c.1828) server stopped by UID = 0 PID = 1 
   2018-06-28 06:19:53: (log.c.217) server started 
   2018-06-28 06:35:27: (server.c.1828) server stopped by UID = 0 PID = 1 
   2018-06-28 06:35:48: (log.c.217) server started 
   2018-06-28 06:38:24: (server.c.1828) server stopped by UID = 0 PID = 1 
   2018-06-28 06:38:43: (log.c.217) server started 

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

-rw-r--r-- 1 pihole pihole 13510 Jun 28 06:40 /var/log/pihole-FTL.log
   [2018-06-28 00:00:03.167] NOTICE: pihole.log has been flushed
   [2018-06-28 00:00:03.167]   Resetting internal data structure
   [2018-06-28 00:00:03.167]   Queries in memory before flushing: 451
   [2018-06-28 00:00:03.168] FATAL: Trying to free NULL pointer in pihole_log_flushed() (flush.c:61)
   [2018-06-28 00:00:03.473] Gravity list entries: 127353
   [2018-06-28 00:00:03.473] No blacklist present
   [2018-06-28 00:00:03.473] No wildcard blocking list present
   [2018-06-28 00:00:03.474] Notice: Increasing queries struct size from 0 to 10000 (440.23 KB)
   [2018-06-28 00:00:03.474] Notice: Increasing domains struct size from 0 to 1000 (460.23 KB)
   [2018-06-28 00:00:03.475] Notice: Increasing clients struct size from 0 to 10 (460.39 KB)
   [2018-06-28 00:00:03.475] New client: 127.0.0.1 localhost (0/10)
   [2018-06-28 00:00:03.475] Notice: Increasing forwarded struct size from 0 to 4 (460.50 KB)
   [2018-06-28 00:00:03.564] New forward server: 8.8.4.4 google-public-dns-b.google.com (0/4)
   [2018-06-28 00:00:03.564] Notice: Increasing overTime struct size from 0 to 100 (464.54 KB)
   [2018-06-28 00:00:03.647] New client: 192.168.1.64 (1/10)
   [2018-06-28 00:00:03.651] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
   [2018-06-28 00:00:03.657] Imported 451 queries from the long-term database
   [2018-06-28 00:00:03.657] Reading from /var/log/pihole.log (rw-r--r--)
   [2018-06-28 03:50:22.825] NOTICE: Received signal SIGHUP - re-reading gravity files
   [2018-06-28 03:50:23.132] Gravity list entries: 127353
   [2018-06-28 03:50:23.132] No blacklist present
   [2018-06-28 03:50:23.132] No wildcard blocking list present
   [2018-06-28 03:50:23.132]  -> Total DNS queries: 451
   [2018-06-28 03:50:23.132]  -> Cached DNS queries: 45
   [2018-06-28 03:50:23.132]  -> Forwarded DNS queries: 331

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 158042 Jun 28 07:23 /var/log/pihole.log
   -----head of pihole.log------
   Jun 28 00:00:03 dnsmasq[12931]: 1070 127.0.0.1/54461 query[PTR] 4.4.8.8.in-addr.arpa from 127.0.0.1
   Jun 28 00:00:03 dnsmasq[12931]: 1070 127.0.0.1/54461 forwarded 4.4.8.8.in-addr.arpa to 8.8.4.4
   Jun 28 00:00:03 dnsmasq[12931]: 1070 127.0.0.1/54461 forwarded 4.4.8.8.in-addr.arpa to 8.8.8.8
   Jun 28 00:00:03 dnsmasq[12931]: 1070 127.0.0.1/54461 reply 8.8.4.4 is google-public-dns-b.google.com
   Jun 28 00:00:03 dnsmasq[12931]: 1071 127.0.0.1/35913 query[PTR] 64.1.168.192.in-addr.arpa from 127.0.0.1
   Jun 28 00:00:03 dnsmasq[12931]: 1071 127.0.0.1/35913 forwarded 64.1.168.192.in-addr.arpa to 8.8.8.8
   Jun 28 00:00:03 dnsmasq[12931]: 1072 127.0.0.1/60992 query[PTR] 8.8.8.8.in-addr.arpa from 127.0.0.1
   Jun 28 00:00:03 dnsmasq[12931]: 1072 127.0.0.1/60992 cached 8.8.8.8 is google-public-dns-a.google.com
   Jun 28 00:00:03 dnsmasq[12931]: 1073 127.0.0.1/51995 query[PTR] 64.1.168.192.in-addr.arpa from 127.0.0.1
   Jun 28 00:00:03 dnsmasq[12931]: 1073 127.0.0.1/51995 forwarded 64.1.168.192.in-addr.arpa to 8.8.8.8
   Jun 28 00:59:00 dnsmasq[12931]: 1074 127.0.0.1/52401 query[PTR] 64.1.168.192.in-addr.arpa from 127.0.0.1
   Jun 28 00:59:00 dnsmasq[12931]: 1074 127.0.0.1/52401 forwarded 64.1.168.192.in-addr.arpa to 8.8.4.4
   Jun 28 00:59:00 dnsmasq[12931]: 1074 127.0.0.1/52401 forwarded 64.1.168.192.in-addr.arpa to 8.8.8.8
   Jun 28 01:59:00 dnsmasq[12931]: 1075 127.0.0.1/49347 query[PTR] 64.1.168.192.in-addr.arpa from 127.0.0.1
   Jun 28 01:59:00 dnsmasq[12931]: 1075 127.0.0.1/49347 forwarded 64.1.168.192.in-addr.arpa to 8.8.4.4
   Jun 28 01:59:00 dnsmasq[12931]: 1075 127.0.0.1/49347 forwarded 64.1.168.192.in-addr.arpa to 8.8.8.8
   Jun 28 02:59:00 dnsmasq[12931]: 1076 127.0.0.1/38169 query[PTR] 64.1.168.192.in-addr.arpa from 127.0.0.1
   Jun 28 02:59:00 dnsmasq[12931]: 1076 127.0.0.1/38169 forwarded 64.1.168.192.in-addr.arpa to 8.8.4.4
   Jun 28 02:59:00 dnsmasq[12931]: 1076 127.0.0.1/38169 forwarded 64.1.168.192.in-addr.arpa to 8.8.8.8
   Jun 28 03:50:22 dnsmasq[12931]: read /etc/hosts - 5 addresses

I've tried a few fixes I've found online, but nothing has worked.

I am assuming it has something to do with the VPN and the tun0 interface, but this is working, when I change my DHCP (ISC DHCP not the Pi Hole DHCP) setting back to using Google DNS servers everything works fine again, so I think it is the Pi Hole that is failing somehow even when showing that it is running and enabled. I also don't know why the web interface stopped working since I go directly to the IP Address.

Any suggestions on how to proceed or ideas of what could be causing this?

Thanks,

Stu.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.