Deluge web-ui blocked by docker-proxy?

LSIO Discussion Container Support
,
1

Cannot open the web-ui on 8112 anymore. Here’s the relevant log info…

09:11:48 [ERROR   ][deluge.ui.web.web          :81  ] Couldn't listen on 192.168.10.35:8112: [Errno 99] Address not available. 
deluge     | Check that deluge-web or webui plugin is not already running.

… and here’s a netstat which finds docker-proxy…

Kodi:~ # netstat -tulpn | grep :8112
tcp        0      0 0.0.0.0:8112            0.0.0.0:*               LISTEN      28968/docker-proxy

Honestly can’t recall making any changes other than adding/removing radarr to my compose.yml the other day at about the time this breakage occured. Not sure how to troubleshoot this much further as I’m just learning containers after 20+ years of bare metal admin.

System is CoreELEC latest on ODroid N2+ using the CE Docker plugin v19.03.15 and the following compose file.

version: "2.1"
services:
  deluge:
    image: lscr.io/linuxserver/deluge:latest
    container_name: deluge
    environment:
      - PUID=65534
      - PGID=0
      - UMASK=002
      - TZ=America/Chicago
      - DELUGE_LOGLEVEL=error #optional
    volumes:
      - /storage/.config/dockers/deluged:/config
      - /media/storage1/mdrive:/downloads
    ports:
      - 8112:8112
      - 49104:65525
      - 49104:65525/udp
    restart: unless-stopped
  jackett:
    image: lscr.io/linuxserver/jackett:latest
    container_name: jackett
    environment:
      - PUID=65534
      - PGID=0
      - UMASK=002
      - TZ=America/Chicago
      - AUTO_UPDATE=true #optional
      - RUN_OPTS= #optional
    volumes:
      - /storage/.config/dockers/jackett:/config
      - /media/storage1/mdrive:/downloads
    ports:
      - 9117:9117
    restart: unless-stopped
  sonarr:
    image: lscr.io/linuxserver/sonarr:latest
    container_name: sonarr
    environment:
      - PUID=65534
      - PGID=0
      - UMASK=002
      - TZ=America/Chicago
    volumes:
      - /storage/.config/dockers/sonarr:/config
      - /media/storage1/mdrive:/downloads
    ports:
      - 8989:8989
    restart: unless-stopped
2

it seems like you already have a container running using port 8112.

try docker ps | grep 8112 and see what comes up

3

Forgot to add the process list. CE/LE don’t have grep . We’ll use …

Kodi:~ # docker-compose ps
 Name     Command   State                                                      Ports                                                   
---------------------------------------------------------------------------------------------------------------------------------------
deluge    /init     Up      58846/tcp, 58946/tcp, 58946/udp, 0.0.0.0:49104->65525/tcp, 0.0.0.0:49104->65525/udp, 0.0.0.0:8112->8112/tcp
jackett   /init     Up      0.0.0.0:9117->9117/tcp                                                                                     
sonarr    /init     Up      0.0.0.0:8989->8989/tcp

Doesn’t look like any other containers are trying to glom onto 8112.

4

you already have deluge running though and it’s using 8112. i bet if you docker stop deluge and then up -d your compose, it’ll run. you will likely encounter the same for the *arrs because they’re already running as well. stop them, then bring them up with compose.

side note, are you starvin marvin from sg/uv? :slight_smile:

5

I’ve tried that, many times. Sames results. Tried docker-compose rm deluge, tried pruning while deluge was down, I’m out of things to try.

edit: not sure what sg/uv is so, likely not :slight_smile: Also, been considering using the docker-coreelec 20.04 version instead of the CoreELEC supplied 19.03 version of docker

6

you can’t rm a non-compose container with compose.
try just doing, docker stop deluge then check docker ps and see if deluge is running. if it is not, do docker-compose up -d deluge (-f to your yml if necessary)

definitely upgrade your docker engine, we’ve been seeing a lot of issues, though not this one, which is just a port conflict.

7

FWIW, there are no other containers on that system, within Kodi or externally, other than what you see in the compose.yml i posted

Here ya go…

Kodi:~ # docker stop deluge
deluge
Kodi:~ # docker ps
CONTAINER ID        IMAGE                                COMMAND             CREATED             STATUS              PORTS                    NAMES
f07f7abaa95a        lscr.io/linuxserver/sonarr:latest    "/init"             About an hour ago   Up 37 minutes       0.0.0.0:8989->8989/tcp   sonarr
85b199fbc006        lscr.io/linuxserver/jackett:latest   "/init"             About an hour ago   Up 37 minutes       0.0.0.0:9117->9117/tcp   jackett
Kodi:~ # 
Kodi:~ # docker-compose up -d deluge
Starting deluge ... done
Kodi:~ # 
Kodi:~ # docker ps
CONTAINER ID        IMAGE                                COMMAND             CREATED             STATUS              PORTS                                                                                                         NAMES
f07f7abaa95a        lscr.io/linuxserver/sonarr:latest    "/init"             About an hour ago   Up 37 minutes       0.0.0.0:8989->8989/tcp                                                                                        sonarr
85b199fbc006        lscr.io/linuxserver/jackett:latest   "/init"             About an hour ago   Up 37 minutes       0.0.0.0:9117->9117/tcp                                                                                        jackett
1f11d35574f9        lscr.io/linuxserver/deluge:latest    "/init"             About an hour ago   Up 7 seconds        58846/tcp, 0.0.0.0:8112->8112/tcp, 58946/tcp, 58946/udp, 0.0.0.0:49104->65525/tcp, 0.0.0.0:49104->65525/udp   deluge

Quick check of the logs…

deluge     | -------------------------------------
deluge     |           _         ()
deluge     |          | |  ___   _    __
deluge     |          | | / __| | |  /  \
deluge     |          | | \__ \ | | | () |
deluge     |          |_| |___/ |_|  \__/
deluge     | Brought to you by linuxserver.io
deluge     | -------------------------------------
deluge     | To support LSIO projects visit:
deluge     | https://www.linuxserver.io/donate/
deluge     | -------------------------------------
deluge     | GID/UID
deluge     | -------------------------------------
deluge     | User uid:    65534
deluge     | User gid:    0
deluge     | -------------------------------------
deluge     | cont-init: info: /etc/cont-init.d/10-adduser exited 0
deluge     | cont-init: info: running /etc/cont-init.d/30-config
deluge     | cont-init: info: /etc/cont-init.d/30-config exited 0
deluge     | cont-init: info: running /etc/cont-init.d/90-custom-folders
deluge     | cont-init: info: /etc/cont-init.d/90-custom-folders exited 0
deluge     | cont-init: info: running /etc/cont-init.d/99-custom-files
deluge     | [custom-init] no custom files found exiting...
deluge     | cont-init: info: /etc/cont-init.d/99-custom-files exited 0
deluge     | s6-rc: info: service legacy-cont-init successfully started
deluge     | s6-rc: info: service legacy-services: starting
deluge     | services-up: info: copying legacy longrun apiping (no readiness notification)
deluge     | services-up: info: copying legacy longrun deluge-web (no readiness notification)
deluge     | services-up: info: copying legacy longrun deluged (no readiness notification)
deluge     | s6-rc: info: service legacy-services successfully started
deluge     | s6-rc: info: service 99-ci-service-check: starting
deluge     | [ls.io-init] done.
deluge     | s6-rc: info: service 99-ci-service-check successfully started
deluge     | 10:24:09 [ERROR   ][deluge.ui.web.web          :81  ] Couldn't listen on 192.168.10.35:8112: [Errno 99] Address not available. 
deluge     | Check that deluge-web or webui plugin is not already running.
deluge     | 10:24:13 [ERROR   ][deluge.ui.web.web          :81  ] Couldn't listen on 192.168.10.35:8112: [Errno 99] Address not available. 
deluge     | Check that deluge-web or webui plugin is not already running.
8

wow that’s weird as fuck. sorry I didn’t understand the issue previously, i get it now. it may be best for you to pop in to our discord for more realtime support. unfortunately, I do not and have not ever used coreelec, though I believe we have a couple members with experience. Lets rule out any nuances.

9

IKR? Something (docker-proxy?) inside the container appears to jump onto the port before deluge-web get’s in there. My lack of docker internals knowledge has me stuck here. As for Discord, I’ll have to wait until I get to a windows desktop to run it, this ChromeBook running xubuntu would keel over :stuck_out_tongue:

10

docker-proxy is just what shows up for anything using a port mapping in docker. so that’s expected, but the error is definitely odd.

for discord, keep in mind, you can use the web version too. that said, ill see if the coreelec guys will peek at this thread.

11

initial suggestion from the team is to upgrade docker as you considered above. let’s try that first and then just let us know if that changes anything

12

rodger dodger. i’ll build it locally and dump the CE version, then report back

13

Cross-compiled installed and pulling with 20.10.16-4 right now, Sonarr starts fine but jackett and deluge are in perpetual restart

Kodi:~ # docker-compose ps
 Name     Command     State              Ports         
-------------------------------------------------------
deluge    /init     Restarting                         
jackett   /init     Restarting                         
sonarr    /init     Up           0.0.0.0:8989->8989/tcp

Perhaps i need to update my docker-compose.yml to a later docker version?

14

[SOLVED]

The problem was with the deluge web.conf param "interface": "x.x.x.x",

I had mine pinned to the host machine, in this case the CoreELEC box’s IP. Inside a container, this turns out to be A Bad Thing. Setting it to null did the trick for me although “0.0.0.0” should also fix it. I recall trying muck about with the Windows 2.0beta client and may have tinkered with web.conf

Thanks driz and shout out to TheOtherGuy that spotted the err!

15

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.