trying to switch my rutorrentVPN from a cheap VPN (that was working, but not provide any Port Forwarding for Torrenting) to AirVPN. 

 

I have my AirVPN.opvpn file, then I remove VPN_USER and VPN_PASS, change the VPN_PORT to match the included port in the .opvpn file (443), change the VPN_REMOTE to match too.

 

Seems the docker doesn't start OK...  Any idea ?

 

** EDIT **

 

Ok, I tried starting from scratch.  Still can't make it work!  tried both rtorrentVPN and DelugeVPN. 

 

1. using AirVPN, is that right I don't provide VPN_USER and VPN_PASS ?

2. How can I tell the Docker what Ports are Forwarded by AirVPN (in my case, I forward 3004,3005,3006,3007 and 3008).  I suppose it need to only be added to the IPtables rules, but isn't there a Variable to edit for that ?

3. True that doesn't need to forward ports on my Router (since it's in the VPN) ?

 

 

I have the same kind of thing in my Log too, and it just doesn't work.

 

Since you knew already how to use AirVPN, can you reply my questions ?

 

1. Do I need to specify a User/pass or only providing the .opvpn is enough ?

2. How to tell the Docker what are the AirVPN forwarded ports ?

 

 

Thanks,

think its a hiccup with latest build - me too, mine was working for months - my internet been down for just under a month now its back and an update or two later and it no work!  Am sure I have just done something stupid! lol

 

So I deleted the old and isntalled from scratch now I get this but no access to web gui - anyone point me in the right direction?

 

 

Created by...

___.  .__      .__                 

\_ |__ |__| ____ |  |__  ____ ___  ___

| __ \|  |/    \|  |  \_/ __ \\  \/  /

| \_\ \  |  |  \  Y  \  ___/ >    <

|___  /__|___|  /___|  /\___  >__/\_ \

    \/        \/    \/    \/      \/

  https://hub.docker.com/u/binhex/

 

2016-10-21 01:00:49.540854 [info] Looks like the host is running unRAID

2016-10-21 01:00:49.562191 [info] PUID defined as '99'

2016-10-21 01:00:49.584304 [info] PGID defined as '100'

2016-10-21 01:00:49.640917 [info] Permissions already set for /config and /data

2016-10-21 01:00:49.662426 [info] VPN_ENABLED defined as 'yes'

2016-10-21 01:00:49.683655 [info] VPN_PROV defined as 'airvpn'

2016-10-21 01:00:49.705407 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'

2016-10-21 01:00:49.727014 [info] VPN_PORT defined as '443'

2016-10-21 01:00:49.748833 [info] VPN_PROTOCOL defined as 'udp'

2016-10-21 01:00:49.770604 [info] LAN_NETWORK defined as '192.168.0.0/24'

2016-10-21 01:00:49.792518 [info] VPN_DEVICE_TYPE defined as 'tun'

2016-10-21 01:00:49.813961 [info] STRONG_CERTS defined as 'no'

2016-10-21 01:00:49.835957 [info] ENABLE_PRIVOXY defined as 'no'

2016-10-21 01:00:49.855296 [info] Setting permissions on files/folders inside container...

2016-10-21 01:00:49.876702 [info] Starting Supervisor...

2016-10-21 01:00:49,963 CRIT Set uid to user 0

2016-10-21 01:00:49,963 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2016-10-21 01:00:49,965 INFO supervisord started with pid 1

2016-10-21 01:00:50,967 INFO spawned: 'start-script' with pid 85

2016-10-21 01:00:50,968 INFO spawned: 'webui-script' with pid 86

2016-10-21 01:00:50,968 INFO spawned: 'deluge-script' with pid 87

2016-10-21 01:00:50,969 INFO spawned: 'privoxy-script' with pid 88

2016-10-21 01:00:50,973 DEBG 'start-script' stdout output:

[info] VPN is enabled, beginning configuration of VPN

 

2016-10-21 01:00:50,973 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2016-10-21 01:00:50,973 INFO success: webui-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2016-10-21 01:00:50,973 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2016-10-21 01:00:50,973 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2016-10-21 01:00:50,973 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47556057338800 for <Subprocess at 47556057212616 with name privoxy-script in state RUNNING> (stderr)>

2016-10-21 01:00:50,973 DEBG 'privoxy-script' stdout output:

[info] Privoxy set to disabled

 

2016-10-21 01:00:50,973 INFO exited: privoxy-script (exit status 0; expected)

2016-10-21 01:00:50,974 DEBG received SIGCLD indicating a child quit

2016-10-21 01:00:50,975 DEBG 'deluge-script' stdout output:

