[Support] binhex - rTorrentVPN


Recommended Posts

For anyone who had port forwarding break after an update, my solution was to delete the Additional_ports variable and re-create it as a port type. Not sure why it switched during the update, but it's an easy fix.
This is bad advise additional_ports has to be an environment variable, it is not a port.

Sent from my CLT-L09 using Tapatalk

Link to comment

i have a hard time following those new changes. i'm running sonarr through rtorrentvpn, with the ip tables change i need to adjust the container networks if i understoof correctly. i'm following A24, trying to remove Host Port 1 and 2 from the Docker Container but those fields are not allowed to be empty. what can i do?

Link to comment
1 hour ago, binhex said:

This is bad advise additional_ports has to be an environment variable, it is not a port.

Sent from my CLT-L09 using Tapatalk
 

Well shoot. How is the port supposed to get passed if you're using bridged mode? Or is that something that shouldn't be used now (I'm not using wireguard, so I thought it was still okay to use bridged mode)?

Edited by nate1749
Link to comment

For some reason rtorrent stops downloading/uploading after a few gigabytes have been snatched. It will still show peers but all traffic stops. It doesn't happen in another client. I will test whether it's related to network stack sharing with thelounge. I've mapped the port for thelounge and added it to ADDITIONAL_PORTS.

I'm not seeing any errors in the log and curl ipconfig.io confirms it's on the vpn ip.

I will test some more and see if it's related to the network stack sharing with thelounge.

 

Edit: disconnecting thelounge from the the rtorrentvpn network stack made it resume downloading immediately.

 

Edit 2: Oh well it stopped again, so it doesn't seem to be related to network stack sharing.

 

Edited by zx81
Link to comment
17 hours ago, nate1749 said:

Well shoot. How is the port supposed to get passed if you're using bridged mode? Or is that something that shouldn't be used now (I'm not using wireguard, so I thought it was still okay to use bridged mode)?

 so you add the ports to the ADDITIONAL_PORTS env var AND add all the ports defined in ADDITIONAL_PORTS as 'ports' too, see Q24 on how to network bind correctly:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to comment

I just tried wireguard as well. It works great for a while and then all of a suddon just drops the connection. curl ipconfig.io hangs for a minute or so and then says could not resolve host.

 

How would I go about debugging this?

Link to comment
5 minutes ago, zx81 said:

I just tried wireguard as well. It works great for a while and then all of a suddon just drops the connection. curl ipconfig.io hangs for a minute or so and then says could not resolve host.

 

How would I go about debugging this?

sounds like your vpn provider is dropping the connection, do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

 

Link to comment
18 hours ago, binhex said:

sounds like your vpn provider is dropping the connection, do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

 

It looks like that may the case. I'm using PIA so I don't get it, though. It's also happening with Mullvad. I've tried running wireguard in the host os and disabling the vpn for rtorrent and the same thing is happening.

The supervisord.log is not giving much detail.

 

2021-02-28 14:35:51,147 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2021-02-28 14:37:51,264 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...

 

If I disconnect rtorrent and wait a while the connection gets responsive in the OS again.

The connection is also dropping when torrenting from a windows machine using the same vpn. 

I guess it's pretty much out of your hands to do anything about this. If you have any suggestions I'd be happy to hear it, though.

 

Regards.

 

Link to comment

Out of nowhere my container is messing up. I've had it running with no problem for months and now I am getting a bunch of errors.

 

[01.03.2021 08:56:39] WebUI started.
[01.03.2021 08:56:42] _cloudflare: Plugin will not work. rTorrent user can't access external program (python).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] autotools: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] create: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] datadir: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] history: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] loginmgr: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] ratio: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] retrackers: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rss: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rutracker_check: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] scheduler: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] trafic: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] unpack: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] xmpp: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (pgrep).
[01.03.2021 08:56:42] mediainfo: Plugin will not work. rTorrent user can't access external program (mediainfo).
[01.03.2021 08:56:42] rss: Some functionality will be unavailable. rTorrent user can't access external program (curl).
[01.03.2021 08:56:42] screenshots: Plugin will not work. rTorrent user can't access external program (ffmpeg).
[01.03.2021 08:56:42] spectrogram: Plugin will not work. rTorrent user can't access external program (sox).
[01.03.2021 11:40:31] The request to rTorrent has timed out.

 

That is from the log of the webui. Is anyone else having this issue or is it just me?

 

edit: I should also add that I can no longer use those plugins. So i can't move files in rutorrent because the plugin that adds "save to" to the right click menu is not loaded. It's pretty frustrating because I have been moving files recently and this has brought that to a full stop.

Edited by Trevo525
  • Like 3
Link to comment

I'm having a strange issue with the rtorrentVPN container. I installed this a week or so ago and it has been running fine but overnight it crashed and then every time I boot it up, it will only work until for a few minutes before rtorrent crashes. I can open the rutorrent gui but none of my torrents show up and it just says it can't connect to rtorrent (see attached photo). One time it worked for a day or so, but only because (seemingly) I never actually opened the webgui. That seems to be what kills it.

 

Per your instructions I:

1) Deleted the supervisord log file

2) Removed the container

3) Rebuilt the container using my stack

 

I waited until I knew it had crashed and then copied the log file.

 

If you could point me to some way I can fix this, I would greatly appreciate it.

 

Thanks!

Rtorrent Error.jpg

supervisord.log

Link to comment
7 hours ago, Trevo525 said:

Out of nowhere my container is messing up. I've had it running with no problem for months and now I am getting a bunch of errors.

 


[01.03.2021 08:56:39] WebUI started.
[01.03.2021 08:56:42] _cloudflare: Plugin will not work. rTorrent user can't access external program (python).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] autotools: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] create: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] datadir: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] history: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] loginmgr: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] ratio: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] retrackers: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rss: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rutracker_check: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] scheduler: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] trafic: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] unpack: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] xmpp: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (pgrep).
[01.03.2021 08:56:42] mediainfo: Plugin will not work. rTorrent user can't access external program (mediainfo).
[01.03.2021 08:56:42] rss: Some functionality will be unavailable. rTorrent user can't access external program (curl).
[01.03.2021 08:56:42] screenshots: Plugin will not work. rTorrent user can't access external program (ffmpeg).
[01.03.2021 08:56:42] spectrogram: Plugin will not work. rTorrent user can't access external program (sox).
[01.03.2021 11:40:31] The request to rTorrent has timed out.

 

That is from the log of the webui. Is anyone else having this issue or is it just me?

 

After the most recent update, couple days ago, I am having the exact same issue.

 

image.png.e7877a2a91f3dd2290640a2bfa6934d6.png

  • Like 1
Link to comment
15 hours ago, Trevo525 said:

Out of nowhere my container is messing up. I've had it running with no problem for months and now I am getting a bunch of errors.

 


[01.03.2021 08:56:39] WebUI started.
[01.03.2021 08:56:42] _cloudflare: Plugin will not work. rTorrent user can't access external program (python).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] autotools: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] create: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] datadir: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] history: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] loginmgr: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] ratio: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] retrackers: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rss: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rutracker_check: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] scheduler: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] trafic: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] unpack: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] xmpp: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (pgrep).
[01.03.2021 08:56:42] mediainfo: Plugin will not work. rTorrent user can't access external program (mediainfo).
[01.03.2021 08:56:42] rss: Some functionality will be unavailable. rTorrent user can't access external program (curl).
[01.03.2021 08:56:42] screenshots: Plugin will not work. rTorrent user can't access external program (ffmpeg).
[01.03.2021 08:56:42] spectrogram: Plugin will not work. rTorrent user can't access external program (sox).
[01.03.2021 11:40:31] The request to rTorrent has timed out.

 

That is from the log of the webui. Is anyone else having this issue or is it just me?

 

edit: I should also add that I can no longer use those plugins. So i can't move files in rutorrent because the plugin that adds "save to" to the right click menu is not loaded. It's pretty frustrating because I have been moving files recently and this has brought that to a full stop.

No, it's not just you. I've had the same problem crop up in just the past few days with the container previously working fine for months.

 

I've tried starting the container fresh with just my VPN details and I still get this problem. So, I think something more sinister is going on.

Link to comment

I am not able to see the privoxy logs in any way when enabled; I might be doing something wrong, but I checked the logfile, it's 0 bytes. Seems the aggregated log doesn't include the privoxy log like the privoxy containers. I tried debug=true and same results. Any ideas?

 

Thanks!

Link to comment
3 hours ago, Zeee said:

No, it's not just you. I've had the same problem crop up in just the past few days with the container previously working fine for months.

 

I've tried starting the container fresh with just my VPN details and I still get this problem. So, I think something more sinister is going on.

While we wait for @binhex to investigate the bug, you can pull the previous release as that was working fine.

 

image.png.627ab674de8ebbe08d73dada758c1657.png

 

Add ":rtorrent-ps-1.1.r54.ga787dd9-1-29" after "binhex/arch-rtorrentvpn". This will pull this specific release. If you ever want to go back to the latest release, you can use ":latest" or just "binhex/arch-rtorrentvpn". You can check the releases here https://github.com/binhex/arch-rtorrentvpn/releases.

 

Hope this helps.

  • Like 1
Link to comment
49 minutes ago, beinghitesh said:

While we wait for @binhex to investigate the bug, you can pull the previous release as that was working fine.

 

image.png.627ab674de8ebbe08d73dada758c1657.png

 

Add ":rtorrent-ps-1.1.r54.ga787dd9-1-29" after "binhex/arch-rtorrentvpn". This will pull this specific release. If you ever want to go back to the latest release, you can use ":latest" or just "binhex/arch-rtorrentvpn". You can check the releases here https://github.com/binhex/arch-rtorrentvpn/releases.

 

Hope this helps.

Good temporary solution. Thank you!

Link to comment

I just updated and port forwarding seems to have some problems. It was working perfectly before the update  (in multiple docker containers using different PIA endpoints).

 

Everything seems to be OK in the logs. It retrieves the port from the PIA endpoint:

 

2021-03-03 09:25:45,174 DEBG 'watchdog-script' stdout output:
[info] rTorrent incoming port 49160 and VPN incoming port 36936 different, marking for reconfigure

 

Then, after:

 

2021-03-03 09:26:04,357 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

 

The logs start outputing this:

 

2021-03-03 09:40:44,618 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '36936'

2021-03-03 09:55:44,787 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '36936'

2021-03-03 09:56:24,526 DEBG 'watchdog-script' stdout output:
[info] rtorrent incoming port closed, marking for reconfigure

2021-03-03 10:10:44,958 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '36936'

 

However, the port shows as "Closed" in the UI (red exclamation mark) even after hours. 

Also, my clients were pretty consistent in the upload per day (around 500GB per day, sometimes some container would upload 1TB) and the last day I only upload between 5 - 30GB (and some of them less than 1GB), so clearly there's something not there yet.

 

I'm using Wireguard with `privileged=true`. All was working before this update. I think the last time I updated was 1-2 months ago, I'm not sure, but I was already using wireguard and everything was working fine.

Link to comment

Looks like there was an update overnight which the container was auto updated to. Now none of my torrents can get a connection. Not sure if its related to the update, or if PIA is down.

 

EDIT: I rolled back to rtorrent-ps-1.1.r54.ga787dd9-1-29 and my problems went away

 

2021-03-04 07:47:14,731 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'au-sydney.privacy.network'...

2021-03-04 07:47:14,957 DEBG 'start-script' stdout output:
[info] Default route for container is 172.18.0.1

2021-03-04 07:47:14,976 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.18.0.0/16

2021-03-04 07:47:14,981 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2021-03-04 07:47:14,983 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2021-03-04 07:47:14,984 DEBG 'start-script' stdout output:
default via 172.18.0.1 dev eth0
172.18.0.0/16 dev eth0 proto kernel scope link src 172.18.0.6
192.168.1.0/24 via 172.18.0.1 dev eth0

2021-03-04 07:47:14,985 DEBG 'start-script' stdout output:
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 172.18.0.0 dev eth0 table local proto kernel scope link src 172.18.0.6
local 172.18.0.6 dev eth0 table local proto kernel scope host src 172.18.0.6
broadcast 172.18.255.255 dev eth0 table local proto kernel scope link src 172.18.0.6

2021-03-04 07:47:14,985 DEBG 'start-script' stdout output:
--------------------

2021-03-04 07:47:14,990 DEBG 'start-script' stdout output:
iptable_mangle 16384 1
ip_tables 28672 4 iptable_filter,iptable_raw,iptable_nat,iptable_mangle

2021-03-04 07:47:14,990 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2021-03-04 07:47:15,604 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2021-03-04 07:47:15,607 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.18.0.0/16 -d 172.18.0.0/16 -j ACCEPT
-A INPUT -s 103.2.196.162/32 -i eth0 -j ACCEPT
-A INPUT -s 103.2.196.172/32 -i eth0 -j ACCEPT
-A INPUT -s 103.2.196.171/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 9443 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.18.0.0/16 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -s 172.18.0.0/16 -d 172.18.0.0/16 -j ACCEPT
-A OUTPUT -d 103.2.196.162/32 -o eth0 -j ACCEPT
-A OUTPUT -d 103.2.196.172/32 -o eth0 -j ACCEPT
-A OUTPUT -d 103.2.196.171/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 9443 -j ACCEPT
-A OUTPUT -s 172.18.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT

2021-03-04 07:47:15,609 DEBG 'start-script' stdout output:
--------------------

2021-03-04 07:47:15,613 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2021-03-04 07:47:15,630 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible


2021-03-04 07:47:15,641 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2021-03-04 07:47:15,644 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2021-03-04 07:47:15,658 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.13.246.156 dev wg0

2021-03-04 07:47:15,668 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2021-03-04 07:47:15,695 DEBG 'start-script' stderr output:
[#] ip -4 route add 10.0.0.0/8 dev wg0

2021-03-04 07:47:15,697 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2021-03-04 07:48:11,811 DEBG 'start-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2021-03-04 07:48:11,817 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2021-03-04 07:48:11,831 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'...


2021-03-04 07:48:11,844 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'...


2021-03-04 07:48:11,861 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'...


2021-03-04 07:48:11,875 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'...
[info] Show name servers defined for container

2021-03-04 07:48:11,876 DEBG 'start-script' stdout output:
nameserver 209.222.18.222
nameserver 84.200.69.80
nameserver 37.235.1.174
nameserver 1.1.1.1
nameserver 209.222.18.218
nameserver 37.235.1.177
nameserver 84.200.70.40
nameserver 1.0.0.1

2021-03-04 07:48:11,876 DEBG 'start-script' stdout output:
[info] Show contents of hosts file

2021-03-04 07:48:11,876 DEBG 'start-script' stdout output:
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.18.0.6 dbe3ded8d535
103.2.196.162 au-sydney.privacy.network

2021-03-04 07:48:11,880 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2021-03-04 07:48:11,880 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2021-03-04 07:48:11,881 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'au-sydney.privacy.network' is port forward enabled...

2021-03-04 07:48:11,888 DEBG 'start-script' stdout output:
[warn] PIA VPN info API currently down, skipping endpoint port forward check

2021-03-04 07:48:13,768 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34854'

2021-03-04 07:48:41,882 DEBG 'start-script' stdout output:
[info] Sending 'down' command to WireGuard due to dns failure...

2021-03-04 07:48:41,884 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...

2021-03-04 07:48:41,897 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible


2021-03-04 07:48:41,903 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2021-03-04 07:48:41,991 DEBG 'start-script' stderr output:
[#] '/root/wireguarddown.sh'

2021-03-04 07:48:41,996 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

2021-03-04 07:48:41,997 DEBG 'start-script' stdout output:
[info] WireGuard interface 'down'

2021-03-04 07:48:41,998 DEBG 'start-script' stderr output:
/root/prerunget.sh: line 1: break: only meaningful in a `for', `while', or `until' loop

2021-03-04 07:48:41,999 DEBG 'start-script' stderr output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]


2021-03-04 07:48:41,999 DEBG 'start-script' stderr output:
/root/getvpnport.sh: line 1: break: only meaningful in a `for', `while', or `until' loop

2021-03-04 07:48:42,001 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2021-03-04 07:48:42,014 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible


2021-03-04 07:48:42,023 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2021-03-04 07:48:42,026 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2021-03-04 07:48:42,041 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.13.246.156 dev wg0

2021-03-04 07:48:42,052 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2021-03-04 07:48:42,080 DEBG 'start-script' stderr output:
[#] ip -4 route add 10.0.0.0/8 dev wg0

2021-03-04 07:48:42,081 DEBG 'start-script' stderr output:

 

Edited by docbrown
Link to comment

I also have the same exact issue currently as above. After a rollback to aforementioned version, it works. Also rolled back prixovy images too, since those also weren't working.

Edited by Rinzler
Link to comment
6 minutes ago, Rinzler said:

I also have the same exact issue currently as above. After a rollback to aforementioned version, it works. Also rolled back prixovy images too, since those also weren't working.

 

17 hours ago, docbrown said:

EDIT: I rolled back to rtorrent-ps-1.1.r54.ga787dd9-1-29 and my problems went away

please pull down 'latest' the dns resolution issue has been resolved.

  • Like 1
Link to comment

Hi everyone, i have an slightly annoying issue: evcerytime this containter is restarted, all torrents with ratio >= 1 are given the Finished state, therefore they don't seed. I have to manually start the seeding. Does someone know how to fix this?

Link to comment
On 3/3/2021 at 10:26 AM, Jeffarese said:

I just updated and port forwarding seems to have some problems. It was working perfectly before the update  (in multiple docker containers using different PIA endpoints).

 

Everything seems to be OK in the logs. It retrieves the port from the PIA endpoint:

 


2021-03-03 09:25:45,174 DEBG 'watchdog-script' stdout output:
[info] rTorrent incoming port 49160 and VPN incoming port 36936 different, marking for reconfigure

 

Then, after:

 


2021-03-03 09:26:04,357 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

 

The logs start outputing this:

 


2021-03-03 09:40:44,618 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '36936'

2021-03-03 09:55:44,787 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '36936'

2021-03-03 09:56:24,526 DEBG 'watchdog-script' stdout output:
[info] rtorrent incoming port closed, marking for reconfigure

2021-03-03 10:10:44,958 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '36936'

 

However, the port shows as "Closed" in the UI (red exclamation mark) even after hours. 

Also, my clients were pretty consistent in the upload per day (around 500GB per day, sometimes some container would upload 1TB) and the last day I only upload between 5 - 30GB (and some of them less than 1GB), so clearly there's something not there yet.

 

I'm using Wireguard with `privileged=true`. All was working before this update. I think the last time I updated was 1-2 months ago, I'm not sure, but I was already using wireguard and everything was working fine.

 

I'm still having this problem. I updated again and the problem persists:

 

Ports don't seem to be forwarded or configured in rTorrent correctly:

 

2021-03-08 11:34:04,443 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

2021-03-08 11:49:04,604 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

2021-03-08 11:53:23,017 DEBG 'watchdog-script' stdout output:
[info] rtorrent incoming port closed, marking for reconfigure

2021-03-08 12:04:04,769 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

2021-03-08 12:19:04,932 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

2021-03-08 12:23:30,398 DEBG 'watchdog-script' stdout output:
[info] rtorrent incoming port closed, marking for reconfigure

2021-03-08 12:34:05,103 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

2021-03-08 12:49:05,273 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

2021-03-08 12:53:37,361 DEBG 'watchdog-script' stdout output:
[info] rtorrent incoming port closed, marking for reconfigure

2021-03-08 13:04:05,445 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

2021-03-08 13:19:05,617 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22390'

 

Any ideas?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.