DavidAUK

February 14, 2020

I got the rclone gui working via the official docker container. Details here. I thought some people on this thread might find it useful.

February 14, 2020

I got it working and made a guide here.

January 29, 2020

13 hours ago, Cat_Seeder said:

VPN_INCOMING_PORT is used in rtorrent.sh (although it is not documented and I'm not really sure if it's meant to be used directly). Could you try to set it with the desired port just for the sake of testing?

I set VPN_INCOMING_PORT=XXXXX as an environment variable for the rtorrentvpn container and it worked! XXXXX is my listening port as set in the network.port_range.set = XXXXX-XXXXX setting in rtorrent.rc. Thank you so much for digging into that one.

I have a feeling the same thing is happening with DelugeVPN.

January 28, 2020

Thanks @Cat_Seeder. Genuinely appreciate the help.

Those lines are correct in my rtorrent.rc file. I just pulled a fresh rc file from the git repo and only changed the network.port_range.set line and it still didn't work. I don't use DHT so I think it's safe to rule that out.

The clues, as I see them, are the fact that the port is open and listening for a few minutes when it starts but then stops listening as it finishes initialising. I can fix it by setting it manually in the container. Also, there are lines in the log that say:

WARNING Not a valid number: '-' (invalid literal for int() with base 10: '-')
INFO: Bad data packets written to '/tmp/xmlrpc2scgi-1000.xml'
ERROR While calling network.bind_address.set('', '10.35.0.101'): <Fault -503: 'Invalid port_range argument.'

Here's a pastebin of my rc.

STRICT_PORT_FORWARD was set to yes, but setting to no hasn't fixed the problem.

VPN_INCOMING_PORT isn't a environment variable for this container, is it?

January 28, 2020

Hey @Cat_Seeder, @binhex. Sorry to bug but if you have any pointers for the above then I'd love to hear it. I can fix it if I change those settings manually from within the Docker but I'd prefer it to work without an intervention. @nota seems to have the same problem.

January 25, 2020

1 hour ago, Cat_Seeder said:

My gut feeling is that one of the 4 values above is wrong for some reason.

