Closed enoch85 closed 5 years ago
this is the issue:-
-e ENABLE_FLOOD=yes \
if you enable flood (alternative ui to rutorrent) then you connect using a different port, in this case port 3000 (shown in readme), so either disable flood or connect using port 3000 instead of 9080.
note you can have both flood AND rutorrent web ui running by setting value of ENABLE_FLOOD to 'both'
Sorry, I posted a config from some debugging I did. With -e ENABLE_FLOOD=no \
it still doesn't work.
I'm having the same issues with MediaBox (based on your Docker container), but for Deluge. With MediaBox everything is setup automatically so there shoudln't be any error docker-wise.
Do I need to open some ports or something?
Here's my latest DEBUG log: https://0bin.net/paste/TTZAQ2hDwWxk16Un#ITXA-ARTydY89fey9yevJYwtX8TvpsRL9phuYmnBPKp
Please help! Thank you!
Tested to only enable flood now, and same result = timeout.
Thank you for your efforts!
I'm having the same issue with the timeout. It works fine with VPN disabled. It keeps waiting for a valid IP address every 30 seconds. Using PIA vpn. Here's the lines that keep repeating.
2018-12-31 02:53:02,883 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
2018-12-31 02:53:03,011 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.74.10.6'
2018-12-31 02:53:03,017 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '199.229.249.152'
2018-12-31 02:53:03,017 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '49785'
2018-12-31 02:53:03,024 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 49785
[debug] rTorrent incoming port is 49785
2018-12-31 02:53:03,024 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.74.10.6
[debug] rTorrent IP is 10.74.10.6
EDIT: I can't get haugene/transmission-openvpn to work either, so it's probably something I am doing wrong.
Here's my latest DEBUG log: https://0bin.net/paste/TTZAQ2hDwWxk16Un#ITXA-ARTydY89fey9yevJYwtX8TvpsRL9phuYmnBPKp
Please help! Thank you!
thats a successful start, so the issue is most probably one of the following:-
I'm having the same issue with the timeout. It works fine with VPN disabled. It keeps waiting for a valid IP address every 30 seconds. Using PIA vpn. Here's the lines that keep repeating.
2018-12-31 02:53:02,883 DEBG 'watchdog-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2018-12-31 02:53:03,011 DEBG 'watchdog-script' stdout output: [debug] Valid IP address from tunnel acquired '10.74.10.6' 2018-12-31 02:53:03,017 DEBG 'watchdog-script' stdout output: [debug] External IP address from tunnel is '199.229.249.152' 2018-12-31 02:53:03,017 DEBG 'watchdog-script' stdout output: [debug] Incoming port for tunnel is '49785' 2018-12-31 02:53:03,024 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 49785 [debug] rTorrent incoming port is 49785 2018-12-31 02:53:03,024 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.74.10.6 [debug] rTorrent IP is 10.74.10.6
EDIT: I can't get haugene/transmission-openvpn to work either, so it's probably something I am doing wrong.
what timeout are you referring to?, there is no timeout in that snipet of the log, the snipet you posted is completely normal, you have debug turned on so it will spit out a message confirming the current vpn ip address, externa;l ip and port every 30 seconds, same deal as the previous post, the issue is most probably host/lan related.
Sorry, I figured that 30 second message was a sign something wrong. I'll post my log here once the container goes back up, but I just want to make sure; This is what comes up when I do ifconfig. I want the middle entry for my LAN_NETWORK right?
docker0 Link encap:Ethernet HWaddr 02:42:24:76:96:95
inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
inet6 addr: fe80::42:24ff:fe76:9695/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1487 errors:0 dropped:0 overruns:0 frame:0
TX packets:2067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:170913 (170.9 KB) TX bytes:706690 (706.6 KB)
enp0s25 Link encap:Ethernet HWaddr 00:26:9e:9c:57:7c
inet addr:69.XX.XX.XX Bcast:69.XX.XX.XX Mask:255.255.255.248
inet6 addr: fe80::226:9eff:fe9c:577c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:113219 errors:0 dropped:0 overruns:0 frame:0
TX packets:22944 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:154079757 (154.0 MB) TX bytes:7175395 (7.1 MB)
Interrupt:20 Memory:df6e0000-df700000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:21806 (21.8 KB) TX bytes:21806 (21.8 KB)
This is what comes up when I do ifconfig. I want the middle entry for my LAN_NETWORK right?
yes, so LAN_NETWORK will be something like 69.x.x.x/29
Here's my log, although I think I see the problem now. https://0bin.net/paste/u235fRH-b--T0Hjx#hTtdlBy67w3b7FFyWY3hdS68Y4vn1v9NazRcSx08e0i
I'd imagine this line is the problem. "[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN"
I'd imagine this line is the problem. "[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN"
that will be your issue if you are attempting to access outside of your lan, yep.
@binhex
thats a successful start, so the issue is most probably one of the following:-
incorrect LAN_NETWORK - are you sure you have defined this correctly for your lan and CIDR is correct? apparmor - this can block access to apps on the host, try turning it off. firewall - you running anything like pfsense?, if so check this is not blocking
Thanks for the pointers!
So I double checked the firewall and nothing is blocked afaik. I even tried to opened everything (*) for that certain IP that the host is run on. Still no success.
My LAN is this
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.15.14 netmask 255.255.255.0 broadcast 192.168.15.255
inet6 fe80::20c:29ff:fef4:3670 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:f4:36:70 txqueuelen 1000 (Ethernet)
RX packets 3013 bytes 2667600 (2.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1703 bytes 2139185 (2.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
So my LAN variable becomes the one in the logs which is 192.168.15.0/24, though I'm trying to connect from 192.168.2.161 which is my laptop and have access to ALL the subnets in my network. So it should work.
Regarding AppArmor I purged that from my server, so it doesn't even exist at all now.
But I still can't connect via browser.
This is my docker ps -a
if it helps (I'm only trying to access flood now hence I removed the lines regarding ports for ruTorrent):
065024a43c1b binhex/arch-rtorrentvpn "/usr/bin/tini -- /b…" 15 minutes ago Up 15 minutes 0.0.0.0:3000->3000/tcp, 5000/tcp, 9080/tcp, 9443/tcp, 49160/tcp, 0.0.0.0:8118->8118/tcp, 49170/tcp rtorrentvpn
hough I'm trying to connect from 192.168.2.161 which is my laptop and have access to ALL the subnets in my network
your laptop may have access to all subnets but the iptable rules are very tight for this image (for good reason) and thus if your laptop has a source ip of 192.168.2.xx then it wont be able to connect due to LAN_NETWORK being set to 192.168.15.0/24.
solution to this is to add in multiple networks, so try setting LAN_NETWORK to:-
-e LAN_NETWORK=192.168.15.0/24,192.168.2.0/24
@binhex Thanks I will try that.
I just tried to access without PIA and it worked.
Will get back to you. Thanks for your help so far!
@binhex
OMG! I can connect! :D
So far I've tried with flood and I get this: https://i.imgur.com/xLqUegu.png
Is it normal that it takes a while in the beginning or do I need to open ports in the firewall (OPNsense) for it to work properly?
A donation is coming your way when this is working, be sure about that!
Sorry, I needed to connect again (F5) and now it seems to work!
Will do some more tests and then close this issue and donate.
THANK YOU!
@binhex So I can add torrents but they won't download.
Which ports do I need to open for it to work? In my old installation I use 6881 - 6999, does the same rules apply to flood?
OK, so I opened 59292 which is the port in Connectivity in flood, still no success.
Oh, I needed to start it duuh
So everything works! I will donate later today!
Thanks a ton!
@binhex
One last question, which are the safest permissions to run this with?
Right now it's root:root and UID 000 which doesn't feel safe. Any advice here?
I'm thinking 1000:1000 and UID 750, or is there anything better?
One last question, which are the safest permissions to run this with?
you can run this with any user and group you want, but you must ensure that the the specified user and group have permissions to write to whatever your volumes are pointing at on the host side, also if you do change the PUID and PGID after installation then you will need to delete the file /config/perms.txt to force the permissions to be changed to the specified user and group (or alternatively delete everything and let it re-create it all with the new user and group).
JFTR, this is my final config:
docker run -d \
--cap-add=NET_ADMIN \
-p 3000:3000 \
-p 8118:8118 \
--name=rtorrentvpn \
-v /mnt/PlexDownloads/:/data \
-v /root/docker/config:/config \
-v /etc/localtime:/etc/localtime:ro \
-e VPN_ENABLED=yes \
-e VPN_USER=pno01 \
-e VPN_PASS=mmyeah \
-e VPN_PROV=pia \
-e STRICT_PORT_FORWARD=yes \
-e ENABLE_PRIVOXY=yes \
-e ENABLE_FLOOD=yes \
-e ENABLE_AUTODL_IRSSI=yes \
-e LAN_NETWORK=192.168.15.14/32,192.168.2.161/32 \
-e NAME_SERVERS=9.9.9.9,149.112.112.112 \
-e DEBUG=false \
-e PHP_TZ=Europe/Stockholm \
-e UMASK=022 \
-e PUID=1001 \
-e PGID=1001 \
binhex/arch-rtorrentvpn
useradd rtorrentvpn
and then set a strong password. UMASK 022
is Ubuntu default. Works like a charm.
excellent!, thanks for the donation.
Hi!
Thanks for a great docker, and an easier way to enable VPN for rtorrent with ruTorrent GUI.
I have my own installation running on another server but now I'm looking to enable VPN and hide traffic, hence this Docker image.
Though being quite familiar with Linux in general I can't get ruTorrent up and running. I ran the
docker run
stuff with debug mode and everything seems to check out correctly, but when accessing http://host-ip:9080 it fails to connect from my laptop (which have * access to all subnets in my network).So my question I guess is, do I need to install Nginx/APache on the host that runs the docker (Ubuntu 18.04.1) and reverse proxy the Docker container, or am I missing something here?
I run PIA and used the provided example config with my own changes ofc.
This is some of the DEBUG output:
This is my config:
Any help is greatly appreciated! Thanks!