Can't connect to PiHole's Web UI

Help
1

Hi there!
Just installed PiHole on Raspberry1 with DietPi and for some reason I can't access the UI.
Here's the log:

root@DietPi:~# cat /var/log/pihole_debug.log

---= Detecting Installed Package Versions:

Pi-hole: v3.0.1 (master:v3.0.1-0-g26fcb1b)
Pi-hole Dashboard: v3.0.1 (master:v3.0.1-0-ge204cea-dirty)
lighttpd/1.4.35
PHP 5.6.30-0+deb8u1 (cli) (built: Apr 14 2017 16:20:58)

---= Detecting existence of /etc/pihole/setupVars.conf:

PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.8.112/24
IPV6_ADDRESS=
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
QUERY_LOGGING=true
INSTALL_WEB=true

---= Detecting installed OS Distribution

PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

---= Checking processor variety

armv6l

---= Checking IPv6 Stack

IPv6 on eth0
Gravity configured for: NOT CONFIGURED

fe80::8238:8ee1:64fe:6bf2/64
No gateway detected.

---= Checking IPv4 Stack

IPv4 on eth0
Gravity configured for: 192.168.8.112/24

192.168.8.112/24

---= Daemon Process Information

Failure: IPv4 Port not in use

---= Daemon Process Information

Found user dnsmasq with process dnsmasq

---= Daemon Process Information

Found user pihole with process pihole-FTL

---= Processes Check

Status for lighttpd daemon:
failed
Status for dnsmasq daemon:
active
Status for pihole-FTL daemon:
active

---= Resolver Functions Check (IPv4)

Resolution of dkb01.webtrekk.net from Pi-hole (127.0.0.1):
192.168.8.112

Resolution of dkb01.webtrekk.net from Pi-hole (192.168.8.112):
192.168.8.112

Resolution of dkb01.webtrekk.net from 8.8.8.8:
185.54.150.17

Pi-hole dnsmasq specific records lookups
Cache Size:
"10000"
Upstream Servers:
"8.8.4.4#53 2 0" "8.8.8.8#53 2 0"

---= Detecting existence of /etc/lighttpd/lighttpd.conf:

server.modules = (
"mod_access",
"mod_alias",
"mod_compress",
"mod_redirect",
)
server.document-root = "/var/www"
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
index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
url.access-deny = ( "~", ".inc" )
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 "/usr/share/lighttpd/include-conf-enabled.pl"

---= Detecting existence of /var/log/lighttpd/error.log:

/var/log/lighttpd/error.log not found!

---= Detecting existence of /etc/dnsmasq.conf:

conf-dir=/etc/dnsmasq.d

---= Detecting contents of /etc/dnsmasq.d/*:

---= File /etc/dnsmasq.d/01-pihole.conf found

addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/local.list
domain-needed
localise-queries
bogus-priv
no-resolv
server=8.8.8.8
server=8.8.4.4
interface=eth0
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=300
log-async

---= File /etc/dnsmasq.d/README found

---= Detecting existence of /etc/pihole/whitelist.txt:

raw.githubusercontent.com
mirror1.malwaredomains.com
sysctl.org
zeustracker.abuse.ch
s3.amazonaws.com
hosts-file.net

---= Detecting existence of /etc/pihole/blacklist.txt:

/etc/pihole/blacklist.txt not found!

---= Detecting existence of /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

---= Analyzing gravity.list

/etc/pihole/gravity.list is 105960 lines long.

---= Analyzing pihole.log

/var/log/pihole.log is 33360 lines long.
/var/log/pihole.log is 2.2M.

---= Analyzing pihole-FTL.log

/var/log/pihole-FTL.log is 79 lines long.
/var/log/pihole-FTL.log is 8.0K.
[2017-05-12 20:39:53.784] dnsmasq process restarted
[2017-05-12 20:39:54.981] Gravity list entries: 105960
[2017-05-12 20:39:54.982] No blacklist present
[2017-05-12 20:39:54.982] No wildcard blocking list present
[2017-05-12 20:40:19.830] Notice: Increasing queries struct size from 0 to 10000 (320.09 KB)
[2017-05-12 20:40:19.831] Notice: Increasing overTime struct size from 0 to 100 (323.29 KB)
[2017-05-12 20:40:19.831] Notice: Increasing forwarded struct size from 0 to 4 (323.36 KB)
[2017-05-12 20:40:19.957] New forward server: 8.8.4.4 google-public-dns-b.google.com (0/4)
[2017-05-12 20:40:19.957] Notice: Increasing domains struct size from 0 to 1000 (343.40 KB)
[2017-05-12 20:40:19.957] Notice: Increasing clients struct size from 0 to 10 (343.57 KB)
[2017-05-12 20:40:19.958] New client: 127.0.0.1 localhost (0/10)
[2017-05-12 20:40:20.092] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
[2017-05-13 00:00:01.842] NOTICE: pihole.log has been flushed
[2017-05-13 00:00:01.843] Resetting internal data structure
[2017-05-13 00:00:01.843] Queries in memory before flushing: 4772
[2017-05-13 00:00:02.362] Gravity list entries: 105960
[2017-05-13 00:00:02.362] No blacklist present
[2017-05-13 00:00:02.362] No wildcard blocking list present
[2017-05-13 00:00:02.362] Warning: Reading of rotated log file /var/log/pihole.log.1 failed
[2017-05-13 00:00:02.363] Reading from /var/log/pihole.log (rwxrwxr-x)
[2017-05-13 00:00:09.576] Notice: Increasing queries struct size from 0 to 10000 (320.19 KB)
[2017-05-13 00:00:09.576] Notice: Increasing overTime struct size from 0 to 100 (323.39 KB)
[2017-05-13 00:00:09.577] Notice: Increasing domains struct size from 0 to 1000 (343.39 KB)
[2017-05-13 00:00:09.577] Notice: Increasing clients struct size from 0 to 10 (343.57 KB)
[2017-05-13 00:00:09.578] New client: 127.0.0.1 localhost (0/10)
[2017-05-13 00:05:21.156] Notice: Increasing forwarded struct size from 0 to 4 (343.65 KB)
[2017-05-13 00:05:21.164] New forward server: 8.8.4.4 google-public-dns-b.google.com (0/4)
[2017-05-13 00:05:21.173] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
[2017-05-13 00:17:02.290] NOTICE: pihole.log has been flushed
[2017-05-13 00:17:02.291] Resetting internal data structure
[2017-05-13 00:17:02.291] Queries in memory before flushing: 404
[2017-05-13 00:17:03.303] Gravity list entries: 105960
[2017-05-13 00:17:03.303] No blacklist present
[2017-05-13 00:17:03.304] No wildcard blocking list present
[2017-05-13 00:17:03.304] Warning: Reading of rotated log file /var/log/pihole.log.1 failed
[2017-05-13 00:17:03.305] Reading from /var/log/pihole.log (rwxrwxr-x)
[2017-05-13 00:17:03.305] Notice: Increasing queries struct size from 0 to 10000 (320.28 KB)
[2017-05-13 00:17:03.305] Notice: Increasing overTime struct size from 0 to 100 (323.48 KB)
[2017-05-13 00:17:03.306] Notice: Increasing domains struct size from 0 to 1000 (343.49 KB)
[2017-05-13 00:17:03.306] Notice: Increasing clients struct size from 0 to 10 (343.66 KB)
[2017-05-13 00:17:03.307] New client: 127.0.0.1 localhost (0/10)
[2017-05-13 00:17:03.354] Notice: Increasing forwarded struct size from 0 to 4 (343.75 KB)
[2017-05-13 00:17:03.562] New forward server: 8.8.4.4 google-public-dns-b.google.com (0/4)
[2017-05-13 00:17:03.812] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
[2017-05-13 06:58:27.399] Notice: Increasing queries struct size from 10000 to 20000 (664.34 KB)
[2017-05-13 11:24:18.746] dnsmasq process restarted
[2017-05-13 11:24:20.136] Gravity list entries: 105960
[2017-05-13 11:24:20.137] No blacklist present
[2017-05-13 11:24:20.137] No wildcard blocking list present
[2017-05-13 11:28:07.190] New client: 192.168.8.112 DietPi (1/10)

---= pihole.log

May 13 11:28:16 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:16 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:16 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:16 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:16 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:16 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:16 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:16 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:26 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:26 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:26 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:26 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:26 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:26 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:26 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:26 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:36 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:36 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:36 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:36 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:36 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:36 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:36 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:36 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:46 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:46 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:46 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:46 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:46 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:46 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:46 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:46 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:28:56 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:56 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:56 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:56 dnsmasq[7618]: forwarded emoncms.org to 8.8.4.4
May 13 11:28:56 dnsmasq[7618]: forwarded emoncms.org to 8.8.8.8
May 13 11:28:56 dnsmasq[7618]: reply emoncms.org is NODATA-IPv6
May 13 11:28:57 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:28:57 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:28:57 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:28:57 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:29:06 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:29:06 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:29:06 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:29:06 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6
May 13 11:29:07 dnsmasq[7618]: query[A] emoncms.org from 127.0.0.1
May 13 11:29:07 dnsmasq[7618]: cached emoncms.org is 80.243.190.58
May 13 11:29:07 dnsmasq[7618]: query[AAAA] emoncms.org from 127.0.0.1
May 13 11:29:07 dnsmasq[7618]: cached emoncms.org is NODATA-IPv6

Thanks!

2

What URL are you using to connect to the web interface? DietPi changes it from the default (if you installed it through their installer).

3

Today for some reason, I started receiving the message below when trying to connect to the pi-hole web interface via http://xxx.xxx.xxx.xxx/admin/index.php:

This site can’t be reached
The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET

Ad blocking still appears to be working, but the web interface doesn't work.

root@raspberrypi:/var/log# pihole status
::: DNS service is running
::: Pi-hole blocking is Enabled

root@raspberrypi:~# netstat -anp|grep -w LISTEN
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 446/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 672/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 479/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 636/sshd
tcp6 0 0 :::80 :::* LISTEN 672/lighttpd
tcp6 0 0 :::53 :::* LISTEN 479/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 636/sshd

Things I've tried:

  1. Rebooting
  2. Used Firefox instead of Chrome
  3. pihole -g (to update Gravity)
  4. pihole -up (to update Pi-hole)
  5. pihole -f (to flush logs)
  6. pihole restartdns
  7. sudo chown pi:pi /var/log/pihole-FTL.log
  8. pihole -r (to reconfigure)
  9. curl -sSL https://install.pi-hole.net | bash (to reinstall)
  10. pihole -d (to start debugging)

Any help would be greatly appreciated. I've uploaded my logs with this token: vhrs1k1lse

Thank you!

4

Should FTL be listening on port 4711?

root@raspberrypi:/var/log# netstat -anp|grep -w LISTEN
tcp 0 0 127.0.0.1:4711 0.0.0.0: LISTEN 439/pihole-FTL*
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 670/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 480/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 634/sshd
tcp6 0 0 :::80 :::* LISTEN 670/lighttpd
tcp6 0 0 :::53 :::* LISTEN 480/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 634/sshd

[2017-05-17 22:20:43.767] ########## FTL started! ##########
[2017-05-17 22:20:43.784] FTL branch: (no branch)
[2017-05-17 22:20:43.784] FTL hash: v2.7.3
[2017-05-17 22:20:43.784] FTL date: 2017-05-15 14:20:25 +0200
[2017-05-17 22:20:43.784] FTL user: pihole
[2017-05-17 22:20:43.790] Notice: Found no readable FTL config file
[2017-05-17 22:20:43.791] Using default settings
[2017-05-17 22:20:43.791] Starting config file parsing
[2017-05-17 22:20:43.791] SOCKET_LISTENING: only local
[2017-05-17 22:20:43.791] TIMEFRAME: Rolling 24h
[2017-05-17 22:20:43.791] QUERY_DISPLAY: Show queries
[2017-05-17 22:20:43.792] Finished config file parsing
[2017-05-17 22:20:43.802] Found no other running pihole-FTL process
[2017-05-17 22:20:43.805] PID of FTL process: 439
[2017-05-17 22:20:44.289] Gravity list entries: 106964
[2017-05-17 22:20:44.289] No blacklist present
[2017-05-17 22:20:44.290] Notice: Increasing wildcards struct size from 0 to 1 (92.00 B)
[2017-05-17 22:20:44.290] Wildcard blocking list entries: 1
[2017-05-17 22:20:44.290] Starting initial log file parsing
[2017-05-17 22:20:44.290] Warning: Reading of rotated log file /var/log/pihole.log.1 failed
[2017-05-17 22:20:44.290] Reading from /var/log/pihole.log (rw-r--r--)
[2017-05-17 22:20:44.293] Notice: Increasing queries struct size from 0 to 10000 (320.11 KB)
[2017-05-17 22:20:44.294] Notice: Increasing overTime struct size from 0 to 100 (323.31 KB)
[2017-05-17 22:20:44.294] Notice: Increasing forwarded struct size from 0 to 4 (323.38 KB)
[2017-05-17 22:20:50.631] New forward server: 199.85.127.10 (0/4)
[2017-05-17 22:20:50.631] Notice: Increasing domains struct size from 0 to 1000 (343.40 KB)
[2017-05-17 22:20:50.631] Notice: Increasing clients struct size from 0 to 10 (343.59 KB)
[2017-05-17 22:20:50.632] New client: 127.0.0.1 localhost (0/10)
[2017-05-17 22:20:50.662] New forward server: 199.85.126.10 (1/4)
[2017-05-17 22:20:50.669] New client: 10.0.0.77 (1/10)
[2017-05-17 22:20:50.676] New client: 10.0.0.104 (2/10)
[2017-05-17 22:20:50.681] New client: 10.0.0.105 (3/10)
[2017-05-17 22:20:50.683] Finished initial log file parsing
[2017-05-17 22:20:50.683] -> Total DNS queries: 34
[2017-05-17 22:20:50.683] -> Cached DNS queries: 2
[2017-05-17 22:20:50.683] -> Blocked DNS queries: 3
[2017-05-17 22:20:50.683] -> Unknown DNS queries: 0
[2017-05-17 22:20:50.683] -> Unique domains: 24
[2017-05-17 22:20:50.683] -> Unique clients: 4
[2017-05-17 22:20:50.684] Successfully accessed setupVars.conf
[2017-05-17 22:20:50.684] Listening on port 4711

5

I've now tried uninstalling and reinstalling pi-hole with the same result.

  1. pihole uninstall (removed all the dependencies except curl)
  2. curl -sSL https://install.pi-hole.net | bash
6

Yes, that's the correct port for FTL. Your debug log doesn't show anything amiss. Do you see any requests in /var/log/lighttpd/access.log that correspond to your requests? Try http://pi.hole/admin

7

When try to go to http://xxx..xxx.xxx.xxx/admin/index.php today I get:

This site can’t be reached

The webpage at http://10.0.0.15/admin/index.php might be temporarily down or it may have moved permanently to a new web address.
ERR_SOCKET_NOT_CONNECTED

or

This site can’t be reached

The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET

When try to go to http://pi.hole/admin, I get:

This site can’t be reached

pi.hole’s server DNS address could not be found.
Search Google for hole admin
ERR_NAME_NOT_RESOLVED

My /var/log/lighttpd/access.log file looks like this:

tail access.log
1495153791|widget-cdn.rpxnow.com|GET /load/login.foxnews.com HTTP/1.1|200|179
1495153791|widget-cdn.rpxnow.com|GET /load/login.foxnews.com HTTP/1.1|200|179
1495156464|10.0.0.15|GET /admin/index.php HTTP/1.1|200|15409
1495156472|10.0.0.15|GET /admin/index.php HTTP/1.1|200|15409
1495156476|10.0.0.15|GET /admin/index.php HTTP/1.1|200|15418
1495156478|10.0.0.15|GET /admin/index.php HTTP/1.1|200|7955
1495156484|10.0.0.15|GET /admin/index.php HTTP/1.1|200|15415
1495156588|pi.hole|GET /admin HTTP/1.1|301|0
1495156617|pi.hole|GET /admin HTTP/1.1|301|0
1495156726|10.0.0.15|GET /admin/index.php HTTP/1.1|200|7955

Yes, I've been to foxnews.com and a few other sites.

8

Try restarting the Pi-hole. Run pihole -d for another debug token. Then run curl -i http://pi.hole/admin/index.php and share the first 20 or so lines, if it outputs that much.

9

Token - ifnfby24zh

curl -i http://pi.hole/admin/index.php

HTTP/1.1 200 OK
X-Pi-hole: The Pi-hole Web interface is working!
X-Frame-Options: DENY
Set-Cookie: PHPSESSID=etm10lf0lpk1e3astgpn159tk4; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 19 May 2017 01:39:08 GMT
Server: lighttpd/1.4.35

Pi-hole Admin Console
10

That looks like it completed successfully. Was that run on the Pi-hole? If so, run it on a device now.

11

Yes, that was run on the Pihole itself when I was ssh'd into it.

If I run the commands from the terminal on my Linux Mint PC I get the following:
curl -i http://pi.hole/admin/index.php
curl: (56) Recv failure: Connection reset by peer
curl -i http://10.0.0.15/admin/index.php
curl: (56) Recv failure: Connection reset by peer

I've also cleared the cache in Google Chrome and Firefox and get the same results:

This site can’t be reached

The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET

12

Do you have some sort of firewall running?

13

Sorry, we've had a lot of storms in the Tulsa area recently. We lost power last night for an hour or more and lost Internet access for most of the day today. ;-(

Earlier today I was able to see the Pi-hole's page from a different computer on my network but now I can not access it from any computer. I don't know what's going on. I'll post when I find out more.

14

Sorry it's been so long, but I've discovered that my router/firewall, a TP-Link TL-R600VPN Ver. 2.0, seems to stop me from accessing the web page of the PiHole. I don't know why yet. However, if I reboot the TL-R600, the PiHole web interface is available for a little while and then becomes unavailable. The TP-Link is also the DHCP server for my network, so I wonder if some other device is stepping on the PiHole. I'm not sure yet, but that's what I'm seeing right now.

15

You could try temporarily using Pi-hole's DHCP server to see if it solves the issue. Then you will know for sure it is something on your router.

You could also try a traceroute pi.hole to see how the traffic is trying to reach the interface.

16

If your router is also sending out DHCPv6 info, then it could be causing the browser to not resolve pi.hole correctly via IPv6. Try nslookup pi.hole on your client to see if it resolves correctly.

17

Traceroute and nslookup to pi.hole and the IP address worked as expected. The DHCP address range did not conflict with the IP address of the PiHole. I also restored the router/firewall to defaults and the issue persisted. However, just the other day my issue stopped. We have not added or removed any hardware or made any changes that I'm aware of. I'm not sure what caused the issue or what resolved it. It just isn't happening now. :confused: