pihole - error log: "can't bind to socket: 192.168.1.8:80 Address already in use"

[daptap]

I had a pihole running for a couple of years in docker in DSM. Then I tried to update the container today and it broke. After following this tutorial and this one (the same except for what they name the pihole subfolders in file station), I get the following error in the container log: "2021-11-22 20:35:17: (network.c.313) can't bind to socket: 192.168.1.8:80 Address already in use", then "stopping lighttpd", then "lighttpd: no process found". rinse and repeat in the log.

Any thoughts? I've read the other posts about pihole on the forum and didn't find it helpful to this error. I'm using port 8181 (webport variable added; see below). Using same network as docker host.

 

[Rusty]

port 80 is in use by default. What does your port mapping for this container looks like?

 

[daptap]

When I click the radio button below:

the port settings are blocked out --

But, googling more has led me to this article which has port mapping like this (so clearly they didn't check the radio button above).

 

[one-eyed-king]

If "Use the same network network as Docker Host" is enable, the container does not require / allow port mappings, at it already uses the hosts network interface directly. Network-wise this container runs like any other process on the host.

Of course you will need to make sure that there is no collisions between the occupied ports on the host and the ports the container wants to use. In you case lighttpd to bind port 80 inside the container, tries to bind against port 80 on the host , which is already bound to nginx.

When the container is stopped, you can remove the container from the "host network" and addit to the "bridge network", then add you port mappings and everything should be good. This can be done in Docker-UI -> "Network".

 

[daptap]

Yeah the last image I posted will work, I believe. Haven't tried it yet b/c I have a rp4 that is much easier to load with pihole and the DSM and so I just migrated to that. This article is what helped me. EDIT: @one-eyed-king - didn't see your post before posting this one. thanks for the response. I might go ahead and enable and then add the docker pi-hole as the secondary DNS in my router.

 

[daptap]

2 other questions:

1 - I got it running in Docker again using the article I posted to above. However, the GUI won't accept the pw I've assigned to it. I checked the pw in the container and entered it by typing, copy paste, pasting with lastpass, etc. Then I deleted and redid the container. still no dice. really strange. Maybe I'll just do one without a pw.

2 - I assume I would need to disable AP isolation on the guest network to be able to use the pihole on the guest network, right? Don't want to do that though.

 

[Coop777]

Yeah the last image I posted will work, I believe. Haven't tried it yet b/c I have a rp4 that is much easier to load with pihole and the DSM and so I just migrated to that. This article is what helped me. EDIT: @one-eyed-king - didn't see your post before posting this one. thanks for the response. I might go ahead and enable and then add the docker pi-hole as the secondary DNS in my router.

I got my first one running via that link...but you can't update pi hole versions once created. There's a second article that uses portainer and pi-hole that has a process for updating it....if you can't find it will post it later.

 

[sophiaabigail]

can't bind to socket: 192.168.1.8:80 Address already in use", then "stopping lighttpd", then "lighttpd: no process found". rinse and repeat ...I've been running pihole in 192.168.l.254 Docker on my DS920. ... pihole - error log: "can't bind to socket: 192.168.1.8:80 Address already in use".

 

[Rusty]

can't bind to socket: 192.168.1.8:80 Address already in use", then "stopping lighttpd", then "lighttpd: no process found". rinse and repeat ...I've been running pihole in 192.168.l.254 Docker on my DS920. ... pihole - error log: "can't bind to socket: 192.168.1.8:80 Address already in use".

Pihole UI will not work on 80, as 80 is in use by Synology's nginx (as it is 443), just bind it to some other local port