search

sebgl / htpc-download-box

Sonarr / Radarr / Jackett / NZBGet / Deluge / OpenVPN / Plex
1.94k stars 323 forks source link

Deluge UI inaccessible remotely #36

Open timkelty opened 4 years ago

timkelty commented 4 years ago

Configured as shown, I can only access deluge from localhost. I can't even access it from my local network with the machine's IP (e.g. 192.168.0.5:8112). Every other service I can access, so I'm guessing it has something to do with the vpn network.

Any ideas?

Also, in your guide you state:

Important ports are 8112 (web UI) and 58846 (bittorrent daemon)

But I don't see 58846 referenced in the compose file at all. Should it be?

nebajoth commented 4 years ago

I am having this issue as well.

javierdlg commented 4 years ago

Oh I just opened another issue regarding this specifically.

I can access all the other services remotely, through port forwarding or my router's VPN except Deluge for some reason. I can access it locally but well, I'm no longer permitted into the US with the visa ban xD

So I'd very much appreciate finding a way to remotely access my deluge web server.

javierdlg commented 4 years ago

@timkelty the daemon port gets set in the deluge preferences, shown below. And if it's not configured, deluge wouldn't work at all.

@nebajoth and @timkelty Could you check that you enabled remote access in the deluge preferences? image

javierdlg commented 4 years ago

I just tried enabling this setting through the config file in the server box and it still doesn't work.

Just to be clear, I have port forwarding and a router VPN set up and both fail with deluge but work with everything else even with that setting enabled. Maybe there's another setting missing?

javierdlg commented 4 years ago

Bit of an update: I was able to flip the allow remote connection on Deluge but it seems to be an issue with the VPN specifically. Hoping someone else might know more as to how to enable remote connections to the VPN endpoint in the local network.

But for now I'll be looking into setting up a reverse proxy and see if that works.

javierdlg commented 4 years ago

This issue has been fixed on the OpenVPN side. Do a docker-compose down, get the latest image using docker pull dperson/openvpn-client:latest, and then compose them back up using docker-compose up -d.

https://github.com/dperson/openvpn-client/pull/317 @sebgl feel free to close this issue

kayti commented 3 years ago

As for me it doesn't work, can load GUI through localhost (ubuntu desktop) but accessing via ip is not working (connection timeout). Latest version of each docker container.

dinckelman commented 1 year ago

I've noticed that this happens with not just Deluge, but anything that you'd put under network_mode: service:vpn. After about a day, deluge becomes unavailable until a container restart. Have no found the issue, and there's nothing in the logs