UNRAID 7.2.4

CA - Binhex-Official-Pihole

I have run into a issue that hopefully has a simple solution:

I recently installed the Official Pi-Hole App from Binhex off of the CA. I configured it with a custom network and a static IP of 192.168.1.5 that is not being used by any other device. I also assigned it PRIVILEGED access from the console shell command within the configuration settings.

Once the container pulled down all of the files and installed successfully I checked log and didn't have any issues or warnings. I then tried to launch the WebUI and got a blank page initially but then showed that the site can't be reached, that 192.168.1.5 took to long to respond. I have also tried to access the WebUI by manually typing in the IP address with the port i.e. (192.168.1.5:80/admin) and get the same result.

I have tried making changes to the network type in the container but get the same result or a complete failure to install.

Right now, I have Pi-Hole installed and running on UNRAID but can't access the WebUI from my computer, however, I can access the WebUI from my Android phone, manually typing in the IP address (192.168.1.5:80/admin). Accessing it from my phone takes me to the Pi-Hole WebUI where I can then sign in and start configuring the settings. I am fairly certain that this is a simple networking issue, hopefully...

Please help.

I have attached the Diagnostics Log for reference.

I am very new to networking and trying to learn as much as I can so please forgive me if I have overlooked something simple.

olivejuice-diagnostics-20260418-1217.zip

Edited April 18Apr 18 by Olivejuice
Amended

Additionally I can ping from the terminal in UNRAID (192.168.1.40) to my local machine (192.168.1.86), cloudflare (1.1.1.1), and google (8.8.8.8), but get Destination Host Unreachable when pinging Pi-Hole (192.168.1.5).

I can also ping my local machine, cloudflare, and google from the Pi-Hole terminal.

Additionally, I can ping to my UNRAID server (192.168.1.40), cloudflare, google, but but get Destination Host Unreachable when pinging Pi-Hole. (192.168.1.5)

Maybe these will help...?

I am very new to networking and trying to learn as much as I can so please forgive me if I have overlooked something simple.

Edited April 18Apr 18 by Olivejuice
Amended

I could be wrong, but based on your ping to 192.168.1.5 being "Reply from 192.168.1.40", it seems like your PC has a stale ARP cache entry for 192.168.1.5 causing packets to go to Unraid instead of Pi Hole. You can try running arp -d 192.168.1.5 to clear it and then try the browser again by typing in the IP.

9 minutes ago, CandleSir said:

I could be wrong, but based on your ping to 192.168.1.5 being "Reply from 192.168.1.40", it seems like your PC has a stale ARP cache entry for 192.168.1.5 causing packets to go to Unraid instead of Pi Hole. You can try running arp -d 192.168.1.5 to clear it and then try the browser again by typing in the IP.

Thank you for your reply and suggestion...

