Closed xanoni closed 2 years ago
I actually have no idea how that config is supposed to work - I've never used it myself - but there is nothing inside the pihole/pihole
container listening for https
requests.
I think we're probably better off deleting this file - unless someone can explain to me how it works.
there is nothing inside the
pihole/pihole
container listening forhttps
requests.
Ha I noticed that too but assumed docker-compose was doing some magic to have it connect anyway ....
What is the least painful way to make it work with HTTPS? I run one in a WiFi network that I don't fully trust.
I've just found this statement here from @PromoFaux
https://github.com/pi-hole/docker-pi-hole/issues/755#issuecomment-835774149
Official stance:
There is no need to expose the Pi-hole web interface to the public internet.
If you do need to access it remotely - use a VPN.
However, this assumes that the local network can be fully trusted. That's an assumption that I don't want to make, thus HTTPS would be useful.
Why not make it the default? Too much overhead?
For what it's worth, I just set the Pi-hole up as a Tor hidden service and that was super painless... just had to add the 2 lines (+ client auth) to torrc
and change the VIRTUAL_HOST
and VIRTUAL_PORT
variables in docker_compose.yml
to the .onion
domain.
It's obviously not super performant, but probably the safest way to access it remotely. Doesn't solve my local network concerns, though, unless I want to use Tor also locally (which is a possibility ... it's not THAT bad).
Is it possible to define more than one VIRTUAL_HOST
/ VIRTUAL_PORT
?
You could try this, obviously you'll need to do some volume/file mounting for /var/lighttpd/external.conf
https://discourse.pi-hole.net/t/enabling-https-for-your-pi-hole-web-interface/5771
Keep in mind this isn't an "official" guide, and we can't guarantee it will always be compatible (e.g version 6.0 will remove lighttpd
as the web server)
Thank you @PromoFaux ... I haven't gotten to it yet but it's on the TODO list ... will report back once I get to it.
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.
This is a: Run Issue
Details
I'm trying to expose the web interface via HTTPS by running "docker-compose-nginx-proxy.yml" instead of the "docker-compose.yml.example".
Unfortunately that doesn't work, I can only connect to Port 80. Is any extra configuration required beyond what's mentioned in the .yml?
Related Issues
How to reproduce the issue
Environment data
docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
These common fixes didn't work for my issue
docker run
example(s) in the readme (removing any customizations I added)If the above debugging / fixes revealed any new information note it here. Add any other debugging steps you've taken or theories on root cause that may help.