[Support] binhex - rTorrentVPN


Recommended Posts

6 minutes ago, limes said:

I hope this might help. The container also times out when trying to access the WebUI from port 9080, but it works fine using port 9443. For now I'll stick to the rTorrent release, as I already changed my config one time today.

I confirm it works with me. Thank you

Link to comment
5 minutes ago, limes said:

I hope this might help. The container also times out when trying to access the WebUI from port 9080, but it works fine using port 9443. For now I'll stick to the rTorrent release, as I already changed my config one time today.

Interesting, yep. Still on earlier (new) release and same here. My reverse proxy (NGINX proxy manager) points to 9080 and works (via https and SSL cert) and locally on 9443

Link to comment
9 minutes ago, Rikul said:

I confirm it works with me. Thank you

thanks for restoring my sanity! so for me rollback to rtorrent-ps was seamless, everything works as it was and a clean install of rtorrent-ps also works!, glad its working for you too, by any chance are you also accessing the web ui via 9443? (or host port defined for container port 9443).

Link to comment

hmm so it appears that http is broken for nginx, most probably due to an upgrade of nginx changing the config options perhaps, any nginx guru's please feel free to look at /config/nginx/config/nginx.conf and tell me what looks wrong with it for latest nginx, it certainly seems to work correctly for https 'server' block in the config file.

Link to comment
55 minutes ago, binhex said:

thanks for restoring my sanity! so for me rollback to rtorrent-ps was seamless, everything works as it was and a clean install of rtorrent-ps also works!, glad its working for you too, by any chance are you also accessing the web ui via 9443? (or host port defined for container port 9443).

So with a reverse proxy I can access externaly trough 9443.

My reverse proxy was configured with swag.

Internaly, trough 9080 I got the time out error, but I got acess trough 9443.

All my torrents and my config match the previous container.

Link to comment

I didn't think to try the HTTPS port. That works for me on latest as well, but now I'm seeing this in the logs:

 

 

2021-02-12 15:37:43,868 DEBG 'watchdog-script' stderr output:
/home/nobody/rtorrent.sh: line 24: rtxmlrpc: command not found

 

2021-02-12 15:40:15,037 DEBG 'watchdog-script' stdout output:
[warn] Incoming port range not defined, unable to bind IP address

 

Everything seems to be working though.

Edited by psycho_asylum
Link to comment
25 minutes ago, psycho_asylum said:

I didn't think to try the HTTPS port. That works for me on latest as well, but now I'm seeing this in the logs:

 

 

2021-02-12 15:37:43,868 DEBG 'watchdog-script' stderr output:
/home/nobody/rtorrent.sh: line 24: rtxmlrpc: command not found

 

2021-02-12 15:40:15,037 DEBG 'watchdog-script' stdout output:
[warn] Incoming port range not defined, unable to bind IP address

 

Everything seems to be working though.

 

rtxmlrpc is part of pyrocore. @binhex, without pyrocore we'll not have rtxmlrpc, and reverting to xmlrpc means that port-forwarding will need /RPC2 mounts and we'll be back discussing security shenanigans. I understand that you want to get alway from rtorrent-ps, but can you maybe include an individual release of pyrocore in the image?

  • Like 1
Link to comment

So i updated and couldent get to the web gui. Read some recent posts here and figured i had to get a new rtorrent.rc file. Deleted it but still no joy. For fun i disabled my vpn (pia) and then i got in. Looked through the log and all i see is no errors only two warnings

 

2021-02-13 12:46:46 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.

2021-02-13 12:46:46 WARNING: file 'credentials.conf' is group or others accessible

(text with yellow background is a warning not error right?)

 

Got new ovpn file form pia and still same problem (tried a custom config and a couple premade by pia)

 

So tried some more and figured out that using port 9443 it works... So seems its the same problem as other are having. Didn't realize i had to use https as when just clicking on the web gui uses http...

 

But like i said earlier it works fine without my vpn on port 9080 if that helps others.

 

 

Latest update fixed it for me @binhex Its now working on the usual 9080 port!

Edited by PetterH
Link to comment

hi, i can't seem to limit the maximum numbre of concurrent downloads/uploads. regardless of what i'm entering, all downloads run at once. i'm using

throttle.max_downloads.global.set = 5
throttle.max_uploads.global.set   = 5


how can i resolve this? is this the correct setting?

 

thx a lot!

Link to comment
6 hours ago, Johnster said:

Is there some tweak so that rutorrent doesn't reset the upload/download stats every time i restart/stop/update the client?

 

rtorrent.PNG

 

I believe this info is presented by rtorrent, and rutorrent displays it.  Most clients often reset this when the app is restarted. 

 

However, by default, the "Trafic" plugin is installed, and you should see a tab that says "Traffic" on the lower portion of the screen. This keeps a running tally of data use by tracker and you can filter it as you please.

Link to comment

I switched from qbittorrentvpn to rtorrentvpn because I had some strange problems where in qbittorrent all torrents would stop downloading for several minutes and after a while everything was fine for about 1min then all downloads would freeze again. That problem repeated forever.

rtorrentvpn have worked perfect since I switched for about 6 months ago. Now I get the same problems suddenly with rtorrentvpn, has something changed ?

Edited by Cliff
Link to comment

Is the docker just having issues lately or is it because I've grown to about 1000 torrents in the past few months? I have it pinned to 2 cores, 4 threads, on an E3-1230 v3 (3.3GHz processor). I know that's a really general question, but I just have no clue if my server is the bottleneck or the container is just having performance issues. I'm finding it times out often, crashes often, very slow UI updates, and can't seem to handle more than 5-7 active downloads now without crashing.

 

If it helps, I'm using AirVPN which doesn't seem to have any reports of issues as far as I've seen.

Edited by s449
Additional info
Link to comment
17 hours ago, Cliff said:

I switched from qbittorrentvpn to rtorrentvpn because I had some strange problems where in qbittorrent all torrents would stop downloading for several minutes and after a while everything was fine for about 1min then all downloads would freeze again. That problem repeated forever.

rtorrentvpn have worked perfect since I switched for about 6 months ago. Now I get the same problems suddenly with rtorrentvpn, has something changed ?

 

3 hours ago, s449 said:

Is the docker just having issues lately or is it because I've grown to about 1000 torrents in the past few months? I have it pinned to 2 cores, 4 threads, on an E3-1230 v3 (3.3GHz processor). I know that's a really general question, but I just have no clue if my server is the bottleneck or the container is just having performance issues. I'm finding it times out often, crashes often, very slow UI updates, and can't seem to handle more than 5-7 active downloads now without crashing.

 

If it helps, I'm using AirVPN which doesn't seem to have any reports of issues as far as I've seen.

I was having issues with my seedbox over a year ago (closer to 2 probably), and the tldr of the quoted support response from provider is too many active is a problem (currently tend to have around 75 active with no prob on there). Issue on seedbox was move when completed not always working, torrents going into pausing state, and rtorrent crashing.

 

Over the past couple months i remembered the seedbox issue and applied that to binhexrtorrentvpn (was having issues similar to cliff), and container has been working pretty well since. Getting uploads and downloads, but run into issues if there are more than 100 to 150 non-stopped torrents, or if active count is over like 30. I'm running dual e5-2695v2 (2*12 cores, hyperthreaded, 2.4ghz), 128gb ram, with nothing pinned, pia vpn. My plan has been to make a manager to coordinate between multiple containers like a "rtorrent container swarm" thing (multiple containers networked thru 1 running vpn & manager)...but have not gotten around to it yet as it feels like an overengineered solution.

 

Maybe others can weigh in as to how many non-stopped and active torrents they have...or other knowledge of what our problems might be.

 

Quote

I believe it's possible that both of these issues were being caused by the amount of torrents that you had in active downloading states. For whatever reason this seems to strain rtorrent a lot past a certain point, it may be too aggressive in trying to find peers on so many torrents that it impacts performance of other aspects. You should find right now that most of your torrents have been put into stopped states--this was necessary to troubleshoot because the client could hardly load at all--and in doing so the client is significantly more responsive. I expect that you won't have any issues with torrents being moved or randomly pausing as long as your active downloads remains at a lower number, for example in the single digits.

...

rtorrent is regrettably the best client for handling large amounts of torrents overall. The other clients we offer, Deluge and Transmission, have better queuing systems that allow for specifying a maximum number of torrents to be active simultaneously (downloading, uploading, and overall), but these clients cannot handle as many torrents overall as rtorrent and I would generally recommend keeping them at 2000 or fewer, with the higher you go, the worse performance will become. You could run multiple clients at once if you wished, to help spread out the load between them.

 

Link to comment
3 hours ago, DontWorryScro said:

Any one able to point me in the right direction for how to install File Manager?

For the old version of the container with rtorrent-ps + old version of file-manager (before it was split on its own repo) see: https://github.com/binhex/arch-rtorrentvpn/issues/96

 

For the latest version of the container + newest version of file manager I can't get it to work at all. Had to revert back. Please do let me know if you figure out.

  • Thanks 1
Link to comment
15 hours ago, Cat_Seeder said:

For the latest version of the container + newest version of file manager I can't get it to work at all. Had to revert back. Please do let me know if you figure out.

fyi and everybody else, i have rolled back to rtorrent-ps (as previously mentioned) and have also kludged a build of pyrocore back into the image as it was, so tagged 'latest' should now be identical to how it was before the upgrade to rtorrent 0.9.8.

 

i have also identified the issue with http (missing iptables rules) so this should also be working for 'latest'.

  • Thanks 2
Link to comment

Recently installed the container.

 

I was having a start-up issue where the container wouldn't launch because it was hung up on not having passwords for the webui and the contrainer itself "RPC2_USER not defined (via -e RPC2_USER), defaulting to 'admin' /usr/local/bin/init.sh: line 346: /config/nginx/security/rpc2_pass: No such file or directory"

 

After reading through someone else's post, they fixed this by defining a user/pass for the webui and the RPC2 and this worked for me too.

 

However, when I try to log into the webui using https://IP:9443, it gives me a certificate error.

 

I can essentially tell my browser "Yes, it's fine. I promise." and I can log in, but I'd like to get this issue fixed if possible.

 

Any help would be appreciated!

Link to comment
2 minutes ago, godzillafanclub said:

I was having a start-up issue where the container wouldn't launch because it was hung up on not having passwords for the webui and the contrainer itself "RPC2_USER not defined (via -e RPC2_USER), defaulting to 'admin' /usr/local/bin/init.sh: line 346: /config/nginx/security/rpc2_pass: No such file or directory"

i will take a look at this, thanks.

 

3 minutes ago, godzillafanclub said:

However, when I try to log into the webui using https://IP:9443, it gives me a certificate error.

 

I can essentially tell my browser "Yes, it's fine. I promise." and I can log in, but I'd like to get this issue fixed if possible.

the certificate included is a self signed cert, thus you get the warning, if you dont want the warning then you will need to purchase a certificate from a trusted internet CA, or generate one from letsencrypt website.

Link to comment
2 hours ago, binhex said:

fyi and everybody else, i have rolled back to rtorrent-ps (as previously mentioned) and have also kludged a build of pyrocore back into the image as it was, so tagged 'latest' should now be identical to how it was before the upgrade to rtorrent 0.9.8.

 

i have also identified the issue with http (missing iptables rules) so this should also be working for 'latest'.

And everything is working again. Thanks Binex, you are awesome.

I know that eventually we'll need to jump off rtorrent-ps (unless a miracle happens and it pick up the pace again). Hopefully there's a way to do it without having to force users to expose RPC2 mounts and someone will find a way to make file manager before that.

 

For now, I'm glad to be on good ol' versions :).

Link to comment
11 hours ago, Cat_Seeder said:

And everything is working again. Thanks Binex, you are awesome.

I know that eventually we'll need to jump off rtorrent-ps (unless a miracle happens and it pick up the pace again). Hopefully there's a way to do it without having to force users to expose RPC2 mounts and someone will find a way to make file manager before that.

 

For now, I'm glad to be on good ol' versions :).

tbh im not overly happy to be on either version as of right now, 0.9.6 has tracker overload issues (https://github.com/pyroscope/rtorrent-ps/issues/132) and DDOS vulnerabilities (apparently) and 0.9.8 has a major flaw which is triggered by offline trackers (https://github.com/rakshasa/rtorrent/issues/999), bit of a rock and a hard place situation.

 

for now i will monitor the issues and if things change then review the situation.

 

p,s. having said all of the above, rtorrent/rutorrent is STILL my torrent client of choice for me, its fast and has most features you want from a torrent client so im not abandoning it...yet :-).

  • Like 3
Link to comment

i've notived that rutorrent gets tuck with 100% cpu usage, sometimes in a way that it affects other dockers. is there anything i can do to figure out whats going on? "htop" only shows me that it does that, but i don't see why. i only have about 20 torrents open, most of them idling. appreciate any help!

Link to comment
On 2/15/2021 at 11:02 AM, s449 said:

Is the docker just having issues lately or is it because I've grown to about 1000 torrents in the past few months? I have it pinned to 2 cores, 4 threads, on an E3-1230 v3 (3.3GHz processor). I know that's a really general question, but I just have no clue if my server is the bottleneck or the container is just having performance issues. I'm finding it times out often, crashes often, very slow UI updates, and can't seem to handle more than 5-7 active downloads now without crashing.

 

If it helps, I'm using AirVPN which doesn't seem to have any reports of issues as far as I've seen.

So I got my client down to about 800 torrents and it seemed to improve. However, I added 3 torrents that were 100GB and another that was 50GB. I've had some pretty big torrents before but I'm not sure ever this big, plus trying to download it all at once. Extremely slow UI and it kept crashing and because of that kept trying to re-check everything and crashing again. I even had my Unraid shares crash to where I had to reboot my server to see them again, even once had to fix a drive's file system. Not sure if it's related, I'm on Unraid 6.9.0-RC2. Anyway, when the UI would load it just wouldn't download/upload anything. I had zero peers across the board. After the stability being on-and-off it ended up getting stuck in a loop of rTorrent just crashing at start. It wouldn't start at all and just stopped working 99% of the time. I checked the rtorrent session folder and there was almost 2000 files created in the past day. I think it was stuck in a loop trying to fix itself or something.

 

After loads of debugging all week I ended up just going with a fresh install and configuration of the docker and so far it seems to be stable and working just fine. It's a pain to have to re-add all my torrents, still working on that, and that I lost all my stats. I'm just dying for this docker to feel stable again. I feel like I've spent 1000 hours debugging it the past few months.

 

So my question is once again...does it sound like I just hit some sort of performance bottleneck? Can the docker just not handle large size or large amounts of torrents? I just want to know if this sounds even remotely like a simple performance issue so I can conclude my endless debugging as: keep the torrent list low, don't flood the docker with big downloads all at once, and download beefier torrents on another desktop PC.

 

It seems similar to the issue this user had, at one point I had the same exact error (which is how I found this post):

  

On 10/29/2020 at 9:26 PM, plantsandbinary said:

My entire rTorrent has stopped working for some reason whilst downloading a large 1.6TB torrent.

 

My first drive filled up and most of my docker images crash when that happens. So I turned off all containers and moved files to the next drive.

Figured there would be no problems so I restarted the container.

 

Now I get this in the log.

 



2020-10-30 06:23:05,894 DEBG 'rutorrent-script' stderr output:
[NOTICE] [pool www] 'user' directive is ignored when FPM is not running as root
[NOTICE] [pool www] 'group' directive is ignored when FPM is not running as root

2020-10-30 06:23:05,903 DEBG 'rutorrent-script' stdout output:
[info] starting nginx...

2020-10-30 06:23:16,542 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries

2020-10-30 06:23:16,543 DEBG 'watchdog-script' stdout output:
[warn] Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...

2020-10-30 06:33:23,916 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.14.0.3 different, marking for reconfigure

2020-10-30 06:33:24,772 DEBG 'watchdog-script' stdout output:
0

2020-10-30 06:33:25,099 DEBG 'watchdog-script' stderr output:
INFO: Bad data packets written to '/tmp/xmlrpc2scgi-99.xml'

2020-10-30 06:33:25,100 DEBG 'watchdog-script' stdout output:
ERROR While calling network.local_address.set('', '216.239.32.10\n216.239.34.10\n216.239.36.10\n216.239.38.10'): <Fault -503: 'Could not set local address: Name or service not known.'>

I've even rebooted my server. It was running for 415 days without issues and I must have updated this container maybe 3 or 4 times during that time because I like to update only after a good period of time.

 

Any advice is appreciated. Thank you!!

Edited by s449
Link to comment
1 hour ago, s449 said:

So my question is once again...does it sound like I just hit some sort of performance bottleneck? Can the docker just not handle large size or large amounts of torrents?

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).

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