[info] deluge config file already exists, skipping copy

 

2016-10-21 01:00:50,976 DEBG 'deluge-script' stdout output:

[info] VPN is enabled, checking VPN tunnel local ip is valid

 

2016-10-21 01:00:50,978 DEBG 'start-script' stdout output:

[info] VPN config file (ovpn extension) is located at /config/openvpn/AirVPN_United-Kingdom_UDP-443.ovpn

 

2016-10-21 01:00:50,994 DEBG 'start-script' stdout output:

[info] Default route for container is 172.17.0.1

[info] Setting permissions recursively on /config/openvpn...

 

2016-10-21 01:00:51,000 DEBG 'start-script' stdout output:

[info] Adding 192.168.0.0/24 as route via docker eth0

 

2016-10-21 01:00:51,001 DEBG 'start-script' stdout output:

[info] ip route defined as follows...

--------------------

 

2016-10-21 01:00:51,001 DEBG 'start-script' stdout output:

default via 172.17.0.1 dev eth0

172.17.0.0/16 dev eth0  proto kernel  scope link  src 172.17.0.5

192.168.0.0/24 via 172.17.0.1 dev eth0

 

2016-10-21 01:00:51,001 DEBG 'start-script' stdout output:

--------------------

 

2016-10-21 01:00:51,003 DEBG 'start-script' stdout output:

[info] iptable_mangle module not supported, attempting to load...

 

2016-10-21 01:00:51,004 DEBG 'start-script' stderr output:

modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.4.23-unRAID

 

2016-10-21 01:00:51,004 DEBG 'start-script' stdout output:

[warn] iptable_mangle module not supported, you will not be able to connect to Deluge webui or Privoxy outside of your LAN

 

2016-10-21 01:00:51,020 DEBG 'start-script' stdout output:

[info] iptables defined as follows...

--------------------

 

2016-10-21 01:00:51,020 DEBG 'start-script' 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 443 -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 -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -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 443 -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 -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -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-10-21 01:00:51,021 DEBG 'start-script' stdout output:

--------------------

[info] Starting OpenVPN...

 

2016-10-21 01:00:51,023 DEBG 'start-script' stdout output:

Fri Oct 21 01:00:51 2016 OpenVPN 2.3.11 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 12 2016

Fri Oct 21 01:00:51 2016 library versions: OpenSSL 1.0.2h  3 May 2016, LZO 2.09

 

2016-10-21 01:00:51,023 DEBG 'start-script' stdout output:

Fri Oct 21 01:00:51 2016 Control Channel Authentication: tls-auth using INLINE static key file

Fri Oct 21 01:00:51 2016 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

Fri Oct 21 01:00:51 2016 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

 

2016-10-21 01:00:51,024 DEBG 'start-script' stdout output:

Fri Oct 21 01:00:51 2016 Socket Buffers: R=[212992->212992] S=[212992->212992]

 

2016-10-21 01:00:51,069 DEBG 'start-script' stdout output:

Fri Oct 21 01:00:51 2016 UDPv4 link local: [undef]

Fri Oct 21 01:00:51 2016 UDPv4 link remote: [AF_INET]46.166.186.251:443

 

its not a "hiccup" in the latest build, its a change from parsing ovpn file to using the env variables, this was introduced about 2 months ago, i wont go into the pro's and con's of this right now but thats how it is at the moment, so it looks like you havent updated since the change to this up until now and thus it appears to be the recent changes that are the problem

 

so the problem is you have never needed to define the env variables correctly and now your getting tripped up by this, this is the problem in short:-

 

VPN_REMOTE defined as 'nl.privateinternetaccess.com'

 

as you've stated earlier your using airvpn so im pretty sure this is incorrect :-), please take a look at your ovpn file and copy and paste the value for the remote line in place of the above (left click, edit, select advanced view to see the values).

 

trying to switch my rutorrentVPN from a cheap VPN (that was working, but not provide any Port Forwarding for Torrenting) to AirVPN. 

 

I have my AirVPN.opvpn file, then I remove VPN_USER and VPN_PASS, change the VPN_PORT to match the included port in the .opvpn file (443), change the VPN_REMOTE to match too.

 

Seems the docker doesn't start OK...  Any idea ?

 

** EDIT **

 

Ok, I tried starting from scratch.  Still can't make it work!  tried both rtorrentVPN and DelugeVPN. 

 

1. using AirVPN, is that right I don't provide VPN_USER and VPN_PASS ?

2. How can I tell the Docker what Ports are Forwarded by AirVPN (in my case, I forward 3004,3005,3006,3007 and 3008).  I suppose it need to only be added to the IPtables rules, but isn't there a Variable to edit for that ?

