FTLCONF_webserver_port environment variable is ignored

Versions

• Pi-hole: 6
• AdminLTE:
• FTL:

Platform

• OS and version: Fedora Server 41

• Platform: Podman

Expected behavior

when setting environment variale FTLCONF_webserver_port="9000, the should change the used port for web ui

Actual behavior / bug

-e FTLCONF_webserver_port="9000" is ignored

Steps to reproduce

Steps to reproduce the behavior:

use this command

create_pihole() {
    podman run -d \
    --name $PIHOLE_CONTAINER \
    --network host \
    -e TZ=Europe/Rome \
    -e FTLCONF_webserver_api_password="piholepassword" \
    -e FTLCONF_dns_listeningMode=all \
    -e FTLCONF_webserver_port="9000" \
    -v $PIHOLE_VOLUME:/etc/pihole \
    --cap-add NET_ADMIN \
    --restart unless-stopped \
    pihole/pihole:latest
}

this is the output of podman ps:

27f26380d855 docker.io/pihole/pihole:latest 2 seconds ago Up 2 seconds 53/tcp, 80/tcp, 443/tcp, 53/udp, 67/udp, 123/udp pihole

[PromoFaux]

What's the actual output from the container logs?

Do you not need to portmap? I.e -p 9000:9000

@PromoFaux here the logs

  [i] Setting up user & group for the pihole user
  [i] PIHOLE_UID not set in environment, using default (1000)
  [i] PIHOLE_GID not set in environment, using default (1000)

  [i] Starting FTL configuration
  [i] Assigning password defined by Environment Variable
  [i] Starting crond for scheduled scripts. Randomizing times for gravity and update checker

  [i] Ensuring logrotate script exists in /etc/pihole

  [i] Gravity migration checks
  [i] Existing gravity database found - schema will be upgraded if necessary
     

  [i] pihole-FTL pre-start checks
  [i] Setting capabilities on pihole-FTL where possible
  [i] Applying the following caps to pihole-FTL:
        * CAP_CHOWN
        * CAP_NET_BIND_SERVICE
        * CAP_NET_ADMIN

  [i] Starting pihole-FTL (no-daemon) as pihole

  [i] Version info:
      Core version is v6.0.5 (Latest: v6.0.5)
      Web version is v6.0.2 (Latest: v6.0.2)
      FTL version is v6.0.4 (Latest: v6.0.4)

2025-03-25 13:48:54.467 CET [46M] INFO: ########## FTL started on localhost.localdomain! ##########
2025-03-25 13:48:54.467 CET [46M] INFO: FTL branch: master
2025-03-25 13:48:54.468 CET [46M] INFO: FTL version: v6.0.4
2025-03-25 13:48:54.468 CET [46M] INFO: FTL commit: b7eb53bf
2025-03-25 13:48:54.468 CET [46M] INFO: FTL date: 2025-03-04 17:22:10 +0000
2025-03-25 13:48:54.468 CET [46M] INFO: FTL user: pihole
2025-03-25 13:48:54.468 CET [46M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-25 13:48:54.681 CET [46M] INFO: 3 FTLCONF environment variables found (3 used, 0 invalid, 0 ignored)
2025-03-25 13:48:54.681 CET [46M] INFO:    [✓] FTLCONF_dns_listeningMode is used
2025-03-25 13:48:54.681 CET [46M] INFO:    [✓] FTLCONF_webserver_api_password is used
2025-03-25 13:48:54.681 CET [46M] INFO:    [✓] FTLCONF_webserver_port is used
2025-03-25 13:48:54.682 CET [46M] INFO: Wrote config file:
2025-03-25 13:48:54.682 CET [46M] INFO:  - 153 total entries
2025-03-25 13:48:54.682 CET [46M] INFO:  - 148 entries are default
2025-03-25 13:48:54.682 CET [46M] INFO:  - 5 entries are modified
2025-03-25 13:48:54.682 CET [46M] INFO:  - 2 entries are forced through environment
2025-03-25 13:48:54.683 CET [46M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-03-25 13:48:54.683 CET [46M] INFO: PID file does not exist or not readable
2025-03-25 13:48:54.683 CET [46M] INFO: No other running FTL process found.
2025-03-25 13:48:54.683 CET [46M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0
2025-03-25 13:48:54.686 CET [46M] INFO: PID of FTL process: 46
2025-03-25 13:48:54.692 CET [46M] CRIT: Error in dnsmasq configuration: failed to create listening socket for port 53: Permission denied
2025-03-25 13:48:54.710 CET [46M] INFO: PID of FTL process: 46
2025-03-25 13:48:54.712 CET [46M] INFO: Database version is 21
2025-03-25 13:48:54.712 CET [46M] INFO: Database successfully initialized
2025-03-25 13:48:54.770 CET [46M] INFO: Imported 4698 queries from the on-disk database (it has 15884 rows)
2025-03-25 13:48:54.770 CET [46M] INFO: Parsing queries in database
2025-03-25 13:48:54.786 CET [46M] INFO: Imported 4698 queries from the long-term database
2025-03-25 13:48:54.786 CET [46M] INFO:  -> Total DNS queries: 4698
2025-03-25 13:48:54.786 CET [46M] INFO:  -> Cached DNS queries: 3312
2025-03-25 13:48:54.786 CET [46M] INFO:  -> Forwarded DNS queries: 1143
2025-03-25 13:48:54.786 CET [46M] INFO:  -> Blocked DNS queries: 218
2025-03-25 13:48:54.786 CET [46M] INFO:  -> Unknown DNS queries: 0
2025-03-25 13:48:54.787 CET [46M] INFO:  -> Unique domains: 384
2025-03-25 13:48:54.787 CET [46M] INFO:  -> Unique clients: 10
2025-03-25 13:48:54.787 CET [46M] INFO:  -> DNS cache records: 73
2025-03-25 13:48:54.787 CET [46M] INFO:  -> Known forward destinations: 4
2025-03-25 13:48:54.924 CET [46M] WARNING: Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available
2025-03-25 13:48:54.924 CET [46/T47] ERROR: Error NTP server: Cannot bind to IPv4 address 0.0.0.0:123 (Permission denied), IPv4 NTP server not available
2025-03-25 13:48:54.924 CET [46/T48] ERROR: Error NTP server: Cannot bind to IPv6 address :::123 (Permission denied), IPv6 NTP server not available
2025-03-25 13:48:54.924 CET [46M] INFO: FTL is running as user pihole (UID 1000)
2025-03-25 13:48:54.925 CET [46M] INFO: Web server ports:
2025-03-25 13:48:54.925 CET [46M] INFO:   - 0.0.0.0:9083 (HTTP, IPv4, OK)
2025-03-25 13:48:54.928 CET [46M] INFO: Restored 0 API sessions from the database

And remap does not makes sense since I’m using the host network. Postman agrees and ignores any port mapping set, and returns a warning in verbose

[PromoFaux]

Hmmm. Are you definitely setting it to 9000?

From the logs:

2025-03-25 13:48:54.925 CET [46M] INFO: - 0.0.0.0:9083 (HTTP, IPv4, OK)

Hmmm. Are you definitely setting it to 9000?

From the logs:

2025-03-25 13:48:54.925 CET [46M] INFO: - 0.0.0.0:9083 (HTTP, IPv4, OK)

No I tried several ports, the last attempt did with 9083, as the container logs. But podman ps still says the open port is 80/tcp

[PromoFaux]

I'll see if I can play a out later, I'm not really familiar enough with podman to be able to say what's going on here.

The environment variable is definitely being read, per the logs, and FTL is listening on said port.

I'll see if I can play a out later, I'm not really familiar enough with podman to be able to say what's going on here.

The environment variable is definitely being read, per the logs, and FTL is listening on said port.

Thanks. I’ll try it on another pc and report. Does it work for you using docker? It should be the same command but with docker command

works on another pc, I'll troubleshoot further and eventually open an issue. thanks for your support.

[PromoFaux]

Interesting, OK sure! Could be a configuration thing on the host I guess.

And yes, it works for me in docker - although usually I just use macvlan networking