Help with v6 admin UI webserver

Help
1

I'm having weird trouble. When i run 'network_mode: host' i cant get to the admin webUI. If instead, i run -p 80:80 & 443:443 in my compoe, i get there just fine, everything works. I'd just to use DHCP so i want to run in network host mode.

Expected Behaviour:

expected to log into admin webUI in network mode host.

Actual Behaviour:

nothing. it seems the webservice isnt running?

$ nmap -Pn 192.168.1.3 -p 443,80
Starting Nmap 7.93 ( https://nmap.org ) at 2024-12-18 17:12 CST
Nmap scan report for 192.168.1.3
Host is up (0.0094s latency).

PORT STATE SERVICE
80/tcp closed http
443/tcp closed https

Debug Token:

https://tricorder.pi-hole.net/45GFQBup/

##Compose

version: "3.4"                                            # More info at https://github.com/pi-hole/docker-pi-hole/tree/development
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:development
    network_mode: host
#    ports:
#      - "53:53/tcp"                                        # DNS Port TCP
#      - "53:53/udp"                                        # DNS Port UDP
#      - "80:80/tcp"                                        # Default HTTP Port
#      - "443:443/tcp"                                      # Default HTTPs Port. FTL will generate a self-signed certificate
#      - "67:67/udp"                                        # Uncomment this line if using Pi-hole as your DHCP Server
    environment:
      PUID: 1000
      GUID: 1000
      TZ: 'America/Chicago'                                # Set the appropriate timezone for your location (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), e.g:
      FTLCONF_webserver_api_password: 'sdklfndsklfns'           # Set a password to access the web interface. Not setting one will result in a random password being assigned
    volumes:                                               # Volumes store your data between container upgrades
      - '/mnt/docker_configs_local/pihole:/etc/pihole'                         # For persisting Pi-hole's databases and common configuration file
    #- './etc-dnsmasq.d:/etc/dnsmasq.d'                    # Uncomment this line if you have custom dnsmasq config files that you want to persist. Not needed for most.
    cap_add:                                               # See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
      - NET_ADMIN                                          # Required if you are using Pi-hole as your DHCP server, else not needed
      - SYS_TIME
      - SYS_NICE
    restart: unless-stopped
    deploy:
      placement:
        constraints:
          - node.hostname == rpi5a
2

What is the output of this command when you try to use host network?

sudo ss -tupln '( dport = 80 or dport = 443 or sport = 80 or sport = 443 )'

NOTE:

image: pihole/pihole:development

You are using the wrong image.
development tag is updated only when we need to update the container dependencies or code related to docker-pihole.
This image is not updated when there are new code in Core, Web or FTL.

If you want to test v6 using the most recent updates, please use pihole/pihole:nightly.

3

updated to proper image

with network_mode:host in compose

https://tricorder.pi-hole.net/knIz1Xvd/

5e4de0807113:/# sudo ss -tupln '( dport = 80 or dport = 443 or sport = 80 or sport = 443 )'
Netid              State               Recv-Q              Send-Q                           Local Address:Port                           Peer Address:Port             Process
tcp                LISTEN              0                   200                                    0.0.0.0:80                                  0.0.0.0:*
tcp                LISTEN              0                   200                                    0.0.0.0:443                                 0.0.0.0:*
tcp                LISTEN              0                   200                                       [::]:80                                     [::]:*
tcp                LISTEN              0                   200                                       [::]:443                                    [::]:*

desktop::~::22:06:09::$ nmap -Pn 192.168.1.3 -p 443,80
Starting Nmap 7.93 ( https://nmap.org ) at 2024-12-18 22:06 CST
Nmap scan report for 192.168.1.3
Host is up (0.0068s latency).

PORT    STATE  SERVICE
80/tcp  closed http
443/tcp closed https

with ports specified in compose

https://tricorder.pi-hole.net/MVg7it8U/

ac068be01141:/# sudo ss -tupln '( dport = 80 or dport = 443 or sport = 80 or sport = 443 )'
Netid              State               Recv-Q              Send-Q                           Local Address:Port                           Peer Address:Port             Process
tcp                LISTEN              0                   200                                    0.0.0.0:80                                  0.0.0.0:*
tcp                LISTEN              0                   200                                    0.0.0.0:443                                 0.0.0.0:*
tcp                LISTEN              0                   200                                       [::]:80                                     [::]:*
tcp                LISTEN              0                   200                                       [::]:443                                    [::]:*

desktop::~::22:07:26::$ nmap -Pn 192.168.1.3 -p 443,80
Starting Nmap 7.93 ( https://nmap.org ) at 2024-12-18 22:10 CST
Nmap scan report for 192.168.1.3
Host is up (0.024s latency).

PORT    STATE SERVICE
80/tcp  open  http
443/tcp open  https