Let me know what information you need from me to help resolve this. I would like some assistance getting back to a working state. This isn't a great workaround though, since there are paths within the config that point to volume locations within the container. Everything seemed to work right away, which gives me some confidence that my config is not the problem. I found that I was able to successfully run (and connect to) the daemon if the daemon was run from the host system (using the same parameters I saw from ps, substituting volume mount paths). I was unable to connect to the daemon from this instance as well. I then tried starting the web UI on my host system.

I was not able to connect to the daemon from either instance of deluge-console. I tried debugging this by running deluge-console from within the container and from the host system. 11:09:45 torrentmanager:779 Successfully loaded fastresume file: /config/state/torrents.fastresume 11:09:45 torrentmanager:650 Successfully loaded state file: /config/state/torrents.state 11:09:45 preferencesmanager:496 Unable to find GeoIP database file! 11:09:45 configmanager:70 Setting config directory to: /config Here is the output of ps from within the container: I could not add a duplicate daemon to the connection manager. I tried removing the daemon from the list so I could re-add it, but this also had no effect. I was unable to click Connect from the web UI because the daemon was offline. When I returned the connection manager was open, showing the daemon as Offline. I switched tabs to my email and came back to the deluge tab about 30 minutes later. These torrents added successfully, and began downloading almost immediately. Today I was using the deluge web UI from the container to add a few small torrents. I have been using your image for several months with no problems. I was able to connect to the daemon when I ran it directly on the host system. In each case I was unable to connect to the daemon. I have tried running deluge-web and deluge-console from within the container, as well as from the host system. I cannot connect to the daemon within the running docker container.

Deluge torrent immediately shows error