I tried running that command in both Powershell and the UNRAID terminal and still get the same result unfortunately... :(

Problem on docker network setting, there shouldn't only have wlan0 appear on docker.cfg, where br0, bond0 ?

Pls review docker network setting in docker config, try DOCKER_USER_NETWORKS="remove" and setting the ip, subnet, gateway ..... etc

DOCKER_CUSTOM_NETWORKS="wlan0 "

DOCKER_USER_NETWORKS="preserve"

Edited April 19Apr 19 by Vr2Io

Thank you for your response. As I mentioned before, I am new to networking and all of the innerworkings of it. I can usually fumble my way around but definitely can use precise directions.

4 hours ago, Vr2Io said:

Problem on docker network setting, there shouldn't only have wlan0 appear on docker.cfg, where br0, bond0 ?

Pls review docker network setting in docker config, try DOCKER_USER_NETWORKS="remove" and setting the ip, subnet, gateway ..... etc

So I was able to review the docker config file that you mentioned and saw that DOCKER_CUSTOM_NETWORKS="wlan0 " and that br0 and bond0 are not showing.

I was able to change the Preserve user defined networks to NO, which changed the docker config to DOCKER_USER_NETWORKS="remove".

I know how to change the IP and GATEWAY within the Network Settings but I don't know how to change the SUBNET. I originally set my UNRAID server with a static IP of 192.168.1.40 when setting up my server and this hasn't ever changed. Why would I want to change these settings manually? Are they not already set to the correct addresses?

Please give me more directions and or something else to try to resolve my issue as it remains.

I will say that I disabled docker, stopped my array, and rebooted my server and I still can't access Pi-Hole from my local machine but CAN access it from my phone.

4 hours ago, Vr2Io said:

DOCKER_CUSTOM_NETWORKS="wlan0 "

DOCKER_USER_NETWORKS="preserve"

I attached the latest diagnostics file for reference. As you can see the settings that you mentioned have changed accordingly...

I don't know how to change the DOCKER_CUSTOM_NETWORKS to include br0 and bond0, please advise.

Thank you again for any and all advice!!

olivejuice-diagnostics-20260419-0856.zip

4 hours ago, Olivejuice said:

I will say that I disabled dockerI still can't access Pi-Hole from my local machine but CAN access it from my phone.

If orher physical device (phone) can access Pihole, then no reason oher physical device can't access as all in same subnet 192.168.1.X.

Does Windows setting in dhcp or static ？You setup Unraid in subnet in /24 255.255.255.0, does same netmak also match in Windows ？pls check in Windows by typing “ipconfig". Are you use one router only ？Windows and Unraid are connect in same router or switch ？

4 hours ago, Olivejuice said:

don't know how to change the DOCKER_CUSTOM_NETWORKS to include br0 and bond0, please advise.

I can't reproduce this, and now this shouldn't the cause, pls forget in this moment.

EDIT : Are you already tick br0 and bond0 when start docker service ？I am not at home, I would screen capture for better understanding.

For Unraid can't ping pihole is normal because both in same host subnet. If you want overcome this, pls enable ”host access" in docker setting.

Edited April 19Apr 19 by Vr2Io

Mention again, if phone can access Pihole, but Windows can't access then it suppose it is physical network issue.

During test, I found docker.cfg won't show expected parameter even I clearup docker.cfg, so pls ignore docker.cfg.

when I check my docker.cfg, it fill with previous dirty data.

Even cleanup, it still wrongly show custom_networks was br1

ANYWAY, does GUI show br0 in use actually ?

5 hours ago, Vr2Io said:

ANYWAY, does GUI show br0 in use actually ?

Yes, the GUI shows that the custom network is on br0....

I just want to say that I appreciate your help and the time that you are taking to try and help me resolve this issue...

On a side note, couple of other things that I tried but were unsuccessful....

Using different browsers and manually entering (192.168.1.5:80/admin) which also has not worked.

Eliminating the network switch and connecting to my router directly.

Edited April 20Apr 20 by Olivejuice

While I was writing the last response I decided that I would try yet a different local machine, Lenovo Yoga Laptop(192.168.1.25) on my same WIRED LAN and this one connects to the Pi-Hole WebUI, allowing me to login.

I tried yet another local machine, HP Envy (192.168.1.84) on the same LAN, this time wireless, and this one connects to the Pi-Hole WebUI as well.

So what I have concluded is that the local machine that I use regularly for everyday use and to access my UNRAID server for maintenance, Lenovo Optiplex (192.168.1.34) is having an issue connecting to the Pi-Hole IP and port, (192.168.1.5:80/admin), while all other machines, wired or wireless, can connect without any issue.

OK, now that I have isolated the issue to this specific machine, how can I trouble shoot it and resolve whatever is blocking the connection?

Thank you!

EDIT: So that lasted until I refreshed the webpage on the local machine that was working, Lenovo Yoga Laptop(192.168.1.25). Now I can't access it...

Edited April 20Apr 20 by Olivejuice

14 minutes ago, Olivejuice said:

how can I trouble shoot it and resolve whatever is blocking the connection?

Pls check Windows firewall or any antivirus utility cause problem.

Edited April 20Apr 20 by Vr2Io

Have a look in your router firewall settings too. There could be a deny rule blocking traffic from your workstation mac or ip. If your workstation is set to a static IP, try setting it to DHCP. If it works on a new IP address then you know something is stinkered up in your routing rules.

1 hour ago, Veah said:

Have a look in your router firewall settings too. There could be a deny rule blocking traffic from your workstation mac or ip. If your workstation is set to a static IP, try setting it to DHCP. If it works on a new IP address then you know something is stinkered up in your routing rules.

I looked into the router settings, looking for any traffic that is being blocked and wasn't able to find anything that caught my attention. I also went into DHCP reservation and released each static IP I had assigned. As I was going through each of my IP assigned devices and refreshing the webpage for my Netgear router, I noticed that at one point ALL devices connected to my network showed up as being a wired connection which couldn't be possible as most devices are wireless!

At this point I knew that there was something wonky going on with my router and thus I factory reset it. I configured my router as it was previously leaving everything to DHCP. Then I systematically connected all of my wired devices and let my router assign IP addresses. Once my UNRAID server was back up and running, I thought I'd check the Pi-Hole WebUI once again. VIOLA!!!! I could access the WebUI from ALL of my devices. I then started to re-assigned static IP addresses to the devices that had static IP's before and now everything is working as it should....What a pain in the ass!

HOW FRUSTRATING!!!!! I never thought that the router was the issue because everything seemed to be connecting and communicating as it should, or so I thought. Live and learn and not all things are as they seem.

I want to say thank you to each of you that provided input along the way to help me troubleshoot this issue. Thank you, thank you, thank you! This UNRAID community is such a tremendous help. As I grow and learn this system and all of the things associated with it, no matter how frustrating, I will definitely contribute to helping others along the way!