[Support] binhex - DelugeVPN

binhex

By binhex
in Docker Containers

Recommended Posts

Recommended

Posted by binhex,

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A new image has now been rolled out for all vpn enabled docker images (25th Feb 2021) i produce with the fix in place, i would encourage everyone to update to the recently created 'latest' tagged image.   You can force the upgrade by toggling 'basic view' to 'advanced view' and then clicking on
Recommended by binhex
  • Thanks
  • Like

8 reactions

Go to this post
Recommended

Posted by Ryanoc3ros,

Found the solution on reddit.   Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead. You can find your service credentials by following these steps: Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/ Click on the NordVPN tab on the left panel which is under the Services tab.

NordVPN authentication issues - Solution

Recommended by binhex

  • Upvote
  • Thanks
  • Like

13 reactions

Go to this post
  • Replies 10.3k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Ryanoc3ros
Ryanoc3ros

Found the solution on reddit.   Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to u

Dad_Rage
Dad_Rage

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

binhex
binhex

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

Posted Images

Sonyswarm Noob

Sonyswarm

Posted
Posted
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.

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
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.

Link to comment
Sonyswarm Noob

Sonyswarm

Posted
Posted
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?

Link to comment
snowboardjoe Contributor

snowboardjoe

Posted
Posted
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.

  • Like 1
Link to comment
wgstarks Experienced

wgstarks

Posted
Posted
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.

  • Like 1
Link to comment
MammothJerk Apprentice

MammothJerk

Posted
Posted (edited)

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 by MammothJerk
Link to comment
bling Noob

bling

Posted
Posted

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.
 

Link to comment
0x646f6f6d Noob

0x646f6f6d

Posted
Posted
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 

Link to comment
bling Noob

bling

Posted
Posted (edited)
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 by bling
Link to comment
stalkntom Noob

stalkntom

Posted
Posted (edited)

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 by stalkntom
Link to comment
jebusfreek666 Explorer

jebusfreek666

Posted
Posted
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. 

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
 
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

Link to comment
jebusfreek666 Explorer

jebusfreek666

Posted
Posted
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. 

Link to comment
wgstarks Experienced

wgstarks

Posted
Posted
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.

Link to comment
rastus Noob

rastus

Posted
Posted

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.

Link to comment
Kinchouka Noob

Kinchouka

Posted
Posted (edited)

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 by Kinchouka
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing