You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: