Cannot get to the config page of pihole on mikrotik

RouterOS Beginner Basics
1

Hi
I have followed all steps in the following link [https://help.mikrotik.com/docs/display/ROS/Container] to setup the pihole on mikrotik.
It is running but I cannot get to the config page. Instead, I am getting the place holder page
1414.png
What am I doing wrong? The container is running with no issue.
Here is my configuration

/system/device-mode/print
     mode: enterprise
container: yes

/container mounts
add dst=/etc/dnsmasq.d name=pihole_dnsmasq src=/usb1/etc-dnsmasq.d
add dst=/etc/pihole name=pihole_etc src=/usb1/etc

/container
add envlist=pihole_envs interface=veth-docker logging=yes mounts=pihole_dnsmasq,pihole_etc root-dir=usb1/pihole start-on-boot=yes

/container config
set registry-url=https://registry-1.docker.io tmpdir=usb1/pull

/container envs
add key=TZ name=pihole_envs value=America/Vancouver
add key=WEBPASSWORD name=pihole_envs value=***********
add key=DNSMASQ_USER name=pihole_envs value=root

/interface veth
add address=172.16.15.253/24 gateway=172.16.15.254 gateway6="" name=veth-docker

/ip address
add address=172.16.15.254/24 interface=bridge-dockers network=172.16.15.0

/interface bridge port
add bridge=bridge-dockers interface=veth-docker

/ip firewall nat
add action=masquerade chain=srcnat log=yes log-prefix=scr-nat-172- src-address=172.16.15.0/24
add action=dst-nat chain=dstnat dst-address=192.168.10.254 dst-port=4488 log=yes log-prefix=dk-dnat- protocol=tcp to-addresses=172.16.15.253 \
    to-ports=80

/interface bridge
add name=bridge-dockers

/interface bridge port
add bridge=bridge-dockers interface=veth-docker


0 name="ea70fe15-c52c-4633-b2c0-0956505e8991" tag="pihole/pihole:latest" os="linux" arch="arm" interface=veth-docker envlist="pihole_envs" 
   root-dir=usb1/pihole mounts=pihole_dnsmasq,pihole_etc dns="" logging=yes start-on-boot=yes status=running
2

This is in the PiHole documentation. Please read it. You need to add /admin/ to the end of the URL

https://discourse.pi-hole.net/t/placeholder-page-docker/60498/2

3

Thank you very much.

I think updating the document with that instruction would be a great help. I understanding adding that to the video on youtube might be difficult but to the Mikrotik doc should be easy enough.

4

You do realize that container images them selves are not Mikrotik’s business, right? Anything you place inside container image is on you, you have to find relevant documentation (possibly on container package maintainer’s site). Mikrotik only makes possible to run container images and that’s where their responsibility ends.

5

I do understand that. However, when users follow the official doc and at the end the cofiguration is not working, it can get frustrating. A one liner in the doc would have saved the frustration.
We can go on and on about reading docs, but I hope the point is clear.
Thank you all.

6

If the admin URL entry was consistent across all containers then I concur it should be noted, but if its solely pi-hole centric, for you to expect MT to put tailor made solutions in their docs, for your particular scenario is a stretch.

7

In the MT official doc, pihole container is only mentioned as an example of how to build a container. It doesn’t touch the workings of the container contents at all … so I don’t see why should official MT doc detail about how in particular pihole app inside container should be used.
A line has to be drawn somewhere and IMO it’s just fine where it’s drawn now. Or would you rather not see any example of how a container can be built on ROS?

8

Adding another argument why it should NOT be mentioned:
if for one reason or the other pihole decides to change that admin entry … MT (and everyone else referencing PiHole) should adapt their documentation as well ?
I don’t think so.

MT stuff stays with MT.
PH stuff stays with PH

9

Well both sides are correct.
We don’t want to update every time PiHole changes their stuff.
But on the other hand, we do have special instructions for PiHole in the doc. So we added /admin/

10

Tx Normis!!