PIHOLE admin interface not accessable on Local LAN

Help docker
1

Hi

Pi-Hole running on CentOs9.0 as VM in VMware Workstation, and it is fresh installation, Pfsense server is between pi-hole and ISP Modem(Internet)

I can access pihole admin interface via locally

http:/pi.hole/admin
http://pi.hole/
http://127.0.0.1/admin

but I can't access:
http://<IP_ADDPRESS_OF_PI-HOLE_SERVER>/admin/ from another device or computer on my local LAN using any of the methods above (obviously 127.0.0.1 won't work by design).

In Network Overview all local IPs are blocked : Uses pi-hole it show X symbol.

Your debug token is: https://tricorder.pi-hole.net/PumMnDPY/

Any ideas please?

Thanks

DINU

2

The firewall service on your CentOS server is active and is blocking http and dns.

*** [ DIAGNOSING ]: FirewallD
[i] Firewalld service active
[✗]   Allow Service: http (https://docs.pi-hole.net/main/prerequisites/#firewalld)
[✗]   Allow Service: dns (https://docs.pi-hole.net/main/prerequisites/#firewalld)
[✓]   Allow Service: dhcp
[✓]   Allow Service: dhcpv6

I'm not sure how this service works but I suspect it means that http and dns are available on the host itself, but not accessile to other machines on the network. This is consistent with the behaviour you're seeing. Try stopping the firewall service, at least temporarily, to see if this makes it available.

1 Like
3

After disabling firewall in centos now I can able to access admin and DNS from LAN network.
Let me check and add the new rule to my LAN and DMZ VLAN's

Thanks,
Dinu

4

I have disabled the CentOS firewall permanently, I can see admin webconsole and DNS works, but still my local(LAN) request from servers are getting blocks attached screenshot, any other issue to be there ?

pi-hole
pi-hole1260×805 200 KB

Your debug token is: https://tricorder.pi-hole.net/tAqqTNEk/

Regards,
Dinu

5

How do know these are being blocked? Is this shown in firewall or other similar logs?

Another possibility is that these clients aren't using Pi-hole for DNS. They may have another assignment.

6

The information on this table doesn't mean Pi-hole is blocking these clients.
This only means these clients never sent a query to Pi-hole.

The most likely possibility has already been described by jfb: maybe these clients aren't using Pi-hole for DNS. (This is normal for some devices. Example: my router doesn't use Pi-hole, but it shows up on the network table).

To be sure, inside the VM what is the output of nslookup flurry.com?

7

Yes, The IP(System) showing X mark is not configured with pi-hole DNS, I have changed the DNS and it is working now.

Thanks Again !
Dinu