[Support] binhex - DelugeVPN


Recommended Posts

5 hours ago, binhex said:

Ignore the error it's a minor python 3.8 issue that will be resolved at some point

Sent from my CLT-L09 using Tapatalk
 

I was getting ready to point out that the WebUI was not responding. Knowing now that the error at the bottom was non-fatal, I reviewed the output and saw this:

 

2020-01-11 08:57:11,626 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

 

I ran that and restarted the container and now all is well. Thanks!

Link to comment

I'm trying to use Pihole as my DNS for DelugeVPN so my clients connected via proxy get the adblocking that Pihole provides.

 

i added the Pihole local DNS ip to NAME_SERVERS but that doesnt seem to work. Pihole DNS runs through 8.8.8.8 and 8.8.4.4 currently for simplicity while trying to get the problem diagnosed.

2020-01-11 14:10:29,058 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.31 to /etc/resolv.conf

2020-01-11 14:10:44,077 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-01-11 14:10:59,095 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-01-11 14:11:19,113 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

Any idea where to go from here?

Link to comment
I'm trying to use Pihole as my DNS for DelugeVPN so my clients connected via proxy get the adblocking that Pihole provides.
 
i added the Pihole local DNS ip to NAME_SERVERS but that doesnt seem to work. Pihole DNS runs through 8.8.8.8 and 8.8.4.4 currently for simplicity while trying to get the problem diagnosed.
2020-01-11 14:10:29,058 DEBG 'start-script' stdout output:[info] Adding 192.168.1.31 to /etc/resolv.conf2020-01-11 14:10:44,077 DEBG 'start-script' stderr output:Error: error sending query: Could not send or receive, because of network error2020-01-11 14:10:59,095 DEBG 'start-script' stderr output:Error: error sending query: Could not send or receive, because of network error2020-01-11 14:11:19,113 DEBG 'start-script' stderr output:Error: error sending query: Could not send or receive, because of network error

Any idea where to go from here?

Your cannot use local DNS, name resolution is permitted only via VPN tunnel to prevent any chance of DNS leaks.

Sent from my CLT-L09 using Tapatalk

Link to comment
Hey Binhex,

Is there any chance I can get support for passing in a ovpn config with multiple remote options configured? I'd like my geolocation to be randomized within a specified range on vpn start. As it stands, if I use this kind of config, all of the extra remote options are forcibly removed from the file by your startup scripts.
Multiple remote lines are not supported and as you have found out, will be automatically removed

Sent from my CLT-L09 using Tapatalk

Link to comment
5 hours ago, Jamshm said:

Hello Binhex and Team

 

I just started using Unraid. I only have 1 docker and it is yours but it just does not want to work. I followed space invaders videos to a T with no luck.  please help!!!

Looks like you have too many digits in your LAN network setting. 10.0.0.1.0 isn’t valid. Judging by the error message you posted it should probably be 10.0.0.0/24 if your server address actually is 10.0.0.114.

  • Like 1
Link to comment
4 hours ago, binhex said:

Multiple remote lines are not supported and as you have found out, will be automatically removed

Sent from my CLT-L09 using Tapatalk
 

I noticed that it isn't supported. I'm asking if things could be rejiggered so that they could be supported? It looks like the reason why it doesn't work is that your init scripts rebuild the remote entry based on dns returns already - can we get a flag to disable this behavior?

Link to comment
21 hours ago, wgstarks said:

Looks like you have too many digits in your LAN network setting. 10.0.0.1.0 isn’t valid. Judging by the error message you posted it should probably be 10.0.0.0/24 if your server address actually is 10.0.0.114.

Thanks Walter.  However, I get the same message. I wonder if it is the files i added to the openvpn folder in app data folder. 

Link to comment

I am having an issue where my DL speeds fluctuate wildly. bouncing around between 30 Mib/s and a few Kib/s. It fluctuates a lot, which I can live with. The biggest issue is that it will look like it is running well, then all of the sudden drop to 0. Then all of the torrents have to build speed back up again. Any thoughts on where to start looking?

Link to comment
I am having an issue where my DL speeds fluctuate wildly. bouncing around between 30 Mib/s and a few Kib/s. It fluctuates a lot, which I can live with. The biggest issue is that it will look like it is running well, then all of the sudden drop to 0. Then all of the torrents have to build speed back up again. Any thoughts on where to start looking?
This will be a network issue, it could be your host, it could be your ISP or it could be your VPN provider, you need to check all 3 for drops.

Sent from my CLT-L09 using Tapatalk

  • Like 1
Link to comment
I followed this tutorial to install this awesome container!
http://tomthegreat.com/2018/03/11/setting-up-deluge-with-vpn-on-synology-using-docker/
 
The tutorial lets me add this: OPENVPN_OPTS – Set to “–inactive 3600 –ping 10 –ping-exit 60”
 
