Cannot access admin page from second access point

Help
1

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

When connected to either wifi access points, I should be able to access the admin page

Actual Behaviour:

I have to be connected to the access point that the physical pi is closest to in order to access the admin page.

My network is as follows:

All IPs are 192.168.2.xxx

[Router/AP1] ---> powerline adatper --------> powerline adapter/AP2 ---> client
    | 
    ------> PIHole

If I have my client connect to AP2, it cannot access admin page (in this case 192.168.2.252/admin)
If I connect my client to AP1, it can access the admin page (in this case 192.168.2.252/admin)

when my client is connected to AP2 I can successfully ping the pi, as well as ssh into it without any issues. I can also access the router's internal web admin without any issues. PiHole servers out DHCP address without any issue, and blocks blacklisted sites.

I just can't access the admin page from AP2, and have to connect to AP1. Which I think is strange.

If I connect the pi to AP2, my client, when connected to AP2 can see the admin site, but not when my client is connected to AP1.

Debug Token:

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

2

When you say you cannot access the admin page, what exact error do you get?

You mention that the Pi-hole is serving DHCP. What happens if you use the address http://pi.hole/admin instead of the IP address, from both APs?

Try the command below to see exactly what is fetched, using the client on both APs. No need to post the output – just inspect the first few lines and see if they are as below or something different:

curl -s http://192.168.2.252/admin/login.php

output:

<!DOCTYPE html>
<!--
*  Pi-hole: A black hole for Internet advertisements
[... rest of page ...]
3

If you cannot access your Pi-hole by IP, then Pi-hole's DNS service isn't involved.

Does that observation apply to all devices alike, or just to the roaming client that connects through either your router's or your powerline's AP at times?

4

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