[Support] binhex - rTorrentVPN


Recommended Posts

I recently updated this docker and now Im stuck on waiting for valid IP address from tunnel. It was working fine on version 4.4.5(1). 

 

Q11. There is an issue with the latest version of an application, how do i roll back to a specific version?

 

A11. In order to pull down a specific version of an application you need to modify the tag parameter with the version you want. This can be achieved by going to the unRAID web interface, left clicking the specific Docker container and selecting "edit", then click on the advanced view option (top right) and edit the repository string from:-

 

binhex/arch-<appname>:latest

 

to

 

binhex/arch-<appname>:<verisonyouwant>

 

I tried this but I don't see binhex/arch-rtorrentvpn:latest on the repository field and if i put binhex/arch-rtorrentvpn:4.4.5.1 it doesn't work. 

 

Any help to rollback or fix my problem with the latest version will be appreciated. 

 

This are the logs for the latest version: 

 

[info] OpenVPN started

[debug] Waiting for valid IP address from tunnel...

 

Thu May 18 23:55:20 2017 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.

Thu May 18 23:55:20 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Thu May 18 23:55:20 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]172.111.YYY.Y:53

Thu May 18 23:55:20 2017 UDP link local (bound): [AF_INET][undef]:1194

Thu May 18 23:55:20 2017 UDP link remote: [AF_INET]172.111.YYY.Y:53

Thu May 18 23:55:20 2017 VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=HK, ST=HK, L=HongKong, O=PureVPN, OU=IT, CN=PureVPN, name=PureVPN, [email protected]

Thu May 18 23:55:20 2017 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

Thu May 18 23:55:20 2017 TLS_ERROR: BIO read tls_read_plaintext error

Thu May 18 23:55:20 2017 TLS Error: TLS object -> incoming plaintext read error

Thu May 18 23:55:20 2017 TLS Error: TLS handshake failed

Thu May 18 23:55:20 2017 SIGUSR1[soft,tls-error] received, process restarting

Thu May 18 23:55:25 2017 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.

Thu May 18 23:55:25 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Thu May 18 23:55:25 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]104.243.XXX.X:53

Thu May 18 23:55:25 2017 UDP link local (bound): [AF_INET][undef]:1194

Thu May 18 23:55:25 2017 UDP link remote: [AF_INET]104.243.XXX.X:53

Thu May 18 23:55:25 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_ACK_V1)

Thu May 18 23:55:27 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:28 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_ACK_V1)

Thu May 18 23:55:28 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:28 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:29 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:30 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:32 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_ACK_V1)

Thu May 18 23:55:34 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:36 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:37 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:37 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:38 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:41 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_ACK_V1)

Thu May 18 23:55:53 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:54 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:55:57 2017 VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=HK, ST=HK, L=HongKong, O=PureVPN, OU=IT, CN=PureVPN, name=PureVPN, [email protected]

Thu May 18 23:55:57 2017 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

Thu May 18 23:55:57 2017 TLS_ERROR: BIO read tls_read_plaintext error

Thu May 18 23:55:57 2017 TLS Error: TLS object -> incoming plaintext read error

Thu May 18 23:55:57 2017 NOTE: --mute triggered...

Thu May 18 23:55:57 2017 1 variation(s) on previous 20 message(s) suppressed by --mute

Thu May 18 23:55:57 2017 SIGUSR1[soft,tls-error] received, process restarting

Thu May 18 23:56:02 2017 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.

Thu May 18 23:56:02 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Thu May 18 23:56:03 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]104.243.XXX.X:53

Thu May 18 23:56:03 2017 UDP link local (bound): [AF_INET][undef]:1194

Thu May 18 23:56:03 2017 UDP link remote: [AF_INET]104.243.XXX.X:53

Thu May 18 23:56:03 2017 VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=HK, ST=HK, L=HongKong, O=PureVPN, OU=IT, CN=PureVPN, name=PureVPN, [email protected]

Thu May 18 23:56:03 2017 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

Thu May 18 23:56:03 2017 TLS_ERROR: BIO read tls_read_plaintext error

Thu May 18 23:56:03 2017 TLS Error: TLS object -> incoming plaintext read error

Thu May 18 23:56:03 2017 TLS Error: TLS handshake failed

Thu May 18 23:56:03 2017 SIGUSR1[soft,tls-error] received, process restarting

Thu May 18 23:56:08 2017 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.

Thu May 18 23:56:08 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Thu May 18 23:56:08 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]172.111.YYY.Y:53

Thu May 18 23:56:08 2017 UDP link local (bound): [AF_INET][undef]:1194

Thu May 18 23:56:08 2017 UDP link remote: [AF_INET]172.111.YYY.Y:53

Thu May 18 23:56:08 2017 VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=HK, ST=HK, L=HongKong, O=PureVPN, OU=IT, CN=PureVPN, name=PureVPN, [email protected]

Thu May 18 23:56:08 2017 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

Thu May 18 23:56:08 2017 TLS_ERROR: BIO read tls_read_plaintext error

Thu May 18 23:56:08 2017 TLS Error: TLS object -> incoming plaintext read error

Thu May 18 23:56:08 2017 TLS Error: TLS handshake failed

Thu May 18 23:56:08 2017 SIGUSR1[soft,tls-error] received, process restarting

Thu May 18 23:56:13 2017 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.

Thu May 18 23:56:13 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Thu May 18 23:56:13 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]104.243.XXX.X:53

Thu May 18 23:56:13 2017 UDP link local (bound): [AF_INET][undef]:1194

Thu May 18 23:56:13 2017 UDP link remote: [AF_INET]104.243.XXX.X:53

Thu May 18 23:56:13 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_ACK_V1)

Thu May 18 23:56:15 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:15 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_ACK_V1)

Thu May 18 23:56:17 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:19 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:20 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:24 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:25 2017 TLS Error: Unroutable control packet received from [AF_INET]172.111.YYY.Y:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:28 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:28 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_ACK_V1)

Thu May 18 23:56:35 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Thu May 18 23:56:36 2017 TLS Error: Unroutable control packet received from [AF_INET]104.243.XXX.X:53 (si=3 op=P_CONTROL_V1)

Link to comment
5 hours ago, elpuntonegro said:

4.4.5(1). 

hu? where are you getting this version number from, as it doesnt relate to rtorrent (or rutorrent)?

 

as per the FAQ you quoted here is the url to show all available tags:-

 

https://hub.docker.com/r/binhex/arch-rtorrentvpn/tags/

 

and FYI this is your issue:-

 

VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=HK, ST=HK, L=HongKong, O=PureVPN, OU=IT, CN=PureVPN, name=PureVPN, [email protected]

 

Basically your VPN provider is using a weak cipher and OpenSSL v1.1.0 (1.0.x doesnt warn about this) is telling you so, up to you what you do but i wouldnt be happy with using it.

 

 

Link to comment
9 hours ago, binhex said:

hu? where are you getting this version number from, as it doesnt relate to rtorrent (or rutorrent)?

 

as per the FAQ you quoted here is the url to show all available tags:-

 

https://hub.docker.com/r/binhex/arch-rtorrentvpn/tags/

 

and FYI this is your issue:-

 

VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=HK, ST=HK, L=HongKong, O=PureVPN, OU=IT, CN=PureVPN, name=PureVPN, [email protected]

 

Basically your VPN provider is using a weak cipher and OpenSSL v1.1.0 (1.0.x doesnt warn about this) is telling you so, up to you what you do but i wouldnt be happy with using it.

 

 

Thanks for the advice! Time to change the VPN provider. 

 

Regards, 

 

Link to comment
On 5/18/2017 at 10:46 AM, RallyAK said:

After upgrading to the latest unRAID OS (6.3.4) I'm no longer able to login to the ruTorrent web gui.

 

According to the log, the docker appears to be starting fine but I'm getting time out errors when logging in to... 

 

http://<host ip>:9080/

https://<host ip>:9443/

 

Flood and Privoxy access are also broken.

http://<host ip>:3000/

http://<host ip>:8118

 

I've restarted the docker and server several times, and have tried using different VPN servers from my primary provider and AirVPN, but I'm still having the same issue. 

 

Here's a portion of my log, IP's and credentials have been edited, let me know if you need anything else to help troubleshoot.

 

EDIT: I'm able to access the gui if I shut off VPN but prefer not to run that way for very long, for obvious reasons. : |

 

Anyone else having the same issue?

 

supervisord.txt

 

Hi @binhex I switched to an AirVPN account to see if that made a difference with my access issue, but unfortunately it didn't. Here's a new log with DEBUG turned on. Take a look when you have a second and let me know what you think.

 

On a side note, have you considered supporting mullvad's VPN service on future builds? I setup a trial account with them today and tried logging in but the docker froze at the following line in their ovpn. I tried removing it but that didn't make a difference.

 

# Daemonize
service mullvadopenvpn

 

supervisord-2.txt

mullvad_windows.conf.ovpn

Edited by RallyAK
Link to comment
On 2017-5-20 at 7:21 AM, RallyAK said:

 

Hi @binhex I switched to an AirVPN account to see if that made a difference with my access issue, but unfortunately it didn't. Here's a new log with DEBUG turned on. Take a look when you have a second and let me know what you think.

 

On a side note, have you considered supporting mullvad's VPN service on future builds? I setup a trial account with them today and tried logging in but the docker froze at the following line in their ovpn. I tried removing it but that didn't make a difference.

 

# Daemonize
service mullvadopenvpn

 

supervisord-2.txt

mullvad_windows.conf.ovpn

 

i see no problems with the log supervisord-2.txt, that is a clean start.

Link to comment
On 5/22/2017 at 4:06 AM, binhex said:

 

i see no problems with the log supervisord-2.txt, that is a clean start.

That's what I thought, thanks for taking a look!

 

Do you have any thoughts on why I can't access the WebUI when connected to VPN?

 

I've confirmed that nothing on my network is using ports 9080, 9443, 3000, 5000 or 8118 so there shouldn't be any conflicts. Should I try changing the default http and https ports to something else like 9081 and 9444?

 

Of the 5-6 dockers I'm running this is the only one that broke after updating to 6.3.4. I'm able to access the WebUI's on all others via my host ip and default ports.

 

