@AnHero I have no idea.  At this point, I would verify that your pihole webserver is actually running inside the container but that's outside the scope of this template.

Also, just to clarify, the WebUI: setting should be http://[IP]:[PORT:80]/admin and your HTTP: setting should be 80.  Also, ensure you are going to /admin.  Pihole does not offer a website on JUST the ip address.  The /admin at the end is required.  Example http://192.168.0.18/admin would work if that is still your address.  http://192.168.0.18 would not and would give you a 403 access denied.

 

Without knowing more about your settings or what error message you are actually getting, I don't know how to help you.

 

 

@pmacdonald See this post for a breakdown on making sure your containers receive an IPV6 address.  However, this is just the Unraid side.  Your router would have to be properly setup as well.

@EksistenzeCan confirm it's running, on a whim I tried connecting via mobile and was able to log in for the first time on this install. When I try to connect via my PC I get this:

Strange.

@AnHero  Very odd.  The fact that you are able to log in on mobile implies that there is something going on with your computer.  What I would do is clear your cookies and cache data and try it again.  You browser may be holding on to old information so it's looking for something from that ip that it's not getting.  Maybe also try from a different browser in private mode.

 

Other than that, I got nothing.

Quick question.

I set up Pihole with a custom br0 fixed IP address. I have a TP link Omada network setup, and in my Omada Controller my servers IP address has changed to the Pihole containers IP address and I can't access the Unraid GUI from the local IP address anymore. My server and laptop are on two different VLANs. I was able to access before setting up Pihole. Any settings in Unraid I have to change?

Docker does not support using DHCP to request network settings. br0 sets a fixed IP address but that IP address just exists inside your Unraid box and there is always a possibility that your router will assign that address to something else. It is recommended that you assign a static address on the router side.

I have no idea what TP Link might be doing. Perhaps it detected the Pi Hole address coming from your Unraid network MAC and figured that the IP address should change.

You may want to look into the MACVLAN network driver for Unraid and see if there is something there.

Regardless, this is obviously not desired behavior but there is nothing you can do with the container itself to change or fix it. The problem lies outside.

Any chance of getting ssh client added to this docker? I wanted to try and set 2 pihole instances with HA scripts but this isn't possible if I can't SSH out of the docker container to the other pihole instance.

13 minutes ago, allanp81 said:

Any chance of getting ssh client added to this docker? I wanted to try and set 2 pihole instances with HA scripts but this isn't possible if I can't SSH out of the docker container to the other pihole instance.

Look into Docker mods and Docker mod install open SSH server.

There's no reason to add additional packaging where additional packaging is not needed

I don't need the server, just the client. I can SSH into the container by enabling tailscale SSH but can't SSH out of the container to my other physical device running pihole.

23 minutes ago, allanp81 said:

I don't need the server, just the client. I can SSH into the container by enabling tailscale SSH but can't SSH out of the container to my other physical device running pihole.

You want an SSH client inside the docker container so you can access another physical device on your network?

If that is what you are getting at, you are way outside the scope of this. This is just a template for the mpgirro/docker-pihole-unbound container. If you would like them to add that, I suggest opening an issue on the github repository. Alternatively, you can fork it and add it yourself.

My personal view is that there are better ways of accomplishing what you are trying to do.

What are the better ways you can think of?

I'm still not sure exactly what you are trying to do, but there is a PuTTY app on the Community Apps. I mirror @bmartino1 . I hate cramming more things into a docker container than I need. Like'em LEEEEEAN.

Also, ssh has this functionality built in with ProxyCommand and ProxyJump. I'm not sure how that would work with Tailscale (or in general) but you could look into that.

I would just like to be able to ssh from this docker to another device on my network.

Edited January 17Jan 17 by allanp81

On 1/17/2026 at 4:46 PM, allanp81 said:

I would just like to be able to ssh from this docker to another device on my network.

extra parameters

as:

-e DOCKER_MODS=linuxserver/mods:openssh-server

this will ass ssh to the docker you will still need to console in and map the /etc/ssh/sshd_config and edit eh config to set ssh users and etc for ssh... adding things to arealy built dockers and using 3rd party software is on you...

Hoping someone can point me in the right direction here. For some context:

• I am using this container as the DNS on my own network

• I use Tailscale on my network

• When I want to use a commercial VPN for privacy purposes, I use an exit node configured to use the VPN in tailscale

I'm trying to find a way to use my pi hole as my DNS while using one of my VPN exit nodes (this I know how to do), but without defeating the entire purpose and leaking my IP via DNS queries (this I don't know how to do). It seems like theoretically what I need is to route my unbound queries through a VPN, but I'm not sure how to accomplish that (or any alternative). Anyone have any tips?