Setting up Pi-Hole on Docker for the first time - cannot access admin

I've installed Pi-Hole via UnRaid Docker and it appears to have started ok in 'Host' mode, but i cannot get to the admin page..

Expected Behaviour:

Visit pi.hole/admin or 192.168.1.13/admin and see pi-hole admin page

Actual Behaviour:

404 Page not found - nginx

Debug Token:

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

Any help greatly appreciated, im sick of adverts (on my tv mainly) and hoping i can get this running!

@Cobai If your Pi-Hole Docker container on Unraid (running on your Raspberry Pi) is set to Host mode, that’s generally the best choice for Pi-Hole to correctly intercept DNS requests. But if you can’t get to the admin page, there are a few common areas to check that should get you sorted.

First, double-check the port binding — in Host mode, Docker uses the host’s ports directly, so make sure nothing else is occupying port 80 or 443 on the Pi. You can SSH into the Raspberry Pi and run netstat -tuln | grep :80 to check what’s listening. If something else is on port 80 (like another Docker container or a web server), that’s your conflict.

Also, try accessing the admin page directly via IP — something like http://<raspberrypi_ip>/admin. If that fails, confirm that the container is actually running: in Unraid's Docker tab, make sure it shows as "up", and open the container's logs to look for any errors.

If port conflicts are the problem and you're set on using Host mode, you might want to temporarily stop other containers or services that could be binding to :80. Alternatively, you can reconfigure the Pi-Hole container to run in Bridge mode and map custom ports like 8080:80, then access it via http://<raspberrypi_ip>:8080/admin.

Please share your docker compose or docker run script for your Pi-hole container.

It seems you are running nginx as webserver, which would fight over ports 80 and 443 with Pi-hole's embedded webserver.

Since you run your Pi-hole container in Docker's host network mode, you can't simply remap ports.

Instead, you should set your Pi-hole container's FTLCONF_webserver_port environment variable.

That's webserver.port in Pi-hole's UI, as accessible via Settings | All settings » Webserver and API.

For a quick start, try adjusting

FTLCONF_webserver_port: '8080,8443os,[::]:8080,[::]:8443os'

For comprehensive usage details, see the UI comments.

I've got no idea what else could be using the port.
All my other Dockers appear to use other ports so i can't see a visible conflict.

I can't access the /admin page to make any changes to this settings - is there a way to add it as a variable to the docker image manually?

Sure, as mentioned:

Sorry, i'm still fairly new when it comes to manually amending Docker images, i see this but have no idea what each bit is supposed to contain to get Docker to apply this change:

Your screenshot shows neither a docker compose nor a docker run script, but some third-party administrative UI for Docker.

You'd have to consult that tool's documentation and figure how to create an environment variable for your Pi-hole container (the equivalent of using -e FTLCONF_webserver_port: '8080,8443os,[::]:8080,[::]:8443os' with docker run).

If that's what the screenshot is about, it may be correct, though I'd guess that you'd also need to populate Key: the same as Name:.

Oh sorry its Docker on UnRaid that's probably why.
I can't figure it out at the moment, nothing i try works and nothing resolves, errors about this in the log:

Error starting userland proxy: listen udp4 0.0.0.0:68: bind: address already in use.

This is above my pay grade now :\

I never used Unraid, so this is just a guess, but I think the Name: field is just a description of the variable (a comment).

I think you need to use the pair Key: and Value: to actually set the variable.

Also, try with ('8080,8443os,[::]:8080,[::]:8443os') and without (8080,8443os,[::]:8080,[::]:8443os) quotes around the value.

Whoa!
Ok so this got me to the Webui for anyone else who stumbles upon this post:

I'll try playing with Pi-Hole properly now and hoepfully get it working on my network, exciting ad-free times :smiley:

Thank you all for your help!!

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