Jump to content
binhex

[Support] binhex - DelugeVPN

4251 posts in this topic Last Reply

Recommended Posts

Hi

 

I have been using Newshosting as a VPN for about a year and decided to move to PureVPN as I got a good deal. I can get connected but nothing downloads even the checkmytorrentip. I am using a server that PureVPN states is not blocked for p2p so it should work.

Any ideas?

Attached is my supervisord.log

 

Do purevpn support incoming ports? If not then your downloads will be slow at best. If they do support incoming ports then you will need to manually configure deluge to use it.

 

How do you check whether a provider supports incoming ports? I've tried asking FrootVPN (for example), which incoming ports they use but they just told me the port for OpenVPN which is 1194

Share this post


Link to post

Hi

 

I have been using Newshosting as a VPN for about a year and decided to move to PureVPN as I got a good deal. I can get connected but nothing downloads even the checkmytorrentip. I am using a server that PureVPN states is not blocked for p2p so it should work.

Any ideas?

Attached is my supervisord.log

 

Do purevpn support incoming ports? If not then your downloads will be slow at best. If they do support incoming ports then you will need to manually configure deluge to use it.

 

How do you check whether a provider supports incoming ports? I've tried asking FrootVPN (for example), which incoming ports they use but they just told me the port for OpenVPN which is 1194

 

A bit of googling around and then if no joy a simple email asking them outright, if they say something like frootvpn did then they are either technically stupid or just don't want to answer the question. Airvpn or pia recommended both support incoming port.

Share this post


Link to post

Hi guys,

 

I just tried to update deluge vpn - wasnt paying attention and I noticed that it had dissapeared.  Strange I thought - manually reinstalled it - reset it up but then got this error

 

*****

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-delugevpn" --net="bridge" --privileged="true" -e VPN_ENABLED="yes" -e VPN_USER="vpn username" -e VPN_PASS="vpn password" -e VPN_REMOTE="nl.privateinternetaccess.com" -e VPN_PORT="1194" -e VPN_PROV="airvpn" -e ENABLE_PRIVOXY="no" -e LAN_RANGE="192.168.0.1-192.168.0.254" -e TZ="Europe/London" -p 8112:8112/tcp -p 58846:58846/tcp -p 8118:8118/tcp -v "/mnt/cache/appdata/deluge":"/config":rw -v "/mnt/cache/downloads":"/data":rw binhex/arch-delugevpn

Unable to find image 'username:latest' locally

Pulling repository username

Error: image library/username:latest not found

 

The command finished successfully!

 

******

 

Help please :-)

 

I'm having the same issue (Error: image library/username:latest not found).

Share this post


Link to post

I just signed up for a 3 day trial with airvpn and I can't get it to work with this docker

 

I followed all of the instructions here: http://lime-technology.com/forum/index.php?topic=45812.0

 

and copied over my ovpn file. It didn't work, so I tried to get another ovpn file from the config generator but that isn't connecting either. As of right now I cant get into the webgui or the desktop client

 

This is what I see in my log:

 

[info] Env var PUID defined as 99
[info] Env var PGID defined as 100
[info] Permissions already set for /config
[info] Starting Supervisor...
2016-03-28 23:39:32,465 CRIT Set uid to user 0
2016-03-28 23:39:32,465 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2016-03-28 23:39:32,467 INFO supervisord started with pid 12
2016-03-28 23:39:33,469 INFO spawned: 'privoxy' with pid 15
2016-03-28 23:39:33,469 INFO spawned: 'start' with pid 16
2016-03-28 23:39:33,470 INFO spawned: 'webui' with pid 17
2016-03-28 23:39:33,471 INFO spawned: 'deluge' with pid 18
2016-03-28 23:39:33,475 DEBG 'privoxy' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-03-28 23:39:33,475 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-03-28 23:39:33,475 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-03-28 23:39:33,475 DEBG 'privoxy' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-03-28 23:39:33,476 DEBG 'deluge' stdout output:
[info] VPN enabled, configuring Deluge...

2016-03-28 23:39:33,476 DEBG 'deluge' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-03-28 23:39:33,477 DEBG 'start' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2016-03-28 23:39:33,483 DEBG 'start' stdout output:
[info] VPN provider defined as airvpn
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn
/config/openvpn/AirVPN_Sweden_UDP-443.ovpn
/config/openvpn/AirVPN_Switzerland_TCP-443.ovpn

2016-03-28 23:39:33,483 DEBG 'start' stderr output:
/root/start.sh: line 50: /config/openvpn/openvpn.ovpn
/config/openvpn/AirVPN_Sweden_UDP-443.ovpn
/config/openvpn/AirVPN_Switzerland_TCP-443.ovpn: No such file or directory

2016-03-28 23:39:33,483 DEBG 'start' stdout output:
[info] Env vars not defined for remote host, port and protocol, will parse existing entries from ovpn file...

2016-03-28 23:39:33,484 DEBG 'start' stderr output:
cat: '/config/openvpn/openvpn.ovpn'$'\n''/config/openvpn/AirVPN_Sweden_UDP-443.ovpn'$'\n''/config/openvpn/AirVPN_Switzerland_TCP-443.ovpn': No such file or directory

2016-03-28 23:39:33,488 DEBG 'start' stderr output:
cat: '/config/openvpn/openvpn.ovpn'$'\n''/config/openvpn/AirVPN_Sweden_UDP-443.ovpn'$'\n''/config/openvpn/AirVPN_Switzerland_TCP-443.ovpn': No such file or directory

2016-03-28 23:39:33,492 DEBG 'start' stderr output:
cat: '/config/openvpn/openvpn.ovpn'$'\n''/config/openvpn/AirVPN_Sweden_UDP-443.ovpn'$'\n''/config/openvpn/AirVPN_Switzerland_TCP-443.ovpn': No such file or directory

2016-03-28 23:39:33,495 DEBG 'start' stderr output:
cat: '/config/openvpn/openvpn.ovpn'$'\n''/config/openvpn/AirVPN_Sweden_UDP-443.ovpn'$'\n''/config/openvpn/AirVPN_Switzerland_TCP-443.ovpn': No such file or directory

2016-03-28 23:39:33,499 DEBG 'start' stdout output:
[crit] VPN provider remote gateway not defined, exiting...

2016-03-28 23:39:33,499 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 47151743109960 for <Subprocess at 47151742974288 with name start in state RUNNING> (stdout)>
2016-03-28 23:39:33,499 DEBG fd 14 closed, stopped monitoring <POutputDispatcher at 47151743110392 for <Subprocess at 47151742974288 with name start in state RUNNING> (stderr)>
2016-03-28 23:39:33,499 INFO exited: start (exit status 1; not expected)
2016-03-28 23:39:33,499 DEBG received SIGCLD indicating a child quit
2016-03-28 23:39:34,500 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-28 23:39:34,500 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

The only point at which i deviated from the guide was the vpn port. I looked in the ovpn file and instead of 1194 I see port 443

Share this post


Link to post

You have two ovpn files, delete one and then restart, if you're still having issues then post your supervisord.log file

Share this post


Link to post

How easy is it to move from the non vpn version to this? is it just a question of using the same config folder and ports then setting up VPN files etc?

Share this post


Link to post

I have figured out my problem with low speed now.

We have ADSL, but the modem did not open the ports I wanted, before I changed to VDSL interface (sounds wierd, but it was my internet provider who told me to try this), and now I have full speed on this docker :)

Share this post


Link to post

Hoping binhex or someone can help out here.  I've been running this docker forever and not had any issues with it.  Today I wanted to modify which cores it ran on so I stopped the docker (after shutting down the daemon through web console), clicked edit, changed the cores it is running on, and clicked apply.  That cause the docker to pull some image updates and after it completed, Deluge no longer launches correctly and web console never loads.  Here is a log of the docker when it starts:

 

usermod: no changes
[info] Env var PUID defined as 99
[info] Env var PGID defined as 100
[info] Permissions already set for /config
[info] Starting Supervisor...
2016-03-31 23:24:42,488 CRIT Set uid to user 0
2016-03-31 23:24:42,495 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2016-03-31 23:24:42,501 INFO supervisord started with pid 13
2016-03-31 23:24:43,504 INFO spawned: 'privoxy' with pid 16
2016-03-31 23:24:43,505 INFO spawned: 'start' with pid 17
2016-03-31 23:24:43,507 INFO spawned: 'webui' with pid 18
2016-03-31 23:24:43,508 INFO spawned: 'deluge' with pid 19
2016-03-31 23:24:43,524 DEBG 'privoxy' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-03-31 23:24:43,524 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-03-31 23:24:43,524 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-03-31 23:24:43,531 DEBG 'privoxy' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-03-31 23:24:43,536 DEBG 'deluge' stdout output:
[info] VPN enabled, configuring Deluge...