3. True that doesn't need to forward ports on my Router (since it's in the VPN) ?

 

please attach the supervisord.log file, without this im just guessing.

Finaly, it worked by itself.  But, it's super-slow.  It doesn't get pass 800KB/sec... on my previous "cheap" VPN included in my Usenet, I hit 22MB/Sec (my connexion can get 110MB/sec, it's Gigabit Internet). 

 

I thought AirVPN would be an Upgrade

 

Also, I took AirVPN just for the sole option of the "Remote Port Forwarding" they offer.  It seems that I cannot set the forwarded ports anywhere ?  ex: I forwarded port 3004-3008 in AirVPN site, so those are my "incoming" ports, to be used to be "connectable" on torrent trackers.  I tried setting that in the rTorrent UI, but since the iptables doesn't open them, it just don't work

 

How can I have it working? Do I need to modify a script in the docker ?

 

Thank you !

Finaly, it worked by itself.  But, it's super-slow.  It doesn't get pass 800KB/sec... on my previous "cheap" VPN included in my Usenet, I hit 22MB/Sec (my connexion can get 110MB/sec, it's Gigabit Internet). 

 

I thought AirVPN would be an Upgrade

 

Also, I took AirVPN just for the sole option of the "Remote Port Forwarding" they offer.  It seems that I cannot set the forwarded ports anywhere ?  ex: I forwarded port 3004-3008 in AirVPN site, so those are my "incoming" ports, to be used to be "connectable" on torrent trackers.  I tried setting that in the rTorrent UI, but since the iptables doesn't open them, it just don't work

 

How can I have it working? Do I need to modify a script in the docker ?

 

Thank you !

 

you dont need to define the incoming port using iptables, all ports in and out are permitted for the vpn tunnel. you now need to configure the application (in your case rtorrent) to use the port, there are a lot of guides on how to do this on the internet, if you cant figure it out then let me know. please can i request any further conversations regards rtorrent are done in the rtorrent support thread to keep this one clean, link to rtorrent support thread:- http://lime-technology.com/forum/index.php?topic=47832.0

I already set in the rtorrent UI the Incoming Ports of 3004-3008.  But, it is still reported as "not connectable".  With PIA, you do a search and set the port.

 

It seems that ports I set are resetted at each start of the docker (they don't stick).  Is there a trick to make them stick ?

 

Here is my settings, but if I restart the docker, they go back to default.

With PIA, delugeVPN configures it all for you.

should have take PIA... AirVPN seems slow and it would have been easier   Paid 72$CAD for the full year

should have take PIA... AirVPN seems slow and it would have been easier   Paid 72$CAD for the full year

Refund policy?

It seems that ports I set are resetted at each start of the docker (they don't stick).  Is there a trick to make them stick ?

 

contrary to popular belief, rutorrent does NOT set any settings for rtorrent, at least not permanently, the only settings that will "stick" are settings for rutorrent (as in the web ui), if you want to modify rtorrent settings and have them be persistent you will need to crack open your favorite text editor (for the love of god dont use notepad) and set it manually and save, the config file should be in the folder /config/rtorrent/.

Hi

 

Been running this container for about a week using PIA.

Downloads works flawless, but I'm having issues with seeding. Both during a download and when the finished download is seeding, it seems to have issues with any kind of uploading.

 

I see peers connect, then disconnect. Some time later they connect again but there is no upload happening. Once in a while a peer actually gets an upload started. Others connect and disconnect still with no file transfer. I have experienced having more then one peer connected with working upload, but it only uploads to one of them at a time. This is the same regardless if it is during downloading or while just seeding.

 

I have checked and verified that the port forwarding done during startup actually has worked and that the port indeed is open. But with hardly anyone being able to get packets from me and only one peer at a time, that's making it hard to keep up any kind of ratio on private trackers.

 

Any ideas?

Been running this container for about a week using PIA.

Any ideas?

Which gateway? The nl seems to work for most people.

Been running this container for about a week using PIA.

Any ideas?

Which gateway? The nl seems to work for most people.

And watch out for private sites, not all allow VPN access and will block if your ip is from a known range.

 

Sent from my SM-G900F using Tapatalk

 

 

Been running this container for about a week using PIA.

Any ideas?

Which gateway? The nl seems to work for most people.

 

Having issues connecting to the Webui. I just noticed this in my supervisord.log:

 

2016-10-21 15:28:07,490 DEBG 'start-script' stdout output:
Fri Oct 21 15:28:07 2016 RESOLVE: Cannot resolve host address: nl.privateinternetaccess.com: Name or service not known

 

All I did was update the container.  Same issue with SABnzbdVPN from binhex after a container update?!

Been running this container for about a week using PIA.

Any ideas?

Which gateway? The nl seems to work for most people.

 

Having issues connecting to the Webui. I just noticed this in my supervisorord.log:

 

2016-10-21 15:28:07,490 DEBG 'start-script' stdout output:
Fri Oct 21 15:28:07 2016 RESOLVE: Cannot resolve host address: nl.privateinternetaccess.com: Name or service not known

 

All I did was update the container.  Same issue with SABnzbdVPN from binhex after a container update?!

Yep I'm seeing the same, looks like a massive dydns outage, it looks to be affecting Google DNS, twitter and github amongst other big players.

 

Sent from my SM-G900F using Tapatalk

 

 

Specify the IP address instead. 46.166.190.180

Specify the IP address instead. 46.166.190.180

 

Thanks...was just about to ask if that would work (plus get the address)!

 

EDIT:  Didn't work for me

 

EDIT 2:  Now it's working...

Been running this container for about a week using PIA.

Any ideas?

Which gateway? The nl seems to work for most people.

And watch out for private sites, not all allow VPN access and will block if your ip is from a known range.

 

Sent from my SM-G900F using Tapatalk

Ok, thanks. I'll do some more testing

And, I've only used the Dutch server so far

My 2c,

 

Sometime in the past 24hrs Deluge VPN stopped being able to resolve "nl.privateinternetaccess.com" (discovered with DEBUG logging enabled) -Without it, Deluge VPN won't properly start and allow access to the Web console unless you turn the VPN function off. I ended up hard coding the current IP for nl.privateinternetaccess.com  as  109.201.135.220 and everything started working. I consider this a temporary fix, as the name resolution is critical when the NL PIA gateway changes IPs....

 

I wonder if this had something to do with the DDoS attack today on some of the Internet's DNS servers?...

 

I actually like the fact that Deluge VPN shuts down when it can't maintain a secure VPN - better safe than sorry!

 

Cheers,

 

BR

 

 

 

 

My 2c,

 

Sometime in the past 24hrs Deluge VPN stopped being able to resolve "nl.privateinternetaccess.com" (discovered with DEBUG logging enabled) -Without it, Deluge VPN won't properly start and allow access to the Web console unless you turn the VPN function off. I ended up hard coding the current IP for nl.privateinternetaccess.com  as  109.201.135.220 and everything started working. I consider this a temporary fix, as the name resolution is critical when the NL PIA gateway changes IPs....

 

I wonder if this had something to do with the DDoS attack today on some of the Internet's DNS servers?...

 

I actually like the fact that Deluge VPN shuts down when it can't maintain a secure VPN - better safe than sorry!

 

Cheers,

 

BR

Look up at my last post, this was due to an issue with dyn DNS which is now resolved. I will be hardening against this in the future by adding in opendns ns which wasnt affected, as well as allowing users to define their own name servers via an optional env var.

 

 

Issue - http://qz.com/816069/dyn-dns-ddos-affecting-twitter-a-massive-attack-took-out-a-swathe-of-the-internet-affecting-twitter-spotify-github-and-more/

 

Sent from my SM-G900F using Tapatalk

 

Woohoo! AirVPN gave me a refund

 

I might try PIA for 1 month first, to see if it's fast enough.

 

I have 940Mbps / 125Mbps internet.  With my current VPN (free included in my Usenet sub), I max the download at 23MB/sec, Upload maybe at 1MB/sec, but i'm not "connectable".

 

the Speedtest on the PIA website give me only about 350Mbps download on the Us-East, I wonder when using the torrent in the rTorrentVPN if I can reach that or it's a limit of the encryption at 23MB/sec (~184Mbps)...

the Speedtest on the PIA website give me only about 350Mbps download on the Us-East, I wonder when using the torrent in the rTorrentVPN if I can reach that or it's a limit of the encryption at 23MB/sec (~184Mbps)...

Keep in mind not all of the PIA nodes offer incoming, so if seeding is important, be sure you use a node that lets you be "connectable". nl definitely does, I don't know if any of the US do.

I *believe* none of the US servers have port forwarding. The Canadian servers do and I can max out my 100/10 connection without issue.

Hi!

 

I'm completely new to unraid and dockers.

I have a problem. I'm getting ERR_CONNECTION_REFUSED when I try to get to WebUI. I've set LAN_NETWORK Key 12 tp: 192.168.2.0/24 (Unraid machine IP: 192.168.2.5).

Am I missing something?

 

Thank you in advance!