If anyone else is considering upgrading 6.3.4, you might want to hold off until this is resolved. (See below...)

Edited by RallyAK
Link to comment
14 hours ago, RallyAK said:

If anyone else is considering upgrading 6.3.4, you might want to hold off until this is resolved. 

 

please don't make sweeping assumptions :-(, your issue is not specify to version 6.3.4, this is a known issue since unraid build 6.1.8, you can see the issue in the log:-

 

[warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

you can read more about this in my FAQ:- 

 

 

See FAQ Q1.

Link to comment
9 hours ago, binhex said:

 

please don't make sweeping assumptions :-(, your issue is not specify to version 6.3.4, this is a known issue since unraid build 6.1.8, you can see the issue in the log:-

 


[warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

you can read more about this in my FAQ:- 

 

 

See FAQ Q1.

Thanks binhex! I ran '/sbin/modprobe iptable_mangle' restarted the docker and I'm able to access the WebUI again. Hallelujah!!! \o/

 

I saw this command reading through your FAQ but didn't think it applied because I was having issues locally, not outside my LAN as specified in the Q&A.

 

Apologies about the comment to hold off updating unRAID, that was merely a warning to others that updating may have been the culprit. Having ruTorrent running for a week, with hundreds of torrents seeding and no visibility is a little stressful.

 

Thanks again for your help, I appreciate everything you do and hope the beer $$$ I sent a few weeks back went to good use. :)

Edited by RallyAK
Link to comment
23 hours ago, RallyAK said:

I saw this command reading through your FAQ but didn't think it applied because I was having issues locally, not outside my LAN as specified in the Q&A

 

iptable_mangle support is only required if your accessing the webui outside of your defined LAN network, are you sure your connecting to the webui using your internal lan ip address?, your connecting to your home LAN via a VPN are you by any chance?.

 

ps. thanks for the beer money, all donations are very welcome indeed :-)

Link to comment
On 5/24/2017 at 10:57 AM, binhex said:

 

iptable_mangle support is only required if your accessing the webui outside of your defined LAN network, are you sure your connecting to the webui using your internal lan ip address?, your connecting to your home LAN via a VPN are you by any chance?.

 

ps. thanks for the beer money, all donations are very welcome indeed :-)

 

I was having trouble accessing the webui inside my LAN (10.x.x.x) and outside my LAN, on all ports. The only way I could access the webui was by disabling VPN.

 

Since running the '/sbin/modprobe iptable_mangle' command I haven't had any access issues, inside or outside of my network.

Edited by RallyAK
Link to comment
On 2017-4-28 at 2:05 AM, Wob76 said:

 

Thanks binhex, it seems to work most of the time, just once every week or 2 it doesn't seem to update. I usually just check whenever I notice no traffic, sometimes it matches othertimes it seems to be a stale IP.

 

Wob

 

@jonathanm as you mentioned an issue with delugevpn and incoming port - so guys i have put in additional retry code to try and ensure we get incoming port assigned (if PIA and on a gateway that supports it of course) and for rtorrent, also the public ip address, so hoping things should improve, these changes will be included in the next image pushed so please let me know how things go from that point onwards.

  • Upvote 1
Link to comment
1 hour ago, binhex said:

 

@jonathanm as you mentioned an issue with delugevpn and incoming port - so guys i have put in additional retry code to try and ensure we get incoming port assigned (if PIA and on a gateway that supports it of course) and for rtorrent, also the public ip address, so hoping things should improve, these changes will be included in the next image pushed so please let me know how things go from that point onwards.

Thanks! I'll be sure to squawk if it's something I think you can help.

Link to comment

Hi, I have a problem with the ENABLE_FLOOD argument which seems to stuck the startup.

When ENABLE_FLOOD=yes is defined, the startup stop here, and nothing happen after (and of course, the Flood WebUI is down). There is no error, nothing, after this line:

 

[info] Flood enabled, disabling initialisation of ruTorrent plugins...

 

When ENABLE_FLOOD=no is defined (and ruTorrent used consequently), everything starts normally and ruTorrent WebUI is accessible.

 

Thanks for your help!

docker run -d \
    --cap-add=NET_ADMIN \
    -p 9080:9080 \
    -p 9443:9443 \
    -p 8118:8118 \
    -p 3000:3000 \
    --name=rtorrentvpn \
    -v /opt/torrents/data:/data \
    -v /opt/torrents/config:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e VPN_ENABLED=yes \
    -e VPN_REMOTE=nl.vpn.airdns.org \
    -e VPN_PORT=443 \
    -e VPN_PROTOCOL=udp \
    -e VPN_DEVICE_TYPE=tun \
    -e VPN_PROV=airvpn \
    -e ENABLE_PRIVOXY=no \
    -e ENABLE_FLOOD=yes \
    -e LAN_NETWORK=192.168.1.0/24 \
    -e NAME_SERVERS=8.8.8.8,8.8.4.4 \
    -e DEBUG=false \
    -e PHP_TZ=UTC \
    -e UMASK=000 \
    -e PUID=0 \
    -e PGID=0 \
    binhex/arch-rtorrentvpn

 

Edit: I managed to make it work by replacing floodServerHost: '127.0.0.1' by floodServerHost: '0.0.0.0' in config.js, not sure it is the best solution but it works.

Edited by Elix
Config added
Link to comment

Hello, I've been experiencing an odd issue that others have experienced before but I can't seem fix it. RuTorrent seems to lose connection with rTorrent (rTorrent child process quits) as soon as all the torrents are loaded, checked, and immediately (within 3 seconds) of establishing a connection to any peer. The RuTorrent WebUI and functionality works perfectly fine until a connection to a peer is created and the rTorrent process immediately quits (I think). I've been using the Docker for months with VPN enabled without encountering this issue, so I can only conclude it must be correlated to the environment variable of where the internal VPN is disabled as experienced by user MyKroFt in this post but was apparently resolved in an update?

 

I have tried using both non-privileged and privileged mode for the docker and disabling the external OpenVPN plugin.

 

I'm currently running rTorrentVPN in default configuration with the VPN_ENABLED option set to false as I'm running the OpenVPN Client Plugin as I'm trying resolve an issue with rTorrentVPN not downloading with the built-in OpenVPN running on Arch. I'm not 100% sure that OpenVPN Client Plugin is causing this error as DelugeVPN shows no issues with torrenting while the external VPN is enabled.

 

Supervisor Log with DEBUG Enabled (no confidential info): 

https://pastebin.com/HPwiXY6M

chrome_2017-05-31_21-26-07.png

Edited by 1stHyperion
Link to comment
13 hours ago, 1stHyperion said:

Hello, I've been experiencing an odd issue that others have experienced before but I can't seem fix it. RuTorrent seems to lose connection with rTorrent (rTorrent child process quits) as soon as all the torrents are loaded, checked, and immediately (within 3 seconds) of establishing a connection to any peer. The RuTorrent WebUI and functionality works perfectly fine until a connection to a peer is created and the rTorrent process immediately quits (I think). I've been using the Docker for months with VPN enabled without encountering this issue, so I can only conclude it must be correlated to the environment variable of where the internal VPN is disabled as experienced by user MyKroFt in this post but was apparently resolved in an update?

 

I have tried using both non-privileged and privileged mode for the docker and disabling the external OpenVPN plugin.

 

I'm currently running rTorrentVPN in default configuration with the VPN_ENABLED option set to false as I'm running the OpenVPN Client Plugin as I'm trying resolve an issue with rTorrentVPN not downloading with the built-in OpenVPN running on Arch. I'm not 100% sure that OpenVPN Client Plugin is causing this error as DelugeVPN shows no issues with torrenting while the external VPN is enabled.

 

Supervisor Log with DEBUG Enabled (no confidential info): 

https://pastebin.com/HPwiXY6M

chrome_2017-05-31_21-26-07.png

 

That looks like issues with a plugin(s), stop the container and delete '/config/rutorrent/plugins' folder and then start the container again.

Link to comment
10 hours ago, binhex said:

 

That looks like issues with a plugin(s), stop the container and delete '/config/rutorrent/plugins' folder and then start the container again.

Thank you very much BinHex :D

Deleted the Plugins folder and restarted the Docker twice and it now works great.

Link to comment

How can I change the default password and do I need to change .htpasswd or is that not required since this is a docker?

Also on topic of docker how do they handle resources? Whatever the server has they can utilize or can more resources be allocated? While rTorrent has fixed my speeds issues I was having with deluge it seems to get very unresponsive with only a handful of torrents active (20) whereas deluge I've had over 100 without any such issues. (both were docker images) 

Link to comment

Trying to get this running but unable to.

 

Logs

Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2017-06-03 17:59:43.981000 [info] Host is running unRAID
2017-06-03 17:59:44.021144 [info] System information Linux dd09683491e2 4.9.30-unRAID #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017 x86_64 GNU/Linux
2017-06-03 17:59:44.068247 [info] PUID defined as '99'
2017-06-03 17:59:44.115894 [info] PGID defined as '100'
2017-06-03 17:59:44.166783 [info] UMASK defined as '000'
2017-06-03 17:59:44.213286 [info] Setting permissions recursively on volume mappings...
2017-06-03 17:59:44.282529 [info] VPN_ENABLED defined as 'yes'
2017-06-03 17:59:44.350112 [info] VPN_PROV defined as 'pia'
2017-06-03 17:59:44.396129 [info] VPN_REMOTE defined as 'ca.toronto.privateinternetaccess.com'
2017-06-03 17:59:44.440473 [info] VPN_PORT defined as '1198'
2017-06-03 17:59:44.486119 [info] VPN_PROTOCOL defined as 'udp'
2017-06-03 17:59:44.539380 [info] LAN_NETWORK defined as '192.168.1.0/24'
2017-06-03 17:59:44.587021 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2017-06-03 17:59:44.632192 [info] VPN_USER defined as 'xx'
2017-06-03 17:59:44.695034 [info] VPN_PASS defined as 'xx'
2017-06-03 17:59:44.757233 [info] VPN_INCOMING_PORT defined as '49160'
2017-06-03 17:59:44.803846 [info] VPN_DEVICE_TYPE defined as 'tun'
2017-06-03 17:59:44.850298 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2017-06-03 17:59:44.893420 [info] STRONG_CERTS defined as 'no'
2017-06-03 17:59:44.954715 [info] ENABLE_PRIVOXY defined as 'no'
2017-06-03 17:59:45.000748 [info] ENABLE_FLOOD defined as 'no'
chsh: Shell not changed.
Changing shell for nobody.
2017-06-03 17:59:45,753 CRIT Set uid to user 0
2017-06-03 17:59:45,753 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2017-06-03 17:59:45,757 INFO supervisord started with pid 7
2017-06-03 17:59:46,761 INFO spawned: 'flood-script' with pid 121
2017-06-03 17:59:46,762 INFO spawned: 'start-script' with pid 122
2017-06-03 17:59:46,764 INFO spawned: 'rtorrent-script' with pid 123
2017-06-03 17:59:46,765 INFO spawned: 'rutorrent-script' with pid 124
2017-06-03 17:59:46,766 INFO spawned: 'privoxy-script' with pid 125
2017-06-03 17:59:46,778 DEBG 'flood-script' stdout output:
[info] Flood not enabled, skipping starting Flood Web UI