2016-03-31 23:24:43,537 DEBG 'deluge' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-03-31 23:24:43,541 DEBG 'start' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2016-03-31 23:24:43,570 DEBG 'start' stdout output:
[info] VPN provider defined as pia
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2016-03-31 23:24:43,573 DEBG 'start' stdout output:
[info] Env vars not defined for remote host, port and protocol, will parse existing entries from ovpn file...

2016-03-31 23:24:43,609 DEBG 'start' stdout output:
[info] VPN provider remote gateway defined as ca-toronto.privateinternetaccess.com
[info] VPN provider remote port defined as 1194
[info] VPN provider remote protocol defined as udp

2016-03-31 23:24:43,616 DEBG 'start' stdout output:
[info] VPN provider username defined as pXXXXXXX

2016-03-31 23:24:43,620 DEBG 'start' stdout output:
[info] VPN provider password defined as XXXXXXXXXX

2016-03-31 23:24:43,635 DEBG 'start' stdout output:
[info] Default route for container is 172.17.42.1

2016-03-31 23:24:43,654 DEBG 'start' stdout output:
[crit] LAN network not defined, please specify via env variable LAN_NETWORK

2016-03-31 23:24:43,655 DEBG fd 9 closed, stopped monitoring (stdout)>
2016-03-31 23:24:43,655 DEBG fd 14 closed, stopped monitoring (stderr)>
2016-03-31 23:24:43,655 INFO exited: start (exit status 1; not expected)
2016-03-31 23:24:43,655 DEBG received SIGCLD indicating a child quit
2016-03-31 23:24:44,656 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-31 23:24:44,656 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

Nothing else ever follows that and the console never loads. 

 

 

edit:

Ok so it looks like the environment variable LAN_RANGE was replaced with LAN_NETWORK at some point and that is where the problem seems to be.  I tried simply renaming LAN_RANGE to LAN_NETWORK but then I get the following errors, so I assume the syntax was changed as well:


2016-03-31 23:35:34,071 DEBG 'start' stdout output:
[info] Default route for container is 172.17.42.1

2016-03-31 23:35:34,081 DEBG 'start' stdout output:
[info] [u][b]Adding 192.168.0.1-192.168.0.254 as route via docker eth0[/b][/u]

2016-03-31 23:35:34,082 DEBG 'start' stderr output:
[u][b]Error: an inet prefix is expected rather than "192.168.0.1-192.168.0.254".[/b][/u]

 

Now it seems to at least launch and download, but the above message has me concerned it is messing up the routing table and potentially not using VPN.

 

Here's an extended excerpt showing some concerning messages:

2016-03-31 23:35:33,259 DEBG 'start' stdout output:
[info] Env vars not defined for remote host, port and protocol, will parse existing entries from ovpn file...

2016-03-31 23:35:34,045 DEBG 'start' stdout output:
[info] VPN provider remote gateway defined as ca-toronto.privateinternetaccess.com
[info] VPN provider remote port defined as 1194
[info] VPN provider remote protocol defined as udp

2016-03-31 23:35:34,053 DEBG 'start' stdout output:
[info] VPN provider username defined as pXXXXXXX

2016-03-31 23:35:34,057 DEBG 'start' stdout output:
[info] VPN provider password defined as XXXXXXXXXX

2016-03-31 23:35:34,071 DEBG 'start' stdout output:
[info] Default route for container is 172.17.42.1

2016-03-31 23:35:34,081 DEBG 'start' stdout output:
[u][b][info] Adding 192.168.0.1-192.168.0.254 as route via docker eth[/b][/u]0

2016-03-31 23:35:34,082 DEBG 'start' stderr output:
[u][b]Error: an inet prefix is expected rather than "192.168.0.1-192.168.0.254"[/b][/u].

2016-03-31 23:35:34,082 DEBG 'start' stdout output:
[info] ip route defined as follows...
--------------------

2016-03-31 23:35:34,083 DEBG 'start' stdout output:
default via 172.17.42.1 dev eth0

2016-03-31 23:35:34,083 DEBG 'start' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.20
--------------------

2016-03-31 23:35:34,090 DEBG 'start' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2016-03-31 23:35:35,092 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-31 23:35:35,092 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-31 23:36:14,188 DEBG 'start' stderr output:
[u][b]iptables v1.4.21: host/network `192.168.0.1-192.168.0.254' not found
Try `iptables -h' or 'iptables --help' for more information.

2016-03-31 23:36:14,205 DEBG 'start' stderr output:
iptables v1.4.21: host/network `192.168.0.1-192.168.0.254' not found
Try `iptables -h' or 'iptables --help' for more information.[/b][/u]

2016-03-31 23:36:14,209 DEBG 'start' stdout output:
[info] iptables defined as follows...
--------------------

2016-03-31 23:36:14,210 DEBG 'start' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2016-03-31 23:36:14,211 DEBG 'start' stdout output:
--------------------

Share this post


Link to post

Hoping binhex or someone can help out here.  I've been running this docker forever and not had any issues with it.  Today I wanted to modify which cores it ran on so I stopped the docker (after shutting down the daemon through web console), clicked edit, changed the cores it is running on, and clicked apply.  That cause the docker to pull some image updates and after it completed, Deluge no longer launches correctly and web console never loads.  Here is a log of the docker when it starts:

 

usermod: no changes
[info] Env var PUID defined as 99
[info] Env var PGID defined as 100
[info] Permissions already set for /config
[info] Starting Supervisor...
2016-03-31 23:24:42,488 CRIT Set uid to user 0
2016-03-31 23:24:42,495 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2016-03-31 23:24:42,501 INFO supervisord started with pid 13
2016-03-31 23:24:43,504 INFO spawned: 'privoxy' with pid 16
2016-03-31 23:24:43,505 INFO spawned: 'start' with pid 17
2016-03-31 23:24:43,507 INFO spawned: 'webui' with pid 18
2016-03-31 23:24:43,508 INFO spawned: 'deluge' with pid 19
2016-03-31 23:24:43,524 DEBG 'privoxy' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-03-31 23:24:43,524 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-03-31 23:24:43,524 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-03-31 23:24:43,531 DEBG 'privoxy' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-03-31 23:24:43,536 DEBG 'deluge' stdout output:
[info] VPN enabled, configuring Deluge...

2016-03-31 23:24:43,537 DEBG 'deluge' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-03-31 23:24:43,541 DEBG 'start' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2016-03-31 23:24:43,570 DEBG 'start' stdout output:
[info] VPN provider defined as pia
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2016-03-31 23:24:43,573 DEBG 'start' stdout output:
[info] Env vars not defined for remote host, port and protocol, will parse existing entries from ovpn file...

2016-03-31 23:24:43,609 DEBG 'start' stdout output:
[info] VPN provider remote gateway defined as ca-toronto.privateinternetaccess.com
[info] VPN provider remote port defined as 1194
[info] VPN provider remote protocol defined as udp

2016-03-31 23:24:43,616 DEBG 'start' stdout output:
[info] VPN provider username defined as pXXXXXXX

2016-03-31 23:24:43,620 DEBG 'start' stdout output:
[info] VPN provider password defined as XXXXXXXXXX

2016-03-31 23:24:43,635 DEBG 'start' stdout output:
[info] Default route for container is 172.17.42.1

2016-03-31 23:24:43,654 DEBG 'start' stdout output:
[crit] LAN network not defined, please specify via env variable LAN_NETWORK

2016-03-31 23:24:43,655 DEBG fd 9 closed, stopped monitoring (stdout)>
2016-03-31 23:24:43,655 DEBG fd 14 closed, stopped monitoring (stderr)>
2016-03-31 23:24:43,655 INFO exited: start (exit status 1; not expected)
2016-03-31 23:24:43,655 DEBG received SIGCLD indicating a child quit
2016-03-31 23:24:44,656 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-31 23:24:44,656 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

Nothing else ever follows that and the console never loads. 

 

 

edit:

Ok so it looks like the environment variable LAN_RANGE was replaced with LAN_NETWORK at some point and that is where the problem seems to be.  I tried simply renaming LAN_RANGE to LAN_NETWORK but then I get the following errors, so I assume the syntax was changed as well:


2016-03-31 23:35:34,071 DEBG 'start' stdout output:
[info] Default route for container is 172.17.42.1

2016-03-31 23:35:34,081 DEBG 'start' stdout output:
[info] [u][b]Adding 192.168.0.1-192.168.0.254 as route via docker eth0[/b][/u]

2016-03-31 23:35:34,082 DEBG 'start' stderr output:
[u][b]Error: an inet prefix is expected rather than "192.168.0.1-192.168.0.254".[/b][/u]

 

Now it seems to at least launch and download, but the above message has me concerned it is messing up the routing table and potentially not using VPN.

 

Here's an extended excerpt showing some concerning messages:

2016-03-31 23:35:33,259 DEBG 'start' stdout output:
[info] Env vars not defined for remote host, port and protocol, will parse existing entries from ovpn file...

2016-03-31 23:35:34,045 DEBG 'start' stdout output:
[info] VPN provider remote gateway defined as ca-toronto.privateinternetaccess.com
[info] VPN provider remote port defined as 1194
[info] VPN provider remote protocol defined as udp

2016-03-31 23:35:34,053 DEBG 'start' stdout output:
[info] VPN provider username defined as pXXXXXXX

2016-03-31 23:35:34,057 DEBG 'start' stdout output:
[info] VPN provider password defined as XXXXXXXXXX

2016-03-31 23:35:34,071 DEBG 'start' stdout output:
[info] Default route for container is 172.17.42.1

2016-03-31 23:35:34,081 DEBG 'start' stdout output:
[u][b][info] Adding 192.168.0.1-192.168.0.254 as route via docker eth[/b][/u]0

2016-03-31 23:35:34,082 DEBG 'start' stderr output:
[u][b]Error: an inet prefix is expected rather than "192.168.0.1-192.168.0.254"[/b][/u].

2016-03-31 23:35:34,082 DEBG 'start' stdout output:
[info] ip route defined as follows...
--------------------

2016-03-31 23:35:34,083 DEBG 'start' stdout output:
default via 172.17.42.1 dev eth0

2016-03-31 23:35:34,083 DEBG 'start' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.20
--------------------

2016-03-31 23:35:34,090 DEBG 'start' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2016-03-31 23:35:35,092 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-31 23:35:35,092 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-31 23:36:14,188 DEBG 'start' stderr output:
[u][b]iptables v1.4.21: host/network `192.168.0.1-192.168.0.254' not found
Try `iptables -h' or 'iptables --help' for more information.

2016-03-31 23:36:14,205 DEBG 'start' stderr output:
iptables v1.4.21: host/network `192.168.0.1-192.168.0.254' not found
Try `iptables -h' or 'iptables --help' for more information.[/b][/u]

2016-03-31 23:36:14,209 DEBG 'start' stdout output:
[info] iptables defined as follows...
--------------------

2016-03-31 23:36:14,210 DEBG 'start' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2016-03-31 23:36:14,211 DEBG 'start' stdout output:
--------------------

 

See FAQ q7 post #2 of this thread

Share this post


Link to post

Hi,

 

getting this in my DelgueVPN log and download speeds are non existent.

 

2016-04-01 07:59:49,316 DEBG 'deluge' stdout output:
[warn] PIA incoming port is not an integer, downloads will be slow, check if remote gateway supports port forwarding

 

