Pihole will not resolve clients after VPN install (and uninstall)

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

Expected Behaviour:

Pihole should be blocking ads on clients as well as the host

Actual Behaviour:

clients just hang and domains do not resolve. Of note, this happened after I followed this tutorial to set up a VPN on my server: https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04

I have since completely uninstalled and reversed the tutorial, but the problem persists.

Additionally, I can completely reinstall pihole and it works perfectly, but after a reboot it, again, fails to resolve on clients. I can still ping sites from the server.

Thanks so much for any help. I searched the forums but I couldn’t find anything that replicated my issue…

Debug Token:

I get the error: [✗] There was an error uploading your debug log. When I try. Here is the output:

*** [ INITIALIZING ]
[i] 2020-01-18:13:47:21 debug log has been initialized.

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

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

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

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

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

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

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

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

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

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

[✓] IPv6 address(es) bound to the enp3s0 interface:
   fe80::6a05:caff:fe2d:a904 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.1
   * Pinging 192.168.1.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: dev
   * Pinging dev...
ping: dev: No address associated with hostname
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)


*** [ DIAGNOSING ]: Ports in use
*:8096 EmbyServer (IPv6)
*:8920 EmbyServer (IPv6)
*:25565 java (IPv6)
*:25566 java (IPv6)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:445 smbd (IPv6)
*:139 smbd (IPv6)
*:445 smbd (IPv4)
*:139 smbd (IPv4)
[192.168.1.207:53] is in use by pihole-FTL
[127.0.0.1:53] is in use by pihole-FTL
[[fe80::6a05:caff:fe2d:a904]:53] is in use by pihole-FTL
[[::1]:53] is in use by pihole-FTL
[127.0.0.1:4711] is in use by pihole-FTL
[[::1]:4711] is in use by pihole-FTL
127.0.0.1:3306 mysqld (IPv4)
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)
[10.2.144.1:53] is in use by pihole-FTL
[[fe80::e07d:bff:fe3f:dd7b]:53] is in use by pihole-FTL
[[fd42:cbfa:4f3e:9468::1]:53] is in use by pihole-FTL
[*:80] is in use by lighttpd
*:443 apache2 (IPv6)

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

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] regionalnyportal.eu is :: via localhost (::1)
[✓] regionalnyportal.eu is :: via Pi-hole (fd42:cbfa:4f3e:9468::1)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

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

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=enp3s0
    IPV4_ADDRESS=192.168.1.207/24
    IPV6_ADDRESS=fd42:cbfa:4f3e:9468::1
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=false
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=false
    BLOCKING_ENABLED=true

*** [ 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: Sat, 18 Jan 2020 13:47:28 GMT
Server: Apache/2.4.29 (Ubuntu)
Last-Modified: Tue, 04 Dec 2018 15:49:03 GMT
ETag: "0-57c34347842a8"
Accept-Ranges: bytes
Content-Type: text/html

[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Sat, 18 Jan 2020 13:47:28 GMT
Server: Apache/2.4.29 (Ubuntu)
Set-Cookie: PHPSESSID=a2817h63iqbbi996h0um8qp9ue; 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 2887777 Jan 18 13:41 /etc/pihole/gravity.list
   -----head of gravity.list------
   0.0.0.0
   0.nextyourcontent.com
   0.r.msn.com
   0.start.bz

   -----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 313 Jan 18 01:11 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   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 104 Jan 18 13:41 /etc/pihole/local.list
   192.168.1.207 server
   fd42:cbfa:4f3e:9468::1 server
   192.168.1.207 pi.hole
   fd42:cbfa:4f3e:9468::1 pi.hole

-rw-r--r-- 1 root root 238 Jan 18 01:12 /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
   }

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

-rw-r--r-- 1 root root 1389 Jan 18 01:12 /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.8.8
   server=8.8.4.4
   interface=enp3s0

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

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

-rw-r--r-- 1 root root 1704 Jan 18 01:12 /etc/cron.d/pihole
   11 3   * * 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
   39 15  * * *   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
/var/log/lighttpd does not exist.
ls: cannot access '/var/log/lighttpd': No such file or directory

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

-rw-r--r-- 1 pihole pihole 18476 Jan 18 13:41 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2020-01-18 01:12:59.137 5722] Using log file /var/log/pihole-FTL.log
   [2020-01-18 01:12:59.137 5722] ########## FTL started! ##########
   [2020-01-18 01:12:59.137 5722] FTL branch: master
   [2020-01-18 01:12:59.137 5722] FTL version: v4.3.1
   [2020-01-18 01:12:59.137 5722] FTL commit: b60d63f
   [2020-01-18 01:12:59.137 5722] FTL date: 2019-05-25 21:37:26 +0200
   [2020-01-18 01:12:59.137 5722] FTL user: pihole
   [2020-01-18 01:12:59.137 5722] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2020-01-18 01:12:59.137 5722]    SOCKET_LISTENING: only local
   [2020-01-18 01:12:59.137 5722]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2020-01-18 01:12:59.137 5722]    MAXDBDAYS: max age for stored queries is 365 days
   [2020-01-18 01:12:59.137 5722]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2020-01-18 01:12:59.137 5722]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2020-01-18 01:12:59.137 5722]    DBINTERVAL: saving to DB file every minute
   [2020-01-18 01:12:59.137 5722]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2020-01-18 01:12:59.137 5722]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2020-01-18 01:12:59.137 5722]    PRIVACYLEVEL: Set to 0
   [2020-01-18 01:12:59.137 5722]    IGNORE_LOCALHOST: Show queries from localhost
   [2020-01-18 01:12:59.137 5722]    BLOCKINGMODE: Null IPs for blocked domains
   [2020-01-18 01:12:59.137 5722]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2020-01-18 01:12:59.137 5722]    DBIMPORT: Importing history from database
   [2020-01-18 01:12:59.137 5722]    PIDFILE: Using /var/run/pihole-FTL.pid
   [2020-01-18 01:12:59.137 5722]    PORTFILE: Using /var/run/pihole-FTL.port
   [2020-01-18 01:12:59.137 5722]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2020-01-18 01:12:59.137 5722]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2020-01-18 01:12:59.137 5722]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2020-01-18 01:12:59.137 5722]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2020-01-18 01:12:59.137 5722]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2020-01-18 01:12:59.137 5722]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2020-01-18 01:12:59.137 5722]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2020-01-18 01:12:59.137 5722]    MACVENDORDB: Using /etc/pihole/macvendor.db
   [2020-01-18 01:12:59.137 5722]    PARSE_ARP_CACHE: Active
   [2020-01-18 01:12:59.137 5722] Finished config file parsing
   [2020-01-18 01:12:59.138 5722] SQLite3 message: cannot open file at line 38452 of [0eca3dd3d3] (14)
   [2020-01-18 01:12:59.138 5722] SQLite3 message: os_unix.c:38452: (2) open(/etc/pihole/pihole-FTL.db) -  (14)

   -----tail of pihole-FTL.log------
   [2020-01-18 13:34:40.568 1587]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2020-01-18 13:34:40.568 1587]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2020-01-18 13:34:40.568 1587]    MACVENDORDB: Using /etc/pihole/macvendor.db
   [2020-01-18 13:34:40.568 1587]    PARSE_ARP_CACHE: Active
   [2020-01-18 13:34:40.568 1587] Finished config file parsing
   [2020-01-18 13:34:40.573 1587] Database version is 3
   [2020-01-18 13:34:40.573 1587] Database successfully initialized
   [2020-01-18 13:34:40.573 1587] New forward server: 8.8.4.4 (0/512)
   [2020-01-18 13:34:40.574 1587] New forward server: 8.8.8.8 (1/512)
   [2020-01-18 13:34:40.574 1587] Resizing "/FTL-strings" from 4096 to 8192
   [2020-01-18 13:34:40.575 1587] Resizing "/FTL-strings" from 8192 to 12288
   [2020-01-18 13:34:40.576 1587] Imported 1904 queries from the long-term database
   [2020-01-18 13:34:40.576 1587]  -> Total DNS queries: 1904
   [2020-01-18 13:34:40.576 1587]  -> Cached DNS queries: 303
   [2020-01-18 13:34:40.576 1587]  -> Forwarded DNS queries: 1464
   [2020-01-18 13:34:40.576 1587]  -> Exactly blocked DNS queries: 137
   [2020-01-18 13:34:40.576 1587]  -> Unknown DNS queries: 0
   [2020-01-18 13:34:40.576 1587]  -> Unique domains: 402
   [2020-01-18 13:34:40.576 1587]  -> Unique clients: 4
   [2020-01-18 13:34:40.576 1587]  -> Known forward destinations: 2
   [2020-01-18 13:34:40.576 1587] Successfully accessed setupVars.conf
   [2020-01-18 13:34:40.581 1623] PID of FTL process: 1623
   [2020-01-18 13:34:40.581 1623] Listening on port 4711 for incoming IPv4 telnet connections
   [2020-01-18 13:34:40.581 1623] Listening on port 4711 for incoming IPv6 telnet connections
   [2020-01-18 13:34:40.581 1623] Listening on Unix socket
   [2020-01-18 13:34:40.758 1623] Received SIGHUP, reloading cache
   [2020-01-18 13:34:40.758 1623] Blocking status is enabled
   [2020-01-18 13:34:40.758 1623] INFO: No whitelist file found
   [2020-01-18 13:34:40.758 1623] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
   [2020-01-18 13:34:41.953 1623] /etc/pihole/gravity.list: parsed 124212 domains (took 1045.1 ms)
   [2020-01-18 13:41:12.020 1623] Received SIGHUP, reloading cache
   [2020-01-18 13:41:12.020 1623] Blocking status is enabled
   [2020-01-18 13:41:12.020 1623] INFO: No whitelist file found
   [2020-01-18 13:41:12.020 1623] Compiled 0 Regex filters and 0 whitelisted domains in 0.0 msec (0 errors)
   [2020-01-18 13:41:12.387 1623] /etc/pihole/gravity.list: parsed 124212 domains (took 281.1 ms)

*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 pihole pihole 331776 Jan 18 13:34 /dev/shm/FTL-clients
-rw------- 1 pihole pihole 108 Jan 18 13:34 /dev/shm/FTL-counters
-rw------- 1 pihole pihole 98304 Jan 18 13:34 /dev/shm/FTL-domains
-rw------- 1 pihole pihole 20480 Jan 18 13:34 /dev/shm/FTL-forwarded
-rw------- 1 pihole pihole 48 Jan 18 13:34 /dev/shm/FTL-lock
-rw------- 1 pihole pihole 12288 Jan 18 13:34 /dev/shm/FTL-overTime
-rw------- 1 pihole pihole 229376 Jan 18 13:36 /dev/shm/FTL-queries
-rw------- 1 pihole pihole 12 Jan 18 13:34 /dev/shm/FTL-settings
-rw------- 1 pihole pihole 12288 Jan 18 13:34 /dev/shm/FTL-strings

*** [ DIAGNOSING ]: Locale
    LANG=en_US.UTF-8

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 689870 Jan 18 13:47 /var/log/pihole.log
   -----head of pihole.log------
   Jan 18 01:12:59 dnsmasq[5724]: started, version pi-hole-2.80 cachesize 10000
   Jan 18 01:12:59 dnsmasq[5724]: 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
   Jan 18 01:12:59 dnsmasq[5724]: using nameserver 8.8.4.4#53
   Jan 18 01:12:59 dnsmasq[5724]: using nameserver 8.8.8.8#53
   Jan 18 01:12:59 dnsmasq[5724]: read /etc/hosts - 9 addresses
   Jan 18 01:12:59 dnsmasq[5724]: failed to load names from /etc/pihole/local.list: No such file or directory
   Jan 18 01:12:59 dnsmasq[5724]: failed to load names from /etc/pihole/black.list: No such file or directory
   Jan 18 01:12:59 dnsmasq[5724]: failed to load names from /etc/pihole/gravity.list: No such file or directory
   Jan 18 01:12:59 dnsmasq[5724]: query[AAAA] raw.githubusercontent.com from 127.0.0.1
   Jan 18 01:12:59 dnsmasq[5724]: forwarded raw.githubusercontent.com to 8.8.4.4
   Jan 18 01:12:59 dnsmasq[5724]: forwarded raw.githubusercontent.com to 8.8.8.8
   Jan 18 01:12:59 dnsmasq[5724]: reply raw.githubusercontent.com is <CNAME>
   Jan 18 01:12:59 dnsmasq[5724]: reply github.map.fastly.net is NODATA-IPv6
   Jan 18 01:12:59 dnsmasq[5724]: query[A] raw.githubusercontent.com from 127.0.0.1
   Jan 18 01:12:59 dnsmasq[5724]: cached raw.githubusercontent.com is <CNAME>
   Jan 18 01:12:59 dnsmasq[5724]: forwarded raw.githubusercontent.com to 8.8.4.4
   Jan 18 01:12:59 dnsmasq[5724]: reply raw.githubusercontent.com is <CNAME>
   Jan 18 01:12:59 dnsmasq[5724]: reply github.map.fastly.net is 151.101.0.133
   Jan 18 01:12:59 dnsmasq[5724]: reply github.map.fastly.net is 151.101.64.133
   Jan 18 01:12:59 dnsmasq[5724]: reply github.map.fastly.net is 151.101.128.133

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