2017-06-03 17:59:46,778 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47164896974752 for <Subprocess at 47164896973312 with name flood-script in state RUNNING> (stdout)>
2017-06-03 17:59:46,778 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47164896975328 for <Subprocess at 47164896973312 with name flood-script in state RUNNING> (stderr)>
2017-06-03 17:59:46,779 INFO exited: flood-script (exit status 0; expected)
2017-06-03 17:59:46,779 DEBG received SIGCLD indicating a child quit
2017-06-03 17:59:46,779 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2017-06-03 17:59:46,779 DEBG 'rtorrent-script' stdout output:
[info] rTorrent config file doesnt exist, copying default to /config/rtorrent/config/...

2017-06-03 17:59:46,780 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2017-06-03 17:59:46,781 DEBG fd 27 closed, stopped monitoring <POutputDispatcher at 47164898378024 for <Subprocess at 47164896974968 with name privoxy-script in state RUNNING> (stdout)>
2017-06-03 17:59:46,781 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 47164898379392 for <Subprocess at 47164896974968 with name privoxy-script in state RUNNING> (stderr)>
2017-06-03 17:59:46,781 INFO exited: privoxy-script (exit status 0; expected)
2017-06-03 17:59:46,781 DEBG received SIGCLD indicating a child quit
2017-06-03 17:59:46,785 DEBG 'rtorrent-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2017-06-03 17:59:46,789 DEBG 'start-script' stdout output:
[info] VPN default certs defined, copying to /config/openvpn/...

2017-06-03 17:59:46,793 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2017-06-03 17:59:46,795 DEBG 'start-script' stderr output:
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...

2017-06-03 17:59:46,850 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2017-06-03 17:59:46,855 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-06-03 17:59:46,860 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-06-03 17:59:46,868 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2017-06-03 17:59:46,869 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2017-06-03 17:59:46,870 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.12 
192.168.1.0/24 via 172.17.0.1 dev eth0 

2017-06-03 17:59:46,870 DEBG 'start-script' stdout output:
--------------------

2017-06-03 17:59:46,874 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2017-06-03 17:59:46,902 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2017-06-03 17:59:46,980 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-06-03 17:59:46,983 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 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 5000 -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 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -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

2017-06-03 17:59:46,983 DEBG 'start-script' stdout output:
--------------------

2017-06-03 17:59:46,983 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2017-06-03 17:59:46,990 DEBG 'start-script' stdout output:
[info] OpenVPN started

 

Link to comment
On 2017-6-4 at 2:04 AM, tooviral said:

Trying to get this running but unable to.

 

Logs


Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2017-06-03 17:59:43.981000 [info] Host is running unRAID
2017-06-03 17:59:44.021144 [info] System information Linux dd09683491e2 4.9.30-unRAID #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017 x86_64 GNU/Linux
2017-06-03 17:59:44.068247 [info] PUID defined as '99'
2017-06-03 17:59:44.115894 [info] PGID defined as '100'
2017-06-03 17:59:44.166783 [info] UMASK defined as '000'
2017-06-03 17:59:44.213286 [info] Setting permissions recursively on volume mappings...
2017-06-03 17:59:44.282529 [info] VPN_ENABLED defined as 'yes'
2017-06-03 17:59:44.350112 [info] VPN_PROV defined as 'pia'
2017-06-03 17:59:44.396129 [info] VPN_REMOTE defined as 'ca.toronto.privateinternetaccess.com'
2017-06-03 17:59:44.440473 [info] VPN_PORT defined as '1198'
2017-06-03 17:59:44.486119 [info] VPN_PROTOCOL defined as 'udp'
2017-06-03 17:59:44.539380 [info] LAN_NETWORK defined as '192.168.1.0/24'
2017-06-03 17:59:44.587021 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2017-06-03 17:59:44.632192 [info] VPN_USER defined as 'xx'
2017-06-03 17:59:44.695034 [info] VPN_PASS defined as 'xx'
2017-06-03 17:59:44.757233 [info] VPN_INCOMING_PORT defined as '49160'
2017-06-03 17:59:44.803846 [info] VPN_DEVICE_TYPE defined as 'tun'
2017-06-03 17:59:44.850298 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2017-06-03 17:59:44.893420 [info] STRONG_CERTS defined as 'no'
2017-06-03 17:59:44.954715 [info] ENABLE_PRIVOXY defined as 'no'
2017-06-03 17:59:45.000748 [info] ENABLE_FLOOD defined as 'no'
chsh: Shell not changed.
Changing shell for nobody.
2017-06-03 17:59:45,753 CRIT Set uid to user 0
2017-06-03 17:59:45,753 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2017-06-03 17:59:45,757 INFO supervisord started with pid 7
2017-06-03 17:59:46,761 INFO spawned: 'flood-script' with pid 121
2017-06-03 17:59:46,762 INFO spawned: 'start-script' with pid 122
2017-06-03 17:59:46,764 INFO spawned: 'rtorrent-script' with pid 123
2017-06-03 17:59:46,765 INFO spawned: 'rutorrent-script' with pid 124
2017-06-03 17:59:46,766 INFO spawned: 'privoxy-script' with pid 125
2017-06-03 17:59:46,778 DEBG 'flood-script' stdout output:
[info] Flood not enabled, skipping starting Flood Web UI

2017-06-03 17:59:46,778 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-06-03 17:59:46,778 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47164896974752 for <Subprocess at 47164896973312 with name flood-script in state RUNNING> (stdout)>
2017-06-03 17:59:46,778 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47164896975328 for <Subprocess at 47164896973312 with name flood-script in state RUNNING> (stderr)>
2017-06-03 17:59:46,779 INFO exited: flood-script (exit status 0; expected)
2017-06-03 17:59:46,779 DEBG received SIGCLD indicating a child quit
2017-06-03 17:59:46,779 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2017-06-03 17:59:46,779 DEBG 'rtorrent-script' stdout output:
[info] rTorrent config file doesnt exist, copying default to /config/rtorrent/config/...

2017-06-03 17:59:46,780 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2017-06-03 17:59:46,781 DEBG fd 27 closed, stopped monitoring <POutputDispatcher at 47164898378024 for <Subprocess at 47164896974968 with name privoxy-script in state RUNNING> (stdout)>
2017-06-03 17:59:46,781 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 47164898379392 for <Subprocess at 47164896974968 with name privoxy-script in state RUNNING> (stderr)>
2017-06-03 17:59:46,781 INFO exited: privoxy-script (exit status 0; expected)
2017-06-03 17:59:46,781 DEBG received SIGCLD indicating a child quit
2017-06-03 17:59:46,785 DEBG 'rtorrent-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2017-06-03 17:59:46,789 DEBG 'start-script' stdout output:
[info] VPN default certs defined, copying to /config/openvpn/...

2017-06-03 17:59:46,793 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2017-06-03 17:59:46,795 DEBG 'start-script' stderr output:
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...

2017-06-03 17:59:46,850 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2017-06-03 17:59:46,855 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-06-03 17:59:46,860 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-06-03 17:59:46,868 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2017-06-03 17:59:46,869 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2017-06-03 17:59:46,870 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.12 
192.168.1.0/24 via 172.17.0.1 dev eth0 

2017-06-03 17:59:46,870 DEBG 'start-script' stdout output:
--------------------

2017-06-03 17:59:46,874 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2017-06-03 17:59:46,902 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2017-06-03 17:59:46,980 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-06-03 17:59:46,983 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 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 5000 -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 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -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

2017-06-03 17:59:46,983 DEBG 'start-script' stdout output:
--------------------

2017-06-03 17:59:46,983 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2017-06-03 17:59:46,990 DEBG 'start-script' stdout output:
[info] OpenVPN started

 

 

nothing obvious in the normal logs, can you please follow the procedure in my sig, help link (if you cant see my sig then check your profile settings).

Link to comment

Got it running eventually, just retyped my login credentials.

 

Cant get Flood running though...

 

_='[debug] Environment variables defined as follows'
exit_code_chmod=0
exit_code_chown=0
[debug] Directory listing of files in /config/openvpn as follows

2017-06-06 16:56:45,777 DEBG 'start-script' stdout output:
total 16
drwxrwxrwx 1 nobody users 118 Jun 4 13:56 .
drwxrwxr-x 1 nobody users 150 Jun 4 12:52 ..
-rwxrwxrwx 1 nobody users 2025 Jun 6 16:56 ca.rsa.2048.crt
-rwxrwxrwx 1 nobody users 20 Jun 4 13:56 credentials.conf
-rwxrwxrwx 1 nobody users 869 Jun 6 16:56 crl.rsa.2048.pem
-rwxrwxrwx 1 nobody users 272 Jun 6 16:56 openvpn.ovpn

2017-06-06 16:56:45,777 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2017-06-06 16:56:45,778 DEBG 'start-script' stderr output:
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...

2017-06-06 16:56:45,815 DEBG 'start-script' stdout output:
[debug] Contents of ovpn file /config/openvpn/openvpn.ovpn as follows...

2017-06-06 16:56:45,816 DEBG 'start-script' stdout output:
client
dev tun

p
remote ca-toronto.privateinternetaccess.com 1198
resolv-retry infinite
nobind
persist-key
cipher aes-128-cbc

1
tls-client
remote-cert-tls server
auth-user-pass credentials.conf
comp-lzo
verb 1
crl-verify crl.rsa.2048.pem
ca ca.rsa.2048.crt
disable-occ

2017-06-06 16:56:45,822 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2017-06-06 16:56:45,826 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.1 to /etc/resolv.conf

2017-06-06 16:56:45,831 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-06-06 16:56:45,834 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-06-06 16:56:45,834 DEBG 'start-script' stdout output:
[debug] Show name servers defined for container

2017-06-06 16:56:45,835 DEBG 'start-script' stdout output:
nameserver 192.168.1.1
nameserver 8.8.8.8
nameserver 8.8.4.4

2017-06-06 16:56:45,835 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint ca-toronto.privateinternetaccess.com

2017-06-06 16:56:45,887 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 40977
;; flags: qr rd ra ; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; ca-toronto.privateinternetaccess.com.	IN	A

;; ANSWER SECTION:
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.126
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.3
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.27
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.71
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.7
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.6
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.69
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.98
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.34
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.29
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.112
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.135
ca-toronto.privateinternetaccess.com.	154	IN	A	172.98.67.93

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 49 msec
;; SERVER: 192.168.1.1
;; WHEN: Tue Jun 6 16:56:45 2017
;; MSG SIZE rcvd: 262

2017-06-06 16:56:45,895 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2017-06-06 16:56:45,896 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2017-06-06 16:56:45,898 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.10
192.168.1.0/24 via 172.17.0.1 dev eth0

2017-06-06 16:56:45,898 DEBG 'start-script' stdout output:
--------------------
[debug] Modules currently loaded for kernel

2017-06-06 16:56:45,901 DEBG 'start-script' stdout output:
Module Size Used by
tun 19304 0
iptable_mangle 1658 2
xt_nat 1913 19
veth 4966 0
ipt_MASQUERADE 1277 20
nf_nat_masquerade_ipv4 1865 1 ipt_MASQUERADE
iptable_nat 1897 1
nf_conntrack_ipv4 5874 2
nf_nat_ipv4 4199 1 iptable_nat
iptable_filter 1706 5
ip_tables 9853 3 iptable_mangle,iptable_filter,iptable_nat
nf_nat 11145 3 xt_nat,nf_nat_masquerade_ipv4,nf_nat_ipv4
md_mod 36700 11
bonding 92464 0
x86_pkg_temp_thermal 4669 0
coretemp 5340 0
ixgbe 177948 0
kvm_intel 160551 0
mpt3sas 168061 18
ptp 9308 1 ixgbe
i2c_i801 11888 0
ahci 26326 0
i2c_smbus 3041 1 i2c_i801
raid_class 3380 1 mpt3sas
kvm 289949 1 kvm_intel
pps_core 5928 1 ptp
i2c_core 20390 2 i2c_i801,i2c_smbus
libahci 19716 1 ahci
megaraid_sas 100045 0
mdio 2935 1 ixgbe
scsi_transport_sas 21714 1 mpt3sas
wmi 6548 0
ipmi_si 36442 0

2017-06-06 16:56:45,906 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2017-06-06 16:56:45,917 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2017-06-06 16:56:45,921 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.10

2017-06-06 16:56:45,925 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2017-06-06 16:56:45,939 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2017-06-06 16:56:46,048 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-06-06 16:56:46,050 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 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 3000 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 3000 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 5000 -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 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 3000 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 3000 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -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

2017-06-06 16:56:46,050 DEBG 'start-script' stdout output:
--------------------

2017-06-06 16:56:46,051 DEBG 'start-script' stdout output:
[debug] OpenVPN command line '/usr/bin/openvpn --cd /config/openvpn --config /config/openvpn/openvpn.ovpn --daemon --dev tun0 --remote ca-toronto.privateinternetaccess.com 1198 --proto udp --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --setenv VPN_PROV pia --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart --auth-user-pass credentials.conf --disable-occ --remap-usr1 SIGHUP --auth-user-pass credentials.conf --log-append /config/supervisord.log'
[info] Starting OpenVPN...

2017-06-06 16:56:46,067 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-06-06 16:56:46,067 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2017-06-06 16:56:47,457 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.93.10.6'

2017-06-06 16:56:47,463 DEBG 'rtorrent-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.93.10.6'

2017-06-06 16:56:47,468 DEBG 'rtorrent-script' stdout output:
[info] rTorrent not running
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.93.10.6 different, marking for reconfigure

2017-06-06 16:56:47,570 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '173.239.230.89'

2017-06-06 16:56:58,439 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '24059'
[info] Removing any rtorrent session lock files left over from the previous run...

2017-06-06 16:56:58,441 DEBG 'rtorrent-script' stdout output:
[info] Attempting to start rTorrent...

2017-06-06 16:56:58,444 DEBG 'rtorrent-script' stdout output:
Script started, file is /home/nobody/typescript

2017-06-06 16:56:58,477 DEBG 'rtorrent-script' stdout output:
Script done, file is /home/nobody/typescript

