Lighttpd admin interface - listen on vpn subnet

Help docker
1

I have had docker pihole running well, and one of the changes I made at some point was to access the web-gui when connected to my vpn on 10.x.x.x/24. I don't remember how I set this up.

I decided to update the container using instructions here:
https://github.com/pi-hole/docker-pi-hole#upgrading-persistence-and-customizations

and now I can't get to the pihole web-gui through the VPN. I'm on the road for a few days so I don't have access via the local subnet.

I've tried "docker cp CONTAINTER:/etc/lighttpd/lighttpd.conf ."

edit lighttpd.conf to add
"server.bind 10.0.0.5/24"
docker cp lighttpd.conf CONTAINER:/etc/lighttpd

then restarting the container, but then when I grep that file through the container bash the server.bind directive isn't there.

What am I screwing up?
Is there a better way to get lighttpd inside the container to listen on my VPN subnet through the command line?

2

I've realized that when I restart the container, it wipes the edit I made to lighttpd.conf.

So instead, after adding the "server.bind" directive and copying back to the container, I've tried:

docker exec -it CONTAINER service lighttpd stop
docker exec -it CONTAINER service lighttpd start

and that doesn't seem to work either.

Pihole itself is working fine through the VPN, I just can't get to the GUI.

3

Just adjust Pi-hole's Interface settings at Settings | DNS:
Switch to Respond only on interface xxxx.
To the same effect, you can set Pi-hole's advanced Docker environment variable DNSMASQ_LISTENING to single for your Pi-hole container, in conjunction with a respective INTERFACE.

If you employed one of Docker's bridge network modes, you should use Permit all origins (all) instead.

4

OK - to be clear the pihole ad-blocking server is working fine thru the VPN (I do have it set to permit all origins).

My issue is I broke access to the web-gui and want to get it back while I'm on my trip (thru the VPN).

http(s)://10.0.0.5/admin doesn't respond thru the VPN - which makes me think it's a lighttpd setting.