Is it as simple at forwarding the port with my VPN (which really doesn't seem that simple), or is it something else? I should also add that in the log, it states the incoming deluge port is 6881, and the incoming VPN port is blank, there is nothing there.

 

Thanks.

Share this post


Link to post

Hi,

 

getting this in my DelgueVPN log and download speeds are non existent.

 

2016-04-01 07:59:49,316 DEBG 'deluge' stdout output:
[warn] PIA incoming port is not an integer, downloads will be slow, check if remote gateway supports port forwarding

 

Is it as simple at forwarding the port with my VPN (which really doesn't seem that simple), or is it something else? I should also add that in the log, it states the incoming deluge port is 6881, and the incoming VPN port is blank, there is nothing there.

 

Thanks.

 

firstly you must be setting the vpn provider to PIA for it to be attempting to auto set the incoming port (pia supported only), if you are using pia then you need to use a gateway that supports port forwarding, if your not using pia then you need to change the vpn provider to "custom" and figure out what the incoming port is for your vpn provider.

Share this post


Link to post

Hi,

 

getting this in my DelgueVPN log and download speeds are non existent.

 

2016-04-01 07:59:49,316 DEBG 'deluge' stdout output:
[warn] PIA incoming port is not an integer, downloads will be slow, check if remote gateway supports port forwarding

 

Is it as simple at forwarding the port with my VPN (which really doesn't seem that simple), or is it something else? I should also add that in the log, it states the incoming deluge port is 6881, and the incoming VPN port is blank, there is nothing there.

 

Thanks.

 

firstly you must be setting the vpn provider to PIA for it to be attempting to auto set the incoming port (pia supported only), if you are using pia then you need to use a gateway that supports port forwarding, if your not using pia then you need to change the vpn provider to "custom" and figure out what the incoming port is for your vpn provider.

 

Hi, thanks for that.

I am using PIA, but wasn't using a port forwarding enabled gateway, changed that now.

Didn't realise that PIA would automatically forward a port on an enabled gateway, and especially didn't think that DelugeVPN would automagically change the incoming port to the correct one.

Great, and thanks for the help!

:)

Share this post


Link to post

Hi all, I'm not having a lot of luck getting the WebGUI to load (getting ERR_CONNECTION_TIMED_OUT), sure I'm doing something very obvious incorrectly.

 

I installed the docker and set config to:

 

/mnt/cache/appdata/

 

And data to:

 

/mnt/user/downloads/

 

I set my PIA username and password and set VPN_PROV to pia, besides that left everything else as default. I'm unsure what LAN_NETWORK should be pointing to, should it be my default gateway?

 

I have uninstalled/reinstalled the docker, cleared my appdata directory completely, in case something was clogging it up, not sure if I have mis configured or something is blocking it. I haven't made any changes to my router.

 

What's the best way for me to debug? Have to admit I'm still grappling with the basics here with unRAID and Linux!

Share this post


Link to post

Hi all, I'm not having a lot of luck getting the WebGUI to load (getting ERR_CONNECTION_TIMED_OUT), sure I'm doing something very obvious incorrectly.

 

I installed the docker and set config to:

 

/mnt/cache/appdata/

 

And data to:

 

/mnt/user/downloads/

 

I set my PIA username and password and set VPN_PROV to pia, besides that left everything else as default. I'm unsure what LAN_NETWORK should be pointing to, should it be my default gateway?

 

I have uninstalled/reinstalled the docker, cleared my appdata directory completely, in case something was clogging it up, not sure if I have mis configured or something is blocking it. I haven't made any changes to my router.

 

What's the best way for me to debug? Have to admit I'm still grappling with the basics here with unRAID and Linux!

 

LAN_NETWORK is the CIDR notation of the ip range you are using. So for instance, if your home network is 192.168.0.0 to 192.168.0.8 (or whatever), you will put 192.168.0.0 followed by the subnet. So in the end, you would end up with something like 192.168.0.0/24 (assuming your subnet is 255.255.255.0), and that is what you would put in for LAN_NETWORK. Your gateway address is most probably on 192.168.0.1 (something like that), so you don't use that.

Share this post


Link to post

LAN_NETWORK is the CIDR notation of the ip range you are using. So for instance, if your home network is 192.168.0.0 to 192.168.0.8 (or whatever), you will put 192.168.0.0 followed by the subnet. So in the end, you would end up with something like 192.168.0.0/24 (assuming your subnet is 255.255.255.0), and that is what you would put in for LAN_NETWORK. Your gateway address is most probably on 192.168.0.1 (something like that), so you don't use that.

 

Thanks Jimmy, that did the trick.

Share this post


Link to post

Hi!

I have a very frustrating issue with my Deluge VPN. I download a file, tell it to go to a specific folder (/data/Shows for example) and I search for the file after it is downloaded and it isn't there. I __think__ this mostly happens after I start a download on file X, add another torrent, file Y, and set it to download to a different directory than where X is being downloaded. It seems to get confused and copies Y into X's directory, possibly. Not always sure where it goes, I can't find it until I move it again.

 

I have my media organized in separate folders for Movies, Music, Shows, etc. inside a larger folder that I have mapped to this container's data folder, so I am assuming I should use /data/Movies (for example) for the movie folder. This workers, but it looks like Deluge gets totally confused when I start multiple torrents that are supposed to download into different directories. Then, I have to tell it to move the torrent into the proper directory, but this takes a long time for large files, since it has to move all the bits over (not just references).

Am I doing something wrong? How do I make it so the files go into the exact place I tell them to when I first add the torrent file to Deluge?

 

 

Share this post


Link to post

Hi!

I have a very frustrating issue with my Deluge VPN. I download a file, tell it to go to a specific folder (/data/Shows for example) and I search for the file after it is downloaded and it isn't there. I __think__ this mostly happens after I start a download on file X, add another torrent, file Y, and set it to download to a different directory than where X is being downloaded. It seems to get confused and copies Y into X's directory, possibly. Not always sure where it goes, I can't find it until I move it again.

 

I have my media organized in separate folders for Movies, Music, Shows, etc. inside a larger folder that I have mapped to this container's data folder, so I am assuming I should use /data/Movies (for example) for the movie folder. This workers, but it looks like Deluge gets totally confused when I start multiple torrents that are supposed to download into different directories. Then, I have to tell it to move the torrent into the proper directory, but this takes a long time for large files, since it has to move all the bits over (not just references).

Am I doing something wrong? How do I make it so the files go into the exact place I tell them to when I first add the torrent file to Deluge?

 

The rule of thumb is, don't let Deluge dictate what to do with your media but rather, let the other guys to do it as they properly should (SAB, Couch, Sonaar, etc..). So in essence, you need to remove any media management settings from your Deluge preferences (in its GUI) and only leave the "allow remote control/connection" thing activated. Then, fine tune your other guys to tell Deluge what to do with each specific file passed on to it when applicable. Once you have done that, you'll notice that each file given to Deluge will be populated with specific instructions in the detail tab, one by one.

 

Good Luck and adjust one at a time, you'll get there eventually ;)

 

Edit: You obviously need to make sure your Deluge docker setup contains mappings that "drive" with your fetchers, so they speak the same "language". So if your fetching docker has a mapping for TVSHOWS=TV, do the same for Deluge so it knows what your fetcher is talking about when its told to put it there.

Share this post


Link to post

I've got what I'm hoping is a simple question here.

 

I  have had two forced reboots (hardware issue that I think I have resolved) but when I get everything running again, and I finally get to the point where I can get into DelugeVPN, my Deluge settings seem to be gone and I have to recreate them.

 

Is there some sort of commit or something I need to do to get my settings to stick in the event of a reboot?

Share this post


Link to post

Start deluge, set things up, then stop the deluge docker. This should write the config to the appdata folder. Perhaps you've got it all setup and are not writing the settings from RAM to Disk as a result of the hard reboot.

Share this post


Link to post

Hi!

I have a very frustrating issue with my Deluge VPN. I download a file, tell it to go to a specific folder (/data/Shows for example) and I search for the file after it is downloaded and it isn't there. I __think__ this mostly happens after I start a download on file X, add another torrent, file Y, and set it to download to a different directory than where X is being downloaded. It seems to get confused and copies Y into X's directory, possibly. Not always sure where it goes, I can't find it until I move it again.

 

I have my media organized in separate folders for Movies, Music, Shows, etc. inside a larger folder that I have mapped to this container's data folder, so I am assuming I should use /data/Movies (for example) for the movie folder. This workers, but it looks like Deluge gets totally confused when I start multiple torrents that are supposed to download into different directories. Then, I have to tell it to move the torrent into the proper directory, but this takes a long time for large files, since it has to move all the bits over (not just references).

Am I doing something wrong? How do I make it so the files go into the exact place I tell them to when I first add the torrent file to Deluge?

 

The rule of thumb is, don't let Deluge dictate what to do with your media but rather, let the other guys to do it as they properly should (SAB, Couch, Sonaar, etc..). So in essence, you need to remove any media management settings from your Deluge preferences (in its GUI) and only leave the "allow remote control/connection" thing activated. Then, fine tune your other guys to tell Deluge what to do with each specific file passed on to it when applicable. Once you have done that, you'll notice that each file given to Deluge will be populated with specific instructions in the detail tab, one by one.

 

Good Luck and adjust one at a time, you'll get there eventually ;)

 

Edit: You obviously need to make sure your Deluge docker setup contains mappings that "drive" with your fetchers, so they speak the same "language". So if your fetching docker has a mapping for TVSHOWS=TV, do the same for Deluge so it knows what your fetcher is talking about when its told to put it there.

Thanks for your answer. I don't actually have any of those remote apps you are referring to. I use private trackers and always manually add all torrents. The issue I have is when I manually (in the details when adding a .torrent) set the desired destination, Deluge seems to  disobey this.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now