ServerIP still required? #956

scara · 2021-12-27T13:58:15Z

Hello Everyone,
it looks like ServerIP is still required, regardless the improvement in #944, documented in https://github.com/pi-hole/docker-pi-hole/tree/3f97e6e4fc37cb7077f336cfa6a048105c0e6867#recommended-variables.
These are the logs when starting the new docker image:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying...
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing...
 ::: Starting docker specific checks & setup for docker pihole/pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
Applying pihole-FTL.conf setting REPLY_ADDR4=***.***.***.***
Setting DNS servers based on PIHOLE_DNS_ variable
::: Pre existing WEBPASSWORD found
  [✓] Setting admin contact to *********@********
DNSMasq binding to default interface: eth0
Added ENV to php:
                        "PIHOLE_DOCKER_TAG" => "2021.12.1",
                        "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
                        "ServerIP" => "0.0.0.0",
                        "CORS_HOSTS" => "",
                        "VIRTUAL_HOST" => "********.********.home",
Using IPv4
...

This is a: Bug

Details

I assume ServerIP to be no more required but logs mention it so either it is still required i.e. not deprecated or logs should be fixed.

Related Issues

I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

Run the latest 2021.12.1 image - it's there since 2021-11
Replace ServerIP with FTLCONF_REPLY_ADDR4, in the docker-compose you're running fine on 2021.10.1

These common fixes didn't work for my issue

I have tried removing/destroying my container, and re-creating a new container
I have tried fresh volume data by backing up and moving/removing the old volume data
I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
I have tried running without my volume data mounts to eliminate volumes as the cause

The text was updated successfully, but these errors were encountered:

dschaper · 2021-12-27T13:59:44Z

I don't think I understand. Can you explain a bit more about what is broken or not working?

scara · 2021-12-27T14:15:23Z

Hi @dschaper,
nothing is broken in terms of features but ServerIP is no more set as an ENV VAR by me but by the existing Dockerfile.

Being new to pi-hole code, at first glance it could be just a matter of fixing what written by logs by adding/removing relevant ENV VARs, at least adding FTLCONF_REPLY_ADDR4 too:

docker-pi-hole/bash_functions.sh

Line 220 in 523762e

    
           grep -E '(VIRTUAL_HOST|CORS_HOSTS|ServerIP|PHP_ERROR_LOG|PIHOLE_DOCKER_TAG)' "$PHP_ENV_CONFIG"

.

But... there are other places which look at ServerIP e.g.

docker-pi-hole/bash_functions.sh

Line 49 in 523762e