2017-06-06 16:56:58,482 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for rTorrent process to start...

2017-06-06 16:56:58,581 DEBG 'flood-script' stdout output:
[info] rTorrent started, configuring Flood...

2017-06-06 16:56:58,582 DEBG 'flood-script' stdout output:
[info] Flood config file already exists in /config/flood/, copying back to container...

2017-06-06 16:56:58,583 DEBG 'flood-script' stdout output:
[info] Starting Flood...

2017-06-06 16:56:59,488 DEBG 'rtorrent-script' stdout output:
[info] rTorrent started

2017-06-06 16:56:59,488 DEBG 'rtorrent-script' stdout output:
[info] Flood enabled, disabling initialisation of ruTorrent plugins...
[debug] VPN incoming port is 24059
[debug] VPN IP is 10.93.10.6
[debug] rTorrent incoming port is 24059
[debug] rTorrent IP is 10.93.10.6

2017-06-06 16:57:29,490 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2017-06-06 16:57:29,638 DEBG 'rtorrent-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.93.10.6'

2017-06-06 16:57:29,649 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '173.239.230.89'

2017-06-06 16:57:29,650 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '24059'

2017-06-06 16:57:29,832 DEBG 'rtorrent-script' stdout output:
[debug] VPN incoming port is 24059
[debug] VPN IP is 10.93.10.6
[debug] rTorrent incoming port is 24059
[debug] rTorrent IP is 10.93.10.6

2017-06-06 16:57:59,834 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2017-06-06 16:57:59,977 DEBG 'rtorrent-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.93.10.6'

2017-06-06 16:57:59,983 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '173.239.230.89'

2017-06-06 16:57:59,984 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '24059'

2017-06-06 16:58:00,116 DEBG 'rtorrent-script' stdout output:
[debug] VPN incoming port is 24059
[debug] VPN IP is 10.93.10.6
[debug] rTorrent incoming port is 24059
[debug] rTorrent IP is 10.93.10.6

2017-06-06 16:58:30,118 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2017-06-06 16:58:30,249 DEBG 'rtorrent-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.93.10.6'

2017-06-06 16:58:30,254 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '173.239.230.89'

2017-06-06 16:58:30,255 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '24059'

2017-06-06 16:58:30,478 DEBG 'rtorrent-script' stdout output:
[debug] VPN incoming port is 24059
[debug] VPN IP is 10.93.10.6
[debug] rTorrent incoming port is 24059
[debug] rTorrent IP is 10.93.10.6

2017-06-06 16:59:00,479 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2017-06-06 16:59:00,612 DEBG 'rtorrent-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.93.10.6'

2017-06-06 16:59:00,620 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '173.239.230.89'

2017-06-06 16:59:00,622 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '24059'

2017-06-06 16:59:00,911 DEBG 'rtorrent-script' stdout output:
[debug] VPN incoming port is 24059
[debug] VPN IP is 10.93.10.6
[debug] rTorrent incoming port is 24059

2017-06-06 16:59:00,911 DEBG 'rtorrent-script' stdout output:
[debug] rTorrent IP is 10.93.10.6

2017-06-06 16:59:30,913 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2017-06-06 16:59:31,051 DEBG 'rtorrent-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.93.10.6'

2017-06-06 16:59:31,060 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '173.239.230.89'

2017-06-06 16:59:31,062 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '24059'

2017-06-06 16:59:31,302 DEBG 'rtorrent-script' stdout output:
[debug] VPN incoming port is 24059
[debug] VPN IP is 10.93.10.6
[debug] rTorrent incoming port is 24059
[debug] rTorrent IP is 10.93.10.6

 

Link to comment
6 hours ago, karlpox said:

Hi,

 

Why is the download very slow even if the peers and seeders are good? I have a 50mbps connection and all I can download is < 200kbps. My upload speed is fast though.

 

Karl

 

which vpn provider are you with?, if you're not using PIA then you need to configure the incoming port, if you dont do this speeds will be very low.

Link to comment
20 hours ago, binhex said:

 

which vpn provider are you with?, if you're not using PIA then you need to configure the incoming port, if you dont do this speeds will be very low.

Im not on any VPN. I did open the ports already. But rtorrent still shows that its not opened.

Link to comment
2 hours ago, karlpox said:

Im not on any VPN. I did open the ports already. But rtorrent still shows that its not opened.

 

if rutorrent web ui is showing a red icon then you do not have a working incoming port and this will def be the cause of your low speeds. ok so you need to do the following:-

 

1. add a port to the docker configuration for the rtorrentvpn container,  whatever port number you want as long as its not already in use make a note of it!

2. set the incoming port via the rutorrent web ui to use the <port defined in step 1.>

3. login to your router and setup a port forward/virtual server for external port for <port defined in step 1.> to <unraid server ip address> <port defined in step 1.>

 

Keep in mind the reason the docker template doesnt include a incoming port already is because port forwarding is typically done over the vpn tunnel and thus an exposed port forward is not required, you only need this if you don't use the vpn feature (which most people do).

Link to comment
  • binhex locked this topic
Guest
This topic is now closed to further replies.