Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ServerIP - pihole #34

Open
ghost opened this issue Jun 19, 2021 · 3 comments
Open

ServerIP - pihole #34

ghost opened this issue Jun 19, 2021 · 3 comments

Comments

@ghost
Copy link

ghost commented Jun 19, 2021

why does the docker compose file set the ServerIP environment variable in the pihole configuration to 10.1.0.100 (ServerIP: 10.1.0.100 # Internal IP of pihole, line 67)? Shouldn't this value be set to 10.2.0.100? Also can you explain the purpose of this variable? The official pi-hole documentation on this subject is lacking at best and the default value they use is 127.0.0.1 (pi-hole itself). under what circumstances would you not point directly back to pi-hole? I am having a very difficult time coming up with a plausible reason for using 10.1.0.100 ... Thank you

@Robin-Sch
Copy link

You found the answer?

@ghost
Copy link
Author

ghost commented Jul 22, 2021

no I still do not understand this. I was hoping the author of the docker-compose file would provide some insight

@wizzomafizzo
Copy link

This is the IP that the pihole web server for the UI will listen on. Setting it to 10.1 means wireguard clients will be able to access it. Setting it to 10.2 would mean only clients in the compose private network can access it which would be useless. It's not even necessary to set unless you specifically want to only allow VPN clients to manage the DNS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants