Port 80/443 already in use (Deconz)

[mwegener-com]

Hey,
I would like to run pi-hole in docker using docker compose on my pi4.
I'm already using this PI as an Zigbee Gateway, so i'm running Deconz in Docker as well.
Deconz also uses port 80 for its Webinterface.

What is the best way to setup my pi, running pi-hole and Deconz?

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      742/deCONZ          
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      552/sshd            
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      742/deCONZ          
tcp6       0      0 :::22                   :::*                    LISTEN      552/sshd            
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           742/deCONZ          
udp        0      0 0.0.0.0:68              0.0.0.0:*                           542/dhcpcd          
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           340/avahi-daemon: r 
udp        0      0 0.0.0.0:40685           0.0.0.0:*                           340/avahi-daemon: r 
udp6       0      0 :::33102                :::*                                340/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                340/avahi-daemon: r 

[Bucking_Horn]

You'd have to resolve that conflict, e.g. by shifting one of the machine to different ports. Note that Pi-hole's UI does not use port 443, only port 80.

You may try to apply Pi-hole's WEB_PORT Docker environment variable (If you use Pi-hole's default NULL blocking mode, you may ignore the linked comments about the 'webpage blocked' functionality).

[mwegener-com]

Tried this, but getting the same error for 443:

[Bucking_Horn]

As said before, Pi-hole does not require port 443 for its operation at all.

If you are using Pi-hole's default NULL blocking mode, you can remove it from your Docker configuration.

(Pi-hole's Docker configuraton still includes port 443 for the out-dated IP blocking modes, so that HTTPS requests wouldn't starve on time-outs.)

[DanSchaper]

Are you running Pi-hole in docker as well? If so, please provide the docker run line or the docker-compose yaml file.

There's no need to bind the host tcp/443 to the container, as Bucking_Horn has mentioned.