Should i add this or better leave it out?  Is there some sort of ''kill switch''? 
 
No you don't need those options, it auto reconnects on VPN tunnel going down

Sent from my CLT-L09 using Tapatalk

Link to comment
6 hours ago, binhex said:

No you don't need those options, it auto reconnects on VPN tunnel going down

Sent from my CLT-L09 using Tapatalk
 

Thank you!

 

Is this instand or there some delay in this check? When the tunnel is goes down, deluge will close instand?

Edited by Fishke
Link to comment
On 1/11/2020 at 3:32 AM, binhex said:

You need to find out the network for your host not the container

Sent from my CLT-L09 using Tapatalk
 

Okay so I opened the terminal for Unraid on my system and did the Ifconfig command again and here are the results:

Linux 4.18.20-unRAID.
root@UsreyMedia:~# ifconfig
bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500
        inet6 fe80::6d4:c4ff:fe57:4e55  prefixlen 64  scopeid 0x20<link>
        ether 04:d4:c4:57:4e:55  txqueuelen 1000  (Ethernet)
        RX packets 72344418  bytes 54455395648 (50.7 GiB)
        RX errors 0  dropped 0  overruns 235  frame 0
        TX packets 65535197  bytes 42700854453 (39.7 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.8  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::20de:c2ff:feca:eeb1  prefixlen 64  scopeid 0x20<link>
        ether 04:d4:c4:57:4e:55  txqueuelen 1000  (Ethernet)
        RX packets 57499139  bytes 53057311704 (49.4 GiB)
        RX errors 0  dropped 288  overruns 0  frame 0
        TX packets 60361649  bytes 42367326612 (39.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:bff:fef7:e2bf  prefixlen 64  scopeid 0x20<link>
        ether 02:42:0b:f7:e2:bf  txqueuelen 0  (Ethernet)
        RX packets 52046581  bytes 29530460190 (27.5 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 68956108  bytes 53570993784 (49.8 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 04:d4:c4:57:4e:55  txqueuelen 1000  (Ethernet)
        RX packets 72344422  bytes 54455396220 (50.7 GiB)
        RX errors 0  dropped 0  overruns 235  frame 0
        TX packets 65535203  bytes 42700859352 (39.7 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xf6500000-f651ffff

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4644616  bytes 5287958283 (4.9 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4644616  bytes 5287958283 (4.9 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth1114cec: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::e4ad:1eff:fefc:1397  prefixlen 64  scopeid 0x20<link>
        ether e6:ad:1e:fc:13:97  txqueuelen 0  (Ethernet)
        RX packets 104377  bytes 13762126 (13.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 79196  bytes 19082322 (18.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth24170d5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::d9:89ff:fe69:6c9  prefixlen 64  scopeid 0x20<link>
        ether 02:d9:89:69:06:c9  txqueuelen 0  (Ethernet)
        RX packets 68243  bytes 596845800 (569.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 161491  bytes 407691023 (388.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth8130a5e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::1487:90ff:fe6f:bb13  prefixlen 64  scopeid 0x20<link>
        ether 16:87:90:6f:bb:13  txqueuelen 0  (Ethernet)
        RX packets 188914  bytes 27153799 (25.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 217239  bytes 82407082 (78.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth832a600: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::6830:79ff:fe5b:85a5  prefixlen 64  scopeid 0x20<link>
        ether 6a:30:79:5b:85:a5  txqueuelen 0  (Ethernet)
        RX packets 45441742  bytes 27341002496 (25.4 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 48489479  bytes 36406310841 (33.9 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth8680b10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5cde:b5ff:fee9:c77f  prefixlen 64  scopeid 0x20<link>
        ether 5e:de:b5:e9:c7:7f  txqueuelen 0  (Ethernet)
        RX packets 996  bytes 1503463 (1.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1365  bytes 715255 (698.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth91db3b1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::458:d9ff:fece:12b1  prefixlen 64  scopeid 0x20<link>
        ether 06:58:d9:ce:12:b1  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2288  bytes 389239 (380.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethb3876c8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::546e:86ff:feef:e038  prefixlen 64  scopeid 0x20<link>
        ether 56:6e:86:ef:e0:38  txqueuelen 0  (Ethernet)
        RX packets 93193  bytes 20790815 (19.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 77287  bytes 50350863 (48.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:46:9e:b9  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Link to comment
8 minutes ago, 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.

Sorry for being dumb, but i can not find the egg file on that page. I am never sure how to get it from there. I used to get it clicking through the link in deluge under "more plugins". It went to a forum with a direct download.

Link to comment
6 minutes ago, jebusfreek666 said:

Sorry for being dumb, but i can not find the egg file on that page. I am never sure how to get it from there. I used to get it clicking through the link in deluge under "more plugins". It went to a forum with a direct download.

You will need to build it per the readme.

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.