20 hours ago, binhex said:

dont do this, there were some issues with python 3.8 and deluge, fixed in the later images, so i wouldnt roll back to that version, what exactly is your issue with the latest image?.

It's in this post https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=813141, 

Basically the Web-UI shows a Error: Authorative host not found; then shortly there after it says Error: Connection refused for any torrent.  I have tried re-install and changing pia servers, re-downladed certs but still same issue.  DNS is resolved so not sure what the root issue is.

8 minutes ago, Sonyswarm said:

It's in this post https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=813141, 

Basically the Web-UI shows a Error: Authorative host not found; then shortly there after it says Error: Connection refused for any torrent.  I have tried re-install and changing pia servers, re-downladed certs but still same issue.  DNS is resolved so not sure what the root issue is.

that is a message from the tracker, most probably the tracker is refusing your client, either because its not a supported torrent client, and/or the ip address you are coming from is not permitted - vpn ranges are sometimes banned due to abuse.

 

if its the torrent client thats not permitted (probably NOT the case when downloading linux iso's as per your screenshot), then i would recommend rolling back to deluge 1.x, this will no doubt still be supported by most private trackers.

 

if its the vpn range thats been banned then try connecting to another endpoint, in your log snippet i can see you are connecting to 'ca-toronto', try another location.

1 minute ago, binhex said:

that is a message from the tracker, most probably the tracker is refusing your client, either because its not a supported torrent client, and/or the ip address you are coming from is not permitted - vpn ranges are sometimes banned due to abuse.

 

if its the torrent client thats not permitted (probably NOT the case when downloading linux iso's as per your screenshot), then i would recommend rolling back to deluge 1.x, this will no doubt still be supported by most private trackers.

 

if its the vpn range thats been banned then try connecting to another endpoint, in your log snippet i can see you are connecting to 'ca-toronto', try another location.

I did try two other end points (ca-vancouver, ca-montreal) but I got the same error.  Since rolling back to version 2.0.3-2-01 endpoint ca-toronto is working without issue.

 

When I attempted to re-install the docker of the latest image, I noticed the configuration settings were saved.  It seems unraid keeps it, should I attempt to delete the deluge folder in the appdata manually?

15 hours ago, Guanyin said:

@no1home I've noticed that Deluge doesn't crash when I disable proxy, when I enable proxy it keeps crashing and sometimes even not working.

These are my proxy settings:

What are the benefit of setting up proxy when using openvpn with PIA?

6 minutes ago, casperse said:

What are the benefit of setting up proxy when using openvpn with PIA?

when I enable PIA VPN I can't get over 2mbps somehow and proxy used to work for a while... If you know something to fix the speed for PIA VPN then I'd love to hear it

52 minutes ago, Guanyin said:

when I enable PIA VPN I can't get over 2mbps somehow and proxy used to work for a while... If you know something to fix the speed for PIA VPN then I'd love to hear it

 

My proxy setting is off--never enabled it. I don't think you need it since the container is managing that for you already.

1 hour ago, Guanyin said:

when I enable PIA VPN I can't get over 2mbps somehow and proxy used to work for a while... If you know something to fix the speed for PIA VPN then I'd love to hear it

Proxy is built in to the container. You shouldn’t try to add it to the app. I managed to boost my download speeds in Deluge v1 by using the ItConfig plugin to disable utp. Not sure if this still works in v2 though.

I'm getting a lot of spam in my deluged.log with "Session status key not valid:" thanks to the stats plugin, it starts off during the plugin load as such:

20:19:41.892 [INFO    ][deluge_label.core             :78  ] *** Start Label plugin ***
20:19:41.907 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Label enabled...
20:19:41.914 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:41.914 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:41.914 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:41.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:42.214 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Stats enabled...
20:19:42.218 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Scheduler enabled...

then it starts repeating constantly after all my torrents have loaded

20:19:49.616 [INFO    ][deluge.core.torrentmanager    :885 ] Finished loading 2032 torrents in 0:00:03.984063
20:19:49.831 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:49.831 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:50.046 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:50.046 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:50.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:50.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:50.936 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
20:19:51.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:51.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:52.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:52.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:53.138 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: xxx.x.x.x:xxxxx
20:19:53.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:53.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:54.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:54.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:55.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:55.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:56.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:56.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:57.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:57.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:58.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:58.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:59.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:59.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:00.656 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx
20:20:00.749 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
20:20:00.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:00.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:01.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:01.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:02.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:02.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:03.484 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx
20:20:03.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:03.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:04.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:04.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:05.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:05.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:06.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:06.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:07.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:07.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:08.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:08.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:09.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:09.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:10.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:10.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:11.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:11.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:12.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:12.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:13.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:13.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:14.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:14.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:15.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:15.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:16.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:16.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:17.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:17.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:18.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:18.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:19.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:19.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:20.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:20.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:21.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:21.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:22.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:22.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:23.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:23.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:24.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:24.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:25.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:55:09.531 [INFO    ][deluge.pluginmanagerbase      :250 ] Plugin Stats disabled...

-no errors for 5 minutes til i start it up again

20:59:43.245 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:43.245 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:43.246 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:43.246 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:43.510 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Stats enabled...
20:59:44.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:44.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:45.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:45.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:46.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:46.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:47.246 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:47.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:48.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:48.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections

Disabling the stats plugin prevents this spam from occurring, and according to this topic on the deluge bug tracker i have to do something to the stats egg. the problem is i'm not sure where this egg is located in the unraid/docker/delugevpn installation. any pointers on what to do to fix this?

Edited January 21, 20206 yr by MammothJerk

3 minutes ago, MammothJerk said:

problem is i'm not sure where this egg is located

appdata/binhex-delugevpn/plugins

7 minutes ago, wgstarks said:

appdata/binhex-delugevpn/plugins

haha i wish 😋

it's one of deluges default plugins

Edited January 21, 20206 yr by MammothJerk

i'm having problems getting NordVPN working and i have no idea why.  i had it running a 2-3 days ago and then all of a sudden, it stopped working.  the only thing i recall playing around with was docker-compose.  i've deleted any containers created from that.  i've deleted binhex-delugevpn, and re-added.  i left all variables default, except for custom, user/pass, disable port forwarding, and enabling privoxy.

 

as far as i can tell, i'm connected to NordVPN because there are no errors.  however, DNS is busted...

2020-01-23 20:35:33,373 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-01-23 20:37:33,493 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-01-23 20:39:38,619 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-01-23 20:39:38,619 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

any ideas of what i should look for next?  the only way i can get it working now is by running the nordvpn CLI from an ubuntu VM.

 

thanks.
 

2 minutes ago, bling said:

i'm having problems getting NordVPN working and i have no idea why.  i had it running a 2-3 days ago and then all of a sudden, it stopped working.  the only thing i recall playing around with was docker-compose.  i've deleted any containers created from that.  i've deleted binhex-delugevpn, and re-added.  i left all variables default, except for custom, user/pass, disable port forwarding, and enabling privoxy.

 

as far as i can tell, i'm connected to NordVPN because there are no errors.  however, DNS is busted...

2020-01-23 20:35:33,373 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-01-23 20:37:33,493 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-01-23 20:39:38,619 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-01-23 20:39:38,619 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

any ideas of what i should look for next?  the only way i can get it working now is by running the nordvpn CLI from an ubuntu VM.

 

thanks.
 

 What's your DNS option set to? try 1.1.1.1 

On 1/23/2020 at 8:47 PM, 0x646f6f6d said:

 What's your DNS option set to? try 1.1.1.1 

i left it at the default, which is 209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

changing it 1.1.1.1 just now has the same effect.

 

edit: i've tried other docker containers that do similar things, and all of that have the same problem.  some will download ovpn files correctly, authenticate, set up the tunnel, and once that's done everything is dead.  not only is DNS not working, i can't ping those servers either.  is there anything on unRAID itself that might conflict with setting up the VPN?  i diffed /boot from a backup a couple days ago and there's nothing related to networking....

 

edit2: argh!! it magically worked today with no action on my own.  looks like some of the servers are working and others aren't.

Edited January 25, 20206 yr by bling

I'm running DelugeVPN on Unraid without issue at the moment. I'm trying to setup a second container on a PhotonOS docker host separately, different VLAN from Unraid. I'm having an issue accessing the Deluge WebUI while the VPN is enabled. This is when trying to load the WebUI from a different computer on a different VLAN. As soon as the VPN is set to no it will load fine. The same setup on Unraid, VPN on and a different VLAN loads fine.

 

This seems to be the same issue as Kantraz from this page here:

Their same solution of running "iptables -t nat -A POSTROUTING -j MASQUERADE" on the host resolves the issue. I understand very little about iptables and I'm assuming this is opening up more than is required. Is there a cut down version specific to this container that could be used instead? This is the output prior to running the above command:

iptables -L
Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ssh

Chain FORWARD (policy DROP)
target     prot opt source               destination
DOCKER-USER  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere

Chain DOCKER (3 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             172.19.0.2           tcp dpt:9117
ACCEPT     tcp  --  anywhere             172.19.0.3           tcp dpt:58846
ACCEPT     tcp  --  anywhere             172.19.0.3           tcp dpt:privoxy
ACCEPT     tcp  --  anywhere             172.19.0.3           tcp dpt:8112

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (3 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-USER (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

 

Edited January 25, 20206 yr by stalkntom

On 1/21/2020 at 1:30 PM, Guanyin said:

when I enable PIA VPN I can't get over 2mbps somehow and proxy used to work for a while... If you know something to fix the speed for PIA VPN then I'd love to hear it

 

Are you using one of their servers with port forwarding? I would try a different server. I also think that if you have multiple ovpn files, it will only use the first one alphabetically? Could be wrong, but I think I read that some where. So you may have it set up in a way you think is right, but is actually wrong. 

 
Are you using one of their servers with port forwarding? I would try a different server. I also think that if you have multiple ovpn files, it will only use the first one alphabetically? Could be wrong, but I think I read that some where. So you may have it set up in a way you think is right, but is actually wrong. 

This is correct, it picks up the first ovpn file in the folder alphabetically

Sent from my CLT-L09 using Tapatalk

On 1/16/2020 at 8:25 AM, wgstarks said:

This one should work. I haven’t personally tested it though.

https://github.com/springjools/deluge-autoremoveplus

 

Maybe you could post your results after you try it.

For the life of me, I can not get this thing to work. I have it loaded, and can access settings. But no matter what settings I use, it will not remove anything. I'm sure there is just something stupid in the settings I am overlooking, but I don't know what it is. I have tried tweaking both general settings and creating specific rules for labels. Kind of at a dead end for the moment. 

36 minutes ago, jebusfreek666 said:

For the life of me, I can not get this thing to work. I have it loaded, and can access settings. But no matter what settings I use, it will not remove anything. I'm sure there is just something stupid in the settings I am overlooking, but I don't know what it is. I have tried tweaking both general settings and creating specific rules for labels. Kind of at a dead end for the moment. 

Probably need to check the Deluge logs and seek assistance on the github site. I know several other people have reported issues there as well. There have been quite a few recent updates to Deluge. May have broken something.

Is there some way to downgrade this docker container?

I found this issue:
https://github.com/binhex/arch-delugevpn/issues/146

I also want to be on a stable branch, some things don't work for my setup on a dev/unstable branch.

Thanks!

1 minute ago, Arndroid said:

Is there some way to downgrade this docker container?

Read the first couple of posts of this very thread.

Thanks!

Docker Hub didn't load for me when I asked the question.
Good to know there are instructions like that, and that Docker Hub loaded for me now.

Deluge v2 is fine fwiw, even with a thin client here... I just needed the stable branch of it.

 

 

I installed the latest Docker image on an Asustor NAS via Portainer. Logs indicate I’m getting a VPN connection but the script is dying trying to use “set-mark” directives in Iptables:

 

2020-01-29 12:04:34,168 DEBG 'start-script' stderr output:

iptables v1.8.3 (legacy):

2020-01-29 12:04:34,168 DEBG 'start-script' stderr output:

unknown option "--set-mark"

 

The host is running a 4.14.x kernel but it doesn’t include the iptables modules required to use “set-mark”. Are there any workarounds here? I only need to access the web UI on the host LAN network.

Hello everyone,

First, thank you to Binhex and to the Unraid community for your amazing work.

 

I switched lately from haugene/docker-transmission-openvpn to binhex/arch-delugevpn. I quite enjoy Deluge but I can't get the remote connection to work.

 

I opened ports on router, configured remote access in daemon, set connection manager, but it doesn't work for me. Stucked with a timeout when I try remote access.

LAN WebUI does work despite everything.

Could someone help me ?

Thanks for any help.

 

supervisord.log

deluge-web.log

 

Edit: It's now fixed without touching anything. No clue what was happening.

Edited February 2, 20206 yr by Kinchouka

Have there been some breaking updates to the container in regards to connecting to the daemon?
I can't connect using either the deluge-console ("deluge-console -d localhost -p 58846 -U user -P password"), or the desktop client (2.0.4.dev23).

 

I've been able to successfully connect to the daemon up until about a week ago.

The only new error I've seen is the "ngettext" issue from python, but that seems unlikely to be the source of this problem.

6 hours ago, 7thSon said:

Have there been some breaking updates to the container in regards to connecting to the daemon?
I can't connect using either the deluge-console ("deluge-console -d localhost -p 58846 -U user -P password"), or the desktop client (2.0.4.dev23).

 

I've been able to successfully connect to the daemon up until about a week ago.

The only new error I've seen is the "ngettext" issue from python, but that seems unlikely to be the source of this problem.

Working fine here on 3 different boxes. Try setting your VPN_ENABLED to no and see if it allows you to connect. If so, you need to investigate your VPN files and credentials.