Yes, I think you're right. The listening socket is not set when I use rtxmlrpc network.port_range to check it. It's listening as it starts, but then when rtorrent tries to connect to the web interface (if I'm understanding it right) it reconfigures and sets the listening port to null.

[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.35.0.101 different, marking for reconfigure

Here's a log, which shows more.

2020-01-25 21:25:59,063 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.35.0.101 different, marking for reconfigure
2020-01-25 21:26:20,367 DEBG 'watchdog-script' stdout output:
WARNING  Not a valid number: '-' (invalid literal for int() with base 10: '-')
2020-01-25 21:26:20,369 DEBG 'watchdog-script' stdout output:
-
2020-01-25 21:26:25,509 DEBG 'watchdog-script' stderr output:
INFO: Bad data packets written to '/tmp/xmlrpc2scgi-1000.xml'
2020-01-25 21:26:25,510 DEBG 'watchdog-script' stdout output:
ERROR    While calling network.bind_address.set('', '10.35.0.101'): <Fault -503: 'Invalid port_range argument.'

The relevant lines in my rtorrent.conf look like this.

# SCGI Connectivity (for alternative rtorrent interfaces, XMLRPC)
#
# Use a IP socket with scgi_port, or a Unix socket with scgi_local.
# schedule can be used to set permissions on the unix socket.
#
scgi_port = 0.0.0.0:5000
#scgi_local = /home/user/rtorrent/rpc.socket
#schedule = scgi_permission,0,0,"execute.nothrow=chmod,\"g+w,o=\",/home/user/rtorrent/rpc.socket"

Is that scgi_port setting incorrect? Thank you for your help! I feel like I'm getting closer.

January 25, 2020

On 1/18/2020 at 3:41 PM, Cat_Seeder said:

Since netstat is not showing the desired port as LISTEN you may also try to dynamically set the port:

This worked for me. Thank you. How do I avoid doing this manually though?

For anyone who wants to try this for themselves, go to the shell in the container. To find out which ports are listening use

netstat -plnt

If the port is not listening then you can dynamically set the port as Cat_Seeder describes by issuing the following commands.

rtxmlrpc network.port_range.set '' "XXXXX-XXXXX"
rtxmlrpc dht.port.set '' "XXXXX"

Where XXXXX is the rtorrent listening port. Then type the following command.

rtxmlrpc network.bind_address.set '' "The VPN assigned IP"

I found the VPN assigned IP in the following line of rtorrentvpn container log where I've marked XX.XX.X.XX

Sat Jan 25 03:07:45 2020 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS zz.z.z.z,dhcp-option DNS zz.z.z.z,sndbuf 524288,rcvbuf 524288,route zz.zz.z.z,topology net30,ping 5,ping-restart 30,compress,ifconfig XX.XX.X.XX zz.zz.z.zz,peer-id 0'

Then issue the following command.

rtxmlrpc network.local_address.set '' "The External IP"

I found the External IP in the following line of the rtorrentvpn.

[info] Successfully retrieved external IP address XX.XXX.XXX.XXX

After I'd sent those four commands the netstat -plnt showed the port as listening, as did the rutorrent web interface.

January 19, 2020

On 1/18/2020 at 3:41 PM, Cat_Seeder said:
Since netstat is not showing the desired port as LISTEN you may also try to dynamically set the port:
rtxmlrpc network.port_range.set '' "60210-60210"
rtxmlrpc dht.port.set '' "60210"

Thanks for the ideas. Do these lines go in rtorrent.conf or somewhere else?

January 18, 2020

5 minutes ago, Cat_Seeder said:

Check if your box is connectable.

No, that doesn't work. Shows as closed.

Does it matter if I connect to the VPN in UDP or TCP protocol?

January 18, 2020

35 minutes ago, Cat_Seeder said:

Have you manually set port 60210 as your rtorrent port (i.e., network.port_range.set = 60210-60210 in rtorrent.rc)? The container will only detect and set ports automatically for PIA and AirVPN

Yes. That seems to be set up correctly in rtorrent.tc and is shown in the GUI.

January 17, 2020

I'm having a problem with the listening port. It's correctly forwarded at the VPN provider and has worked in the past. The port I've set is 60210 and that's the port that the GUI says it's listening on. The status bar says it's closed.

Here's the results of the netstat from the docker container.

[root@50c27a10609f /]# netstat -lntu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 127.0.0.11:44369        0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:9080            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:7777          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:9443            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN
udp        0      0 127.0.0.11:54700        0.0.0.0:*
[root@50c27a10609f /]#

I would expect 60210 to show up there, so maybe it's related to that? Help appreciated.

December 26, 2019

Rutorrent keeps forgetting my password.

In my YAML file I have

      - WEBUI_USER=jdoe
      - WEBUI_PASS=password123

And on first run that works, but after a while it defaults to admin/rutorrent.

Does anyone have any idea why that would happen?

February 17, 2019

On 2/9/2019 at 10:54 PM, jvorn said:

My ISP doesn't block it as I can navigate there in my browser.

Some more strangeness. I was able to add the tracker from a fresh install of the docker, but the second I added the proxy info back in it starting failing. Adding to the confusion, when I removed the proxy info it STILL didn't work. The proxy does work though, my Deluge is reporting the correct VPN IP...

It could be something related to CloudFlare, which I understand iptorrents recently added. I don't know too much about how CloudFlare works but it sometimes initiates a DDOS prevention page before sending you to the actual page. It looks like this. I believe Jackett is set up to handle them but perhaps there's an issue with CloudFlare in combination with a proxy?

Since CloudFlare DDOS page happens intermittently perhaps that's what's creating intermittent results. But I'm just guessing.

February 16, 2019

14 hours ago, binhex said:

Some index sites will block IP addresses from known proxy and VPN providers so not all indexed sites can be accessed even with ISP restrictions bypassed.

I am able to access those sites using a browser and the same proxy, so I don't think that's it.

My hunch that it's an issue related to Jackett + proxy + CloudFlare.

February 9, 2019

I use a proxy with Jackett and have had problems adding trackers that are blocked by my ISP. Can you add any trackers?

February 6, 2019

Listening for what? Port 5000 in your setup is rtorrent listening for a connection to a WebUI. It's not the port that your browser uses to connect to the WebUI nor the port that rtorrent uses as a listening port for incoming connections.

January 30, 2019

On 1/29/2019 at 9:50 PM, nekromantik said:

People who used both this and DelugeVPN, which torrent client do you prefer?

RTorrent or Deluge?

I’m not an expert but my understanding is that rtorrent let’s you seed more files at once than Deluge. I’ve heard people seeding 1000 torrents in rtorrent.

The plugin system of Deluge is great although a little more geared for desktop users as a lot of them don’t have a webui and need to be operated through thin client, which is a bit painful.

The binhex container of rtorrent comes with two interfaces: rutorrent and Flood. The latter looks modern and clean compared with rutorrent and Deluge. You might also want to take a look at the material design of the combustion interface for Transmission.

Deluge works well with Sonarr, offering some functionality that isn’t present in other clients.

January 28, 2019

On 1/27/2019 at 9:55 AM, binhex said:

Ok so I suspect it's probably a firewall on the host

I don't think it's a firewall as UFW is disabled and non-VPN containers work fine. But I agree that it's likely something on the host. Yes, it's Ubuntu Server 18.04.1 LTS with a default install and very little installed that would clash with these containers. I've spent many hours trying to diagnose this, so while it's certainly something that's caused by the combination of my operating system and this container, any pointers would be appreciated.

Here's what I've worked out.

Ports are open and forwarded on the router, which is google wifi.
Remote access to non-VPN containers (e.g. Portainer) works fine.
Remote access to VPN container's WebUIs (e.g. Flood, Rutorrent, Deluge) all fail. ERR_CONNECTION_TIMED_OUT in Chrome.
Rutorrent shows the listening port status as unknown - likely blocked.
Haugene/docker-transmission-openvpn also has a blocked listening port - problem not unique to binhex builds?
Remote access to VPN container's WebUIs works fine if I use traefik reverse proxy. Doesn't help the listening port though. Currently disabled.
RtorrentVPN and DelugeVPN work without problem on my Synology NAS on the same network.
Changing from the default ports makes no difference.

Since non-VPN containers work fine and the issue is present in Haugene and your containers, I wonder if the issue might be related to OpenVPN?

Is there anything I can do that would give more diagnostic information? Some kind of netstat? Would a 100% fresh install of Ubuntu help?

January 26, 2019

Re-uploaded the log file. iptable_mangle seems to be working but still no success accessing rtorrentvpn on delugevpn remotely.

January 25, 2019

And I don't know if it provides a clue or not, but when I'm on the home LAN and use the WAN IP on the VPN containers then everything works fine. That would suggest that I have the right IP and ports at least.

Also, online port forward testers think that my the ports on my VPN containers are closed.

January 25, 2019

Quote

1. do you use vlan's on your home network? - if so then check that the vlan assigned to the host allows inbound and outbound external access and the routing is correct.

Not as far as I know. I have it working fine on a Synology which shares the same network.

Quote

2. is a firewall running on your host? - check to see if anything is blocking outbound on the host, if you are running all the containers on the same host and you have external access to them, then this wont be the issue.

I'm running non-VPN containers and remotely connecting to them without problems on the same device.

Quote

3. does 192.168.86.0/24 cover all networks on your lan? - if it doesn't then you will need to add in any additional networks you have defined, what is your router's ip address?

The IP addresses are 192.168.86.* The router's IP address is 192.168.86.1.

Quote

4. port forwarding - can you post a screenshot showing how you have defined the port forward for this container?, it should be port forward to internal ip 192.168.86.xxx where xxx is your hosts ip, and port <host port you have chosen for flood, normally 3000>

I've attached a screenshot showing the port forwarding I'm using and a log file with debug enabled. After your post I noticed that I was setting debug to true but then false later in the YML - sorry about that.

To recap, neither DelugeVPN or rTorrentVPN can be accessed remotely. Both can be accessed locally. I previously had these containers running on a Synology on the same network, so I'm inclined to say it's not my network. Ports are correctly forwarded, as far as I can see. This is the first time I'm running on Ubuntu Server, so perhaps I've set something incorrectly there.

I assume that the IP I should be connecting to is the same as my WAN IP? That's what I did successfully on the Synology.

supervisord.log

January 24, 2019

6 hours ago, binhex said:

ok in that case i need to see the logs, please follow the procedure in the link below:-

I appreciate you taking a look.

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

2019-01-24 19:25:10.905186 [info] System information Linux 88294efb28ef 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 GNU/Linux
2019-01-24 19:25:11.007628 [info] PUID defined as '1000'
2019-01-24 19:25:11.902932 [info] PGID defined as '1000'
2019-01-24 19:25:12.116582 [info] UMASK defined as '000'
2019-01-24 19:25:12.214016 [info] Permissions already set for volume mappings
2019-01-24 19:25:12.333951 [info] VPN_ENABLED defined as 'yes'
2019-01-24 19:25:12.466408 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/82.ovpn
dos2unix: converting file /config/openvpn/82.ovpn to Unix format...
2019-01-24 19:25:12.616011 [info] VPN remote line defined as 'remote aus.torguardvpnaccess.com 1912'
2019-01-24 19:25:12.789639 [info] VPN_REMOTE defined as 'aus.torguardvpnaccess.com'
2019-01-24 19:25:12.911753 [info] VPN_PORT defined as '1912'
2019-01-24 19:25:13.017757 [info] VPN_PROTOCOL defined as 'udp'
2019-01-24 19:25:13.128758 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-01-24 19:25:13.222409 [info] VPN_PROV defined as 'custom'
2019-01-24 19:25:13.337962 [info] LAN_NETWORK defined as '192.168.86.0/24'
2019-01-24 19:25:13.463074 [info] NAME_SERVERS defined as '8.8.8.8'
2019-01-24 19:25:13.565596 [info] VPN_USER defined as 'redacted'
2019-01-24 19:25:13.684136 [info] VPN_PASS defined as 'redacted'
2019-01-24 19:25:13.787501 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-01-24 19:25:13.897537 [info] ENABLE_PRIVOXY defined as 'yes'
2019-01-24 19:25:13.990908 [info] ENABLE_FLOOD defined as 'yes'
2019-01-24 19:25:14.087737 [info] ENABLE_AUTODL_IRSSI defined as 'no'
2019-01-24 19:31:40.263742 [info] Starting Supervisor...
2019-01-24 19:31:41,162 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2019-01-24 19:31:41,162 INFO Set uid to user 0 succeeded
2019-01-24 19:31:41,169 INFO supervisord started with pid 7
2019-01-24 19:31:42,176 INFO spawned: 'start-script' with pid 147
2019-01-24 19:31:42,184 INFO spawned: 'rutorrent-script' with pid 148
2019-01-24 19:31:42,188 INFO spawned: 'flood-script' with pid 149
2019-01-24 19:31:42,192 INFO spawned: 'irssi-script' with pid 150
2019-01-24 19:31:42,212 INFO spawned: 'watchdog-script' with pid 151
2019-01-24 19:31:42,256 INFO spawned: 'privoxy-script' with pid 152
2019-01-24 19:31:42,260 INFO reaped unknown pid 8
2019-01-24 19:31:42,262 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-01-24 19:31:42,264 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-24 19:31:42,265 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-24 19:31:42,265 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-24 19:31:42,266 INFO success: irssi-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-24 19:31:42,267 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-24 19:31:42,267 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-24 19:31:42,272 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 140550398030624 for <Subprocess at 140550397704312 with name irssi-script in state RUNNING> (stderr)>
2019-01-24 19:31:42,280 DEBG 'irssi-script' stdout output:
[info] Autodl-irssi not enabled, skipping startup

2019-01-24 19:31:42,280 INFO exited: irssi-script (exit status 0; expected)
2019-01-24 19:31:42,281 DEBG received SIGCLD indicating a child quit
2019-01-24 19:31:42,306 DEBG 'flood-script' stdout output:
[info] Flood enabled

2019-01-24 19:31:42,307 DEBG 'flood-script' stdout output:
[info] Waiting for rTorrent process to start listening on port 5000...

2019-01-24 19:31:42,310 DEBG 'rutorrent-script' stdout output:
[info] Flood enabled, preventing ruTorrent Web UI from starting...

2019-01-24 19:31:42,311 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 140550397705824 for <Subprocess at 140550397704600 with name rutorrent-script in state RUNNING> (stderr)>
2019-01-24 19:31:42,311 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 140550397705536 for <Subprocess at 140550397704600 with name rutorrent-script in state RUNNING> (stdout)>
2019-01-24 19:31:42,312 INFO exited: rutorrent-script (exit status 0; expected)
2019-01-24 19:31:42,313 DEBG received SIGCLD indicating a child quit
2019-01-24 19:31:42,314 DEBG 'watchdog-script' stdout output:
[info] rTorrent config file already exists, skipping copy

2019-01-24 19:31:42,324 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2019-01-24 19:31:42,384 DEBG 'watchdog-script' stderr output:
dos2unix: 
2019-01-24 19:31:42,385 DEBG 'watchdog-script' stderr output:
converting file /config/rtorrent/config/rtorrent.rc to Unix format...

2019-01-24 19:31:42,442 DEBG 'start-script' stdout output:
[info] Default route for container is 172.20.0.1

2019-01-24 19:31:42,451 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-01-24 19:31:42,565 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...

2019-01-24 19:31:42,568 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/4.15.0-43-generic

2019-01-24 19:31:42,569 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2019-01-24 19:31:42,572 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2019-01-24 19:31:42,578 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2019-01-24 19:31:42,672 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.20.0.0/16

2019-01-24 19:31:42,685 DEBG 'start-script' stdout output:
[info] Adding 192.168.86.0/24 as route via docker eth0

2019-01-24 19:31:42,689 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-01-24 19:31:42,693 DEBG 'start-script' stdout output:
default via 172.20.0.1 dev eth0 

2019-01-24 19:31:42,694 DEBG 'start-script' stdout output:
172.20.0.0/16 dev eth0 proto kernel scope link src 172.20.0.2 

2019-01-24 19:31:42,695 DEBG 'start-script' stdout output:
192.168.86.0/24 via 172.20.0.1 dev eth0 

2019-01-24 19:31:42,697 DEBG 'start-script' stdout output:
--------------------

2019-01-24 19:31:42,713 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               40960  9 xt_conntrack,iptable_filter,xt_tcpudp,ipt_MASQUERADE,xt_addrtype,xt_nat,ip_tables,iptable_mangle,xt_mark

2019-01-24 19:31:42,715 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-01-24 19:31:42,992 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-01-24 19:31:42,996 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.20.0.0/16 -d 172.20.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1912 -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.86.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT
-A INPUT -s 192.168.86.0/24 -d 172.20.0.0/16 -i eth0 -p tcp -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.20.0.0/16 -d 172.20.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1912 -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.86.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT
-A OUTPUT -s 172.20.0.0/16 -d 192.168.86.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2019-01-24 19:31:43,000 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2019-01-24 19:31:43,051 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:43 2019 WARNING: file 'credentials.conf' is group or others accessible

2019-01-24 19:31:43,053 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:43 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Thu Jan 24 19:31:43 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10

2019-01-24 19:31:43,056 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:43 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
[info] OpenVPN started

2019-01-24 19:31:43,060 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:43 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.155.10:1912
Thu Jan 24 19:31:43 2019 UDP link local: (not bound)
Thu Jan 24 19:31:43 2019 UDP link remote: [AF_INET]37.120.155.10:1912

2019-01-24 19:31:44,845 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:44 2019 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1602', remote='link-mtu 1569'
Thu Jan 24 19:31:44 2019 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1532', remote='tun-mtu 1500'
Thu Jan 24 19:31:44 2019 WARNING: 'comp-lzo' is present in local config but missing in remote config, local='comp-lzo'

2019-01-24 19:31:44,846 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:44 2019 [TG-OVPN-CA] Peer Connection Initiated with [AF_INET]37.120.155.10:1912

2019-01-24 19:31:46,007 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:46 2019 TUN/TAP device tun0 opened

2019-01-24 19:31:46,010 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:46 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Jan 24 19:31:46 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-01-24 19:31:46,030 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:46 2019 /usr/bin/ip addr add dev tun0 local 10.35.0.26 peer 10.35.0.25

2019-01-24 19:31:46,036 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:46 2019 /root/openvpnup.sh tun0 1500 1605 10.35.0.26 10.35.0.25 init

2019-01-24 19:31:46,111 DEBG 'start-script' stdout output:
Thu Jan 24 19:31:46 2019 Initialization Sequence Completed

2019-01-24 19:31:46,146 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.35.0.26 different, marking for reconfigure

2019-01-24 19:31:46,151 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2019-01-24 19:31:46,163 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2019-01-24 19:31:46,193 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2019-01-24 19:31:46,199 DEBG 'privoxy-script' stderr output:
2019-01-24 19:31:46.198 7f66c1f96100 Info: Privoxy version 3.0.26
2019-01-24 19:31:46.198 7f66c1f96100 Info: Program name: /usr/bin/privoxy

2019-01-24 19:31:46,556 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 37.120.155.10

2019-01-24 19:31:46,578 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2019-01-24 19:31:46,582 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2019-01-24 19:31:46,586 DEBG 'watchdog-script' stdout output:
Script started, file is /home/nobody/typescript

2019-01-24 19:31:46,635 DEBG 'watchdog-script' stdout output:
Script done, file is /home/nobody/typescript

2019-01-24 19:31:48,628 DEBG 'flood-script' stdout output:
[info] Configuring Flood...

2019-01-24 19:31:48,629 DEBG 'flood-script' stdout output:
[info] Copying Flood config file /config/flood/config/config.js back to container...

2019-01-24 19:31:48,636 DEBG 'flood-script' stdout output:
[info] Starting Flood...

2019-01-24 19:31:49,718 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2019-01-24 19:31:49,747 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening

2019-01-24 19:31:49,760 DEBG 'watchdog-script' stdout output:
[info] Autodl-irssi not enabled, skipping startup
[info] Flood enabled, disabling initialisation of ruTorrent plugins...

2019-01-24 19:31:50,115 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 140550397706112 for <Subprocess at 140550397704168 with name flood-script in state RUNNING> (stdout)>
2019-01-24 19:31:50,115 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 140550398030048 for <Subprocess at 140550397704168 with name flood-script in state RUNNING> (stderr)>
2019-01-24 19:31:50,115 INFO exited: flood-script (exit status 0; expected)
2019-01-24 19:31:50,115 DEBG received SIGCLD indicating a child quit

January 24, 2019

Yes. Home LAN works fine. I’m able to load Flood in this docker and Deluge in the DelugeVPN docker from home. The problem is remote access.

I’m also able to log in remotely to the non-VPN containers such as Sonarr, suggesting it’s a VPN thing.

The port is forwarding correctly as best I can see.

January 24, 2019

I love the Binhex docker images. They're exactly what I need. Thank you.

I've previously had rtorrentvpn working perfectly on a Synology but have recently needed to move it to a Ubuntu Server setup. The problem I'm having is that I'm unable to access them remotely. I understand, from reading Q2 in the FAQ, that it's because tun and iptable_mangle need to be available. I think I've been able to load iptable_mangle by entering the following in Ubuntu Server shell

sudo modprobe iptable_mangle

But I don't know how to load tun. As such the logs look like this...

2019-01-23 23:14:53,085 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

Success! (Presumably). But...

2019-01-23 23:14:52,941 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2019-01-23 23:14:52,943 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

This post from Binhex has proved useful, but I don't understand how to get tun to load and resolve the issue above.

Help appreciated!

January 15, 2019

Thank you. Tip left!

STOP PRESS. Something just happened. Let me dig into it.

DavidAUK

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by DavidAUK

[Plugin] rclone

[Request] Docker rclone web UI

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - Jackett

[Support] binhex - Jackett

[Support] binhex - Jackett

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN