[Support] binhex - rTorrentVPN


Recommended Posts

5 minutes ago, binhex said:

there are people using this docker image to seed thousands of torrents so by the sound of it you most probably have not hit the limit of what rtorrent/rutorrent can handle. however, having that many torrents seeding does require a reasonably powerful system, and perhaps some tweaking too

 

so i guess the support from my seedbox a while back was not 100% accurate and that it was more of an issue with whatever hardware they use, missing optimizations, and/or maybe even if they use btrfs. Will dedicate a couple drives for p2p share to be on and disable cache on that share to remove possible problems. Would also love to know what tricks Cat_Seeder recommends

Link to comment
42 minutes ago, binhex said:

there are people using this docker image to seed thousands of torrents so by the sound of it you most probably have not hit the limit of what rtorrent/rutorrent can handle. however, having that many torrents seeding does require a reasonably powerful system, and perhaps some tweaking too, @Cat_Seeder is an old hand at this sort of thing and maybe able to tell you more about any tweaks you have to make to get things running smoothly.

 

one thing to be aware of that i have seen in the past is that btrfs can be an issue, especially when in a cache pool, im assuming you are an unraid user, if you are then you could try a single unassigned device and write to that and see what your performance is like - personally i have a dislike of btrfs and all my drives are xfs only, including my cache drive (nvme).

 

Thank you so much for the response! Yeah I know I've read before that around 2000 torrents is where it can slow down which is why I was so confused. I know my system isn't that powerful, my CPU (Xeon E3-1230 v3) passmark's at 6806 and ruTorrent only gets half the cores and shares those cores. Although I've never seen my CPU max load due to anything going on with ruTorrent. It does go up if it's checking torrents but nothing concerning.

 

Yeah I'm an Unraid user, my shares are on xfs and my cache is btrfs. I actually have always had my media share, where my torrent downloads go, set to "No" for using the cache since I did the math and figured out that SSD is pointless if I'm writing at my internet/VPN's half gigabit speed. So torrents should be downloading to xfs file system.

 

As far as performance I noticed changing my UI update to 3000ms (vs 1000ms) helped a tiny bit for preventing timeouts. And I disabled some plugins that I was clearly not using, although that didn't seem to help honestly.

 

26 minutes ago, Cull2ArcaHeresy said:

so i guess the support from my seedbox a while back was not 100% accurate and that it was more of an issue with whatever hardware they use, missing optimizations, and/or maybe even if they use btrfs. Will dedicate a couple drives for p2p share to be on and disable cache on that share to remove possible problems. Would also love to know what tricks Cat_Seeder recommends

 

Yeah definitely leaning more towards that my hardware is just not up to what I was asking it to do.

 

I know binhex just said btrfs can be an issue in the cache pool, but I'm considering switching back to cache "prefer" so new downloads will be on the SSD vs HDD. Maybe that could help because I think my performance issues are usually when new stuff downloads. If nothing is downloading it can be a bit more stable. Couldn't hurt to try. I'll have to do more research on btrfs vs xfs for cache but I'm not sure if that's too off topic for this support thread.

 

Thanks again!

Edited by s449
Typo
Link to comment

Any reason why it needs to bind so often?

 

Client crashed randomly whilst deleting a 10GB file.

 

Here's the log:

 

Quote

2021-02-23 15:20:18,612 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 15:35:18,686 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 15:50:18,758 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 16:05:18,839 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 16:20:18,914 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 16:35:18,998 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 16:50:19,073 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 16:52:26,887 DEBG 'rutorrent-script' stderr output:
2021/02/23 16:52:26 [error] 2144#2144: *203 upstream timed out (110: Unknown error) while reading response header from upstream, client: 192.168.1.133, server: localhost, request: "GET /plugins/autodl-irssi/getfiles.php?_=1614091794234 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.50:9080", referrer: "http://192.168.1.50:9080/"

2021-02-23 16:52:26,928 DEBG 'rutorrent-script' stderr output:
2021/02/23 16:52:26 [error] 2146#2146: *206 upstream timed out (110: Unknown error) while reading response header from upstream, client: 192.168.1.133, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=&_=1614091794235 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.50:9080", referrer: "http://192.168.1.50:9080/"

2021-02-23 16:54:57,522 DEBG 'rutorrent-script' stderr output:
2021/02/23 16:54:57 [error] 2144#2144: *205 upstream timed out (110: Unknown error) while reading response header from upstream, client: 192.168.1.133, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=&_=1614091794279 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.50:9080", referrer: "http://192.168.1.50:9080/"

2021-02-23 16:57:27,930 DEBG 'rutorrent-script' stderr output:
2021/02/23 16:57:27 [error] 2144#2144: *205 upstream timed out (110: Unknown error) while reading response header from upstream, client: 192.168.1.133, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=&_=1614091794321 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.50:9080", referrer: "http://192.168.1.50:9080/"

2021-02-23 17:01:11,558 DEBG 'rutorrent-script' stderr output:
2021/02/23 17:01:11 [error] 2144#2144: *602 upstream timed out (110: Unknown error) while reading response header from upstream, client: 192.168.1.133, server: localhost, request: "GET /php/getplugins.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.50:9080", referrer: "http://192.168.1.50:9080/"

2021-02-23 17:05:19,175 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

2021-02-23 17:20:19,303 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25538'

 

Couldn't access the web UI at all after this:

 

Just getting an infinite loading circle when trying to load the frontend.

Link to comment
23 minutes ago, plantsandbinary said:

Any reason why it needs to bind so often?

yes its a pia constraint, they require you re-confirm (rebind) the incoming port, if you fail to do this the port will be unassigned and you will loose port forwarding, nothing i can do about it, however....

 

24 minutes ago, plantsandbinary said:

Client crashed randomly whilst deleting a 10GB file.

this is highly likely to NOT be related to the rebind, the rebind is purely a hit of the pia api, it does not change the port or reconfigure rtorrent/rutorrent, so the crash will not be related to this.

Link to comment

Alright thanks. For some reason the container is still randomly timing out after a while and taking ages to load. I have a pretty powerful server and only 1180 torrents. I've also turned off autodl-irssi. I'm going to remove some of the torrents I think and see if it manages to improve.

 

The log is utterly useless :( it's totally empty and doesn't show anything out of the ordinary except the rebinds but the ruTorrent web page just shows:  Loading...

 

The only other possible hint I have is that when this started happening, a bunch of my torrents went red (errored) and give the error:

 

Tracker: [Object operator [peers] could not find element]

Link to comment
8 minutes ago, plantsandbinary said:

Alright thanks. For some reason the container is still randomly timing out after a while and taking ages to load. I have a pretty powerful server and only 1180 torrents. I've also turned off autodl-irssi. I'm going to remove some of the torrents I think and see if it manages to improve.

 

The log is utterly useless :( it's totally empty and doesn't show anything out of the ordinary except the rebinds but the ruTorrent web page just shows:  Loading...

 

The only other possible hint I have is that when this started happening, a bunch of my torrents went red (errored) and give the error:

 

Tracker: [Object operator [peers] could not find element]

a question that may sound random (but isnt), are you by any chance using a cache pool? or have your cache drive formatted to BTRFS?, if so this maybe part of the issue, BTRFS is a wee bit crap when it comes to disk I/O and can cause all sorts of fun and games when using a torrent client, this is double so when using a cache pool, i have had much better experience overall with XFS, but obviously you cannnot (currently) create a XFS cache pool on unraid, so you are then limited to a single cache device, or multi pool single cache devices in 6.9.x

Link to comment

Thanks for this great docker, binhex!

 

I'm using this on two machines. a synology and in ubuntu. Using PIA

It's working but not port forwarding. Is it supposed to work without the usual port forwarding you have to do from your router? If so I'm must be overseeing somthing as the port icon on the bottom of rutorrent stays red with the hover message "Port is closed".

 

Can you advise?

Link to comment

I have some other dockers using the binhex-rtorrentvpn docker for VPN, and cannot access their UIs. My workflow had been to add a port variable to the binhex docker with the UI port of the other docker (following a SpaceInvader video I think). Summarizing Q25 from the FAQ, add ports to 'ADDITIONAL_PORTS' env var value for the VPN container," should I delete all those port entries? I have also updated this docker, but don't see the ADDITIONAL_PORTS env variable - just add it?

 

edit: Just adding the variable worked. Also had to go into each docker and change config from IP to localhost (Q24).

Edited by tiphae
Link to comment

Latest release on synology doesn't work (in Synology Docker)
Container is in a constant reboot loop with error: FATAL: Kernel too old

 

Tried on a DS1817+ on both Synology DSM 6.2 as DSM 7 Beta.

 

Any idea on how to fix this?

 

 

EDIT: reverted to rtorrent-ps-1.1.r54.ga787dd9-1-30 and that runs fine.

Edited by Borkjev
extra info
Link to comment
On 2/25/2021 at 7:02 PM, binhex said:

indeed!, just to be clear read Q15:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

so in order to debug this please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Thanks! 

 

I managed to get things going. I removed a port I had set up in rtorrent.rc when testing with another vpn provider. Once that was gone the port forwarding started working as expected.

 

Is it in any way problematic to have other containers sharing the network stack of rtorrentvpn to utilize the vpn connection?

Link to comment
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
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

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.