validate_env() {

.
I feel that a cleanup should be required to remove the usage of ServerIP in several places, including tests:

docker-pi-hole/bash_functions.sh

Line 49 in 523762e

validate_env() {
docker-pi-hole/docker_run.sh

Line 21 in b0a5a0f

-e ServerIP="127.0.0.1" \
docker-pi-hole/Dockerfile

Line 39 in 523762e

ENV ServerIP 0.0.0.0
docker-pi-hole/test/test_start.py

Line 11 in 20cd9c3

''' When args to docker are empty start.sh exits saying ServerIP is required '''
docker-pi-hole/test/test_bash_functions.py

Line 160 in 6c3ccfc

'"ServerIP" => "127.0.0.1"',
docker-pi-hole/docker-compose-nginx-proxy.yml

Line 33 in b0a5a0f

ServerIP: 192.168.41.55

docker-pi-hole/README.md

Line 121 in b0a5a0f

    
           | `VIRTUAL_HOST` | `$ServerIP` | `<Custom Hostname>` | What your web server 'virtual host' is, accessing admin through this Hostname/IP allows you to make changes to the whitelist / blacklists in addition to the default 'http://pi.hole/admin/' address

while keeping it for backward compat in:

docker-pi-hole/start.sh

Line 80 in 4aaf099

[ -n "${ServerIP}" ] && changeFTLsetting "REPLY_ADDR4" "$ServerIP"

Kind of two separate issues: this one to cleanup the logs and another one to actually deprecate ServerIP*.

HTH,
Matteo

PromoFaux · 2021-12-28T21:53:03Z

Hiya, thanks for opening this issue. I made a similar note about this in a review comment for the PR that added the new FTLCONF_ variable. #944 (comment)

I feel that a cleanup should be required

Absolutely agree here! I filed it under "At some point in the future, I'll have the time and energy to sit down and untangle this from the repo" - and am yet to find the time or energy for 😏

github-actions · 2022-01-27T22:02:46Z

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.

scara · 2022-01-28T10:08:14Z

Hi bot!

Based on #956 (comment) I think this could be the issue useful to track the vision of @PromoFaux .

HTH,
Matteo

PromoFaux · 2022-01-28T10:14:20Z

Gosh, has it been a month already?

I've added the Help Wanted label just in case anyone else would like to dip their toes into the repo, too (and never-stale to stop the bot from marking it stale!)

pralor-bot · 2022-02-03T08:52:26Z

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pihole-freezing-randomly-apparently/53200/7

pralor-bot · 2022-02-03T09:49:24Z

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/local-dns-records-not-resolved-on-mobile-devices/53272/5

pralor-bot · 2022-02-09T16:40:45Z

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pihole-not-resolving-it-s-own-hostname/53396/4

pralor-bot · 2022-02-10T11:26:39Z

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/finding-the-source-of-a-rebind/53449/20

r2ixuz · 2022-06-05T09:57:29Z

I stumbled upon this while I tried to use only non deprecated variables/settings. I need to bind the lighttpd listen address to a virtual eth interface while using docker mode host. With setting ServerIP ENV it works.

Readme says it is deprecated so I tried to use REPLY_ADDR4 only. This sets the listen interface to 0.0.0.0 as described by OP. Furthermore I read at https://docs.pi-hole.net/ftldns/configfile/ that REPLY_ADDR4 is also deprecated. That leaves me confused.

So, what is now or in the future the correct way to bind the lighttpd to one specific address while using docker host mode?

labodj · 2022-08-22T20:07:00Z

I stumbled upon this while I tried to use only non deprecated variables/settings. I need to bind the lighttpd listen address to a virtual eth interface while using docker mode host. With setting ServerIP ENV it works.

Readme says it is deprecated so I tried to use REPLY_ADDR4 only. This sets the listen interface to 0.0.0.0 as described by OP. Furthermore I read at https://docs.pi-hole.net/ftldns/configfile/ that REPLY_ADDR4 is also deprecated. That leaves me confused.

So, what is now or in the future the correct way to bind the lighttpd to one specific address while using docker host mode?

I second this.
This situation is very confusing.

docker-pi-hole readme

docker-pi-hole/README.md

Line 166 in 72634fc

    
           | `ServerIP` | Set to your server's LAN IP, used by web block modes and lighttpd bind address | `FTLCONF_REPLY_ADDR4` |

says to use FTLCONF_REPLY_ADDR4 instead of ServerIP

Pi-hole documentation says that REPLY_ADDR4 is deprecated, LOCAL_IPV4 must be used instead

PromoFaux · 2022-08-22T20:15:32Z

Deprecated is not the same as removed. It's still there for now, and will be read by FTL, so the documentation is not incorrect. :)

Thanks, however, for the pointer - I will look at changing the suggested variable to use instead of REPLY_ADDR4

r2ixuz · 2022-08-25T18:15:18Z

Binding lighthttpd for IPv4 works now with the new Docker image when using FTLCONF_LOCAL_IPV4.

But IPv6 is still binding to every IP:

tcp6 0 0 :::80 :::* LISTEN 13884/lighttpd

I set FTLCONF_LOCAL_IPV6 and FTLCONF_LOCAL_IPV4 via my docker-compose file. ServerIP is not set.

Edit: Typo corrected.

shaderecker · 2022-08-29T20:20:28Z

Hi guys,
Is it also now somehow possible to bind two IPs with the FTLCONF_LOCAL_IPV4?
Use case is accessing the website from the host IP address and also a Virtual IP address.

Edit: Ah, just leaving out the vars completely sets LOCAL_IPV4=0.0.0.0. So that's fine for my use case.

juliankrieger · 2023-02-09T23:46:21Z

I stumbled upon this issue because I had no luck setting up pi hole correctly with the given documentation, or any of the information in this issue. I was get pihole to work with my local devices, but the local DNS functionality won't work.

I'm confused on how to correctly setup my docker-compose.yml.

It seems like there is a lot of conflicting information here. Would anyone mind updating the recommended example docker compose?

PromoFaux mentioned this issue Jan 4, 2022

docker version tag > 2021.11: ERROR: ServerIPv6 Environment variable (X:X:X:X:X:X:X:X) doesn't appear to be a valid IPv6 address #961

Closed

github-actions bot added the Submitter Attention Required label Jan 27, 2022

PromoFaux added never-stale Use this label to ensure the stale action does not close this issue Help Wanted and removed Submitter Attention Required labels Jan 28, 2022

PromoFaux mentioned this issue Aug 22, 2022

FTLCONF_REPLY_ADDR4/6 are now deprecated. Use FTLCONF_LOCAL_IPV4/6 instead #1173

Merged

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ServerIP still required? #956

ServerIP still required? #956

scara commented Dec 27, 2021

dschaper commented Dec 27, 2021

scara commented Dec 27, 2021 •

edited

PromoFaux commented Dec 28, 2021

github-actions bot commented Jan 27, 2022

scara commented Jan 28, 2022

PromoFaux commented Jan 28, 2022

pralor-bot commented Feb 3, 2022

pralor-bot commented Feb 3, 2022

pralor-bot commented Feb 9, 2022

pralor-bot commented Feb 10, 2022

r2ixuz commented Jun 5, 2022

labodj commented Aug 22, 2022

PromoFaux commented Aug 22, 2022

r2ixuz commented Aug 25, 2022 •

edited

shaderecker commented Aug 29, 2022 •

edited

juliankrieger commented Feb 9, 2023

ServerIP still required? #956

ServerIP still required? #956

Comments

scara commented Dec 27, 2021

Details

Related Issues

How to reproduce the issue

These common fixes didn't work for my issue

dschaper commented Dec 27, 2021

scara commented Dec 27, 2021 • edited

PromoFaux commented Dec 28, 2021

github-actions bot commented Jan 27, 2022

scara commented Jan 28, 2022

PromoFaux commented Jan 28, 2022

pralor-bot commented Feb 3, 2022

pralor-bot commented Feb 3, 2022

pralor-bot commented Feb 9, 2022

pralor-bot commented Feb 10, 2022

r2ixuz commented Jun 5, 2022

labodj commented Aug 22, 2022

PromoFaux commented Aug 22, 2022

r2ixuz commented Aug 25, 2022 • edited

shaderecker commented Aug 29, 2022 • edited

juliankrieger commented Feb 9, 2023

scara commented Dec 27, 2021 •

edited

r2ixuz commented Aug 25, 2022 •

edited

shaderecker commented Aug 29, 2022 •

edited