Web Interface Inaccessible from Desktop PC

Help
1

Expected Behaviour:

I want to be able to access the web interface through my desktop PC using pi.hole/admin.

Actual Behaviour:

The page times out in Firefox, IE, and Edge when trying to access pi.hole/admin or piholeip/admin. On my smartphone and laptop, I'm able to reach it through pi.hole/admin.

Debug Token:

https://tricorder.pi-hole.net/r61a66rdmh

I'm using a WR841N router flashed to DD-WRT. I can see that PiHole is working as a DNS resolver by looking at the logs on my phone. I thought this was possibly the issue. Apparently, older versions of DD-WRT have an issue with ethernet ports. This did not help, and now I'm having to set the DNS for my PC in the network adapter properties or I get a weird Windows could not detect proxy settings error. Other devices work, but now I have to set another DNS at adapter level for my desktop PC.

curl -I pi.hole from my PC produces:
PC>curl -I 192.168.1.102
curl: (7) Failed to connect to 192.168.1.102 port 80: Timed out

PC>curl -I pi.hole
curl: (6) Could not resolve host: pi.hole

From the Pi:
HTTP/1.1 200 OK
X-Pi-hole: The Pi-hole Web interface is working!
X-Frame-Options: DENY
Set-Cookie: PHPSESSID=9504iju70ih66dc2cq1uj6hke1; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Content-type: text/html; charset=UTF-8
Date: Wed, 24 Jul 2019 05:48:29 GMT
Server: lighttpd/1.4.45

Edit: I got it working. The problem was with DD-WRT.

Solution was in running some commands on my router. Issue for DD-WRT on some routers where ethernet devices have issues communicating to wireless?
swconfig dev switch0 set reset 1
swconfig dev switch0 set enable_vlan 1

2

Pi-hole is not a proxy.

You should be setting it as a DNS server in either your router settings OR manually in the network settings of each device.

Your setup as you've described it would be expected to fail as windows can't resolve pi.hole unless the Pi-hole is your DNS server

3

I wrote that incorrectly. It was set as the DNS in the network adapter settings. I'm still unable to access the web interface from my desktop PC.

4

From the desktop PC, what are the outputs of the following commands from the PC terminal:

nslookup pi.hole

ipconfig /all

5

nslookup pi.hole
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.102

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : i36300
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.tx.comcast.net

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-06
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f1ca:b093:668f:6009%6(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.96.9(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 403308583
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-1D-01-C8-4C-CC-6A-6B-69-FA
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : hsd1.tx.comcast.net
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 4C-CC-6A-6B-69-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::35d7:d715:9047:6b7f%7(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.112(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, July 24, 2019 5:53:55 PM
Lease Expires . . . . . . . . . . : Thursday, July 25, 2019 6:04:41 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 72141930
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-1D-01-C8-4C-CC-6A-6B-69-FA
DNS Servers . . . . . . . . . . . : 192.168.1.102
NetBIOS over Tcpip. . . . . . . . : Enabled

On the desktop PC, the internet doesn't work at all when its DNS server is set 192.168.1.102. I thought it was earlier, but I must not have had the DNS set to the pihole.

So it appears my desktop PC can't see the pihole, but other devices on the network can.

Edit: I am able to SSH and ping the pihole from the desktop. Although ping only works with the name of the device, not the IP address.

6

I agree that is the case. Since other devices can communicate with Pi-Hole for DNS, this makes it a configuration problem on that PC. I would go to some of the Windows forums and see if there is a solution there.

Your debug log shows that Pi-Hole is working normally.

7

Okay, I'll try there too.

8

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