Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to connect to daemon from Deluge thin-client #139

Closed
JoeMShanahan opened this issue Nov 13, 2019 · 3 comments
Closed

Not able to connect to daemon from Deluge thin-client #139

JoeMShanahan opened this issue Nov 13, 2019 · 3 comments

Comments

@JoeMShanahan
Copy link

JoeMShanahan commented Nov 13, 2019

I have the latest docker image running Deluge 2.0.3.

My client is a VM on the Unraid server running Ubuntu 18.04.3, it also has Deluge 2.0.3

The Deluge daemon does not report as being online.

Unraid host 192.168.0.35
 |   |
 |    +- Docker image
 |         |
 |         +- Daemon running on 58846, with working Webui on 192.168.0.35:8112
 |
 +- VM 192.168.0.30
      |
      +- Can't connect to daemon on 192.168.0.35:58846 with a user/pass from auth file

How do I debug this?

@fryfrog
Copy link

fryfrog commented Nov 13, 2019

Show your docker run or docker-compose.yml, are you passing through the port?

@binhex
Copy link
Owner

binhex commented Nov 19, 2019

probably due to the NAT on the vm, make sure you define the LAN_NETWORK to also include the vm's network as well as your lan.

@groot-stuff
Copy link

groot-stuff commented Nov 21, 2020

Confirming that updating the LAN_NETWORK container parameter fixed my connection issue when attempting to connect from another subnet (my firewall/router has multiple subnet, vlan and zone support).

My config for reference:

  • unRaid server on 10.3.0.0/28
  • Wireless devices on 10.4.0.0/24

Previously I only had LAN_NETWORK set to 10.3.0.0/28 and the webui worked fine...
but I couldn't connect from my wireless devices on 10.4.0.0/24 through the Trireme for Deluge android app (found on the F-Droid app store if you are interested).

Setting my LAN_NETWORK parameter to 10.3.0.0/28,10.4.0.0/24 and restarting the container now allows me to connect from my wireless devices on 10.4.0.0/24.

Thanks @binhex !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants