[Support] binhex - rTorrentVPN


2655 posts in this topic Last Reply

Recommended Posts

2 minutes ago, binhex said:

have you got any of the following:-

1. vlans - if so check config

2. pfsense or other firewall - check its not blocking network connectivity

3. ad blocker - disable on browser

 

things to try:-

1. try another browser

2. try another host to connect to the web ui

 

of note this image does not work with macvlan network configuration, if its set to this then please set back to 'bridge'.

No VLANS.

 

I do have pfsense.  It works and shows the port as correctly forwarded without the VPN.  Could this still be an issues?

 

I'll double check on the adblocker but it should be off on unraid pages.

 

The macvlan thing, is that what I set it to to have a reverse proxy?  I use nginxproxymanager for this.  I also have a wireguard connection for remote access.  I wondered if that might not be causing issues. 

 

It was all working a while back with all of these things being the same, so I'm just not sure what changed.

 

 

Link to post
  • Replies 2.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

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

@binhex   Would it be possible to have the script run through a list of .ovpn files after failing to port forward with one? Use case would be, CA-Montreal is having port-forward API issues r

Posted Images

Well, of all the damnedest things in the world, it decided to just start working.  Only issue I'm having now is that the UDP trackers error out.  That may be a AirVPN issue, as I don't see an option to tell it to let me use both UDP and TCP ports.  Looks like you have to pick one or the other. But what's strange is that the OVPN file I used is a UDP port.  And the port I have forwarded, which shows as open on their website, is both TCP and UDP.  But hey, at least we're working now!

 

https://pastebin.com/Kp0dgAQG

 

Now if I can just figure out the ratiocolor plugin.

 

https://github.com/Gyran/rutorrent-ratiocolor

Edited by EC28
Link to post
19 hours ago, EC28 said:

Well, of all the damnedest things in the world, it decided to just start working.  Only issue I'm having now is that the UDP trackers error out.  That may be a AirVPN issue, as I don't see an option to tell it to let me use both UDP and TCP ports.  Looks like you have to pick one or the other. But what's strange is that the OVPN file I used is a UDP port.  And the port I have forwarded, which shows as open on their website, is both TCP and UDP.  But hey, at least we're working now!

 

https://pastebin.com/Kp0dgAQG

 

Now if I can just figure out the ratiocolor plugin.

 

https://github.com/Gyran/rutorrent-ratiocolor

I'm having the same issue as you and I am also on AirVPN.

I even tried rolling back a few versions of the docker image, but the same issues persists. I assume it must be AirVPN related.

Generating new OVPN files from AirVPN (trying UDP and TCP) didn't solve the issue either.

I will keep restarting in the hopes that my set up will magically start working too I guess!

Link to post

I'm not sure if it's airvpn related or not.  I ended up starting from scratch again last night, as the ratiocolor plugin messes the whole docker up.

 

All I did was use the udp server from airvpn.  I turned off autodl and turned on privoxy and the VPN.  I put my login information for airvpn's website in the vpn fields.  It is working for whatever reason.

Link to post
17 minutes ago, EC28 said:

I put my login information for airvpn's website in the vpn fields. 

not required and will do nothing, airvpn uses embedded credentials in the ovpn file.

Link to post
20 hours ago, EC28 said:

Only issue I'm having now is that the UDP trackers error out.  That may be a AirVPN issue, as I don't see an option to tell it to let me use both UDP and TCP ports. 

not related to tracker issues, airvpn udp or tcp is only the initial connection to the server, once the vpn tunnel is established then all protocols should be permitted. most likely the issue is related to the tracker banning vpn provider known ip ranges (due to abuse).

Edited by binhex
Link to post
25 minutes ago, sephallen said:

I'm having the same issue as you and I am also on AirVPN.

I even tried rolling back a few versions of the docker image, but the same issues persists. I assume it must be AirVPN related.

Generating new OVPN files from AirVPN (trying UDP and TCP) didn't solve the issue either.

I will keep restarting in the hopes that my set up will magically start working too I guess!

EC28's issue was not related to airvpn, i could see a tunnel was established but he was unable to access the web ui, im not sure of the reason why this has now been resolved for him but i doubt its vpn provider related.

 

please do the following:-

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Edited by binhex
Link to post
3 minutes ago, binhex said:

EC28's issue was not related to airvpn, i could see a tunnel was established but he was unable to access the web ui, im not sure of the reason why this has now been resolved for him but i doubt its vpn provider related.

 

please do the following:-

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

When EC28 mentioned they had started from scratch, it reminded me that I had done the same over the weekend in order to try to fix the timeouts I often get (particularly when downloading larger files), but alas it didn't fix the issue.

 

However, I also changed a setting in my rtorrent.rc and hadn't restarted yet - turns out the value was invalid and that's what the issue was. I have now corrected it and everything is working fine again.

 

So AirVPN is a red herring - thanks for the help and sorry for wasting your time!

Link to post

After the latest update, it doesn't seem to be working right.

[29.05.2020 06:05:16] No connection to rTorrent. Check if it is really running. Check $scgi_port and $scgi_host settings in config.php and scgi_port in rTorrent configuration file.

Is what the webui displays

 

And the logs for the container shows that it keeps looping over and over

 


2020-05-29 06:03:58,332 DEBG 'rutorrent-script' stderr output:
2020/05/29 06:03:58 [error] 770#770: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.50.130, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.50.130:9080"

2020-05-29 06:04:08,539 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2020-05-29 06:04:08,540 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2020-05-29 06:04:08,544 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2020-05-29 06:04:08,546 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2020-05-29 06:04:08,575 DEBG 'watchdog-script' stdout output:
Script done.

2020-05-29 06:04:12,642 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2020-05-29 06:04:12,653 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening on port 5000

2020-05-29 06:04:12,653 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2020-05-29 06:04:12,663 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

2020-05-29 06:04:12,674 DEBG 'watchdog-script' stdout output:
[info] nginx running
[info] Initialising ruTorrent plugins...

2020-05-29 06:04:13,258 DEBG 'watchdog-script' stdout output:


2020-05-29 06:04:13,878 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

2020-05-29 06:04:43,907 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2020-05-29 06:04:43,907 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2020-05-29 06:04:43,911 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2020-05-29 06:04:43,912 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2020-05-29 06:04:43,942 DEBG 'watchdog-script' stdout output:
Script done.

2020-05-29 06:04:48,004 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2020-05-29 06:04:48,015 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening on port 5000

2020-05-29 06:04:48,015 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2020-05-29 06:04:48,025 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

2020-05-29 06:04:48,038 DEBG 'watchdog-script' stdout output:
[info] nginx running
[info] Initialising ruTorrent plugins...

2020-05-29 06:04:48,555 DEBG 'watchdog-script' stdout output:


2020-05-29 06:04:49,184 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

2020-05-29 06:04:58,330 DEBG 'rutorrent-script' stderr output:
2020/05/29 06:04:58 [error] 770#770: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.50.130, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.50.130:9080"

 

Link to post

I'm using binghex-DelugeVPN with no issue and I'm also trying to use this docker. I changed the ports not to cause a conflict. The container  starts up fine but I'm unable to access the web GUI. I get an Unable to connect error and the logs keep showing this message:

 

Quote

/usr/local/bin/init.sh: line 346: /config/nginx/security/rpc2_pass: No such file or directory

 

I'm also unable to access the container console. I see an error flash right away but i can't see what's saying

 

Can both containers be used at the same time?

Link to post
5 hours ago, bugster said:

I'm using binghex-DelugeVPN with no issue and I'm also trying to use this docker. I changed the ports not to cause a conflict. The container  starts up fine but I'm unable to access the web GUI. I get an Unable to connect error and the logs keep showing this message:

 

 

I'm also unable to access the container console. I see an error flash right away but i can't see what's saying

 

Can both containers be used at the same time?

yes you can use both at the same time

your situation may be what is addressed in the third post of this thread??

(sorry it wont let me post the info and link)

Link to post
On 5/29/2020 at 12:08 PM, wirenut said:

yes you can use both at the same time

your situation may be what is addressed in the third post of this thread??

(sorry it wont let me post the info and link)

You mean this?

Quote

As from 15th of January 2020, if the web ui and/or rpc2 password have not been defined (defined via environment variables) then the password(s) will be randomised and no longer set to 'rutorrent'.

That's not my problem I can't get to the gui at all

Link to post
On 11/12/2016 at 2:41 PM, binhex said:

 

If you want to modify things like incoming port, enabling/disabling dht, and folders for incomplete/complete downloads then you will have to modify the rtorrent config file, this is located in /config/rtorrent/config/rtorrent.rc please make sure you use something like notepad++ (not notepad) to prevent windows line endings getting added.

Hi, I can't use port 6881 so looking to change the port. I went to rtorrent.rc in the config folder but don't see anywhere to change the incoming port connections (to 7881-7999). How can I change it? Do I need to change anything in the container page (and if so, what do I need to change/add)? Thank you!

Link to post
1 hour ago, puncho said:

Hi, I can't use port 6881 so looking to change the port. I went to rtorrent.rc in the config folder but don't see anywhere to change the incoming port connections (to 7881-7999). How can I change it? Do I need to change anything in the container page (and if so, what do I need to change/add)? Thank you!

You are looking for network.port_range.set, for further information check rtorrent guide at https://rtorrent-docs.readthedocs.io/en/latest/cookbook.html

 

The container README.md also has a sample configuration for AirVPN demonstrating how to change incoming ports: https://github.com/binhex/arch-rtorrentvpn/blob/master/README.md

Link to post
On 5/28/2020 at 8:53 AM, binhex said:

not related to tracker issues, airvpn udp or tcp is only the initial connection to the server, once the vpn tunnel is established then all protocols should be permitted. most likely the issue is related to the tracker banning vpn provider known ip ranges (due to abuse).

Ah, good to know. Thanks again!

Link to post

For some reason my container crashed whilst I was asleep. Wasn't doing anything out of the ordinary, tons of RAM and HDD space left too.

 

I woke up with a 403 error.

 

Log: cryptobin.co/8856i3f9

Password: 6BNny/lSO+lQhS7Obe583ugivfpv44Ylq8KtjCsXrIYlFWfRL3cXOh0rYrU393Em

 

Also does anyone have any information on how to solve this weird thing that started happening out of nowhere about a week ago?

 

Right click brings up the Firefox context menu in front of the menu for rTorrent.

 

y6Kl6Xz.png

Edited by plantsandbinary
Link to post
2 hours ago, plantsandbinary said:

I woke up with a 403 error.

 

Log: cryptobin.co/8856i3f9

nothing out of the ordinary in that log tbh, i noted the stat plugin issue but that is a know problem with php and isnt related to the crash. im assuming the crash must of been a soft crash, as this image will recover from a hard crash of rtorrent/rutorrent, not really much that can be gleaned from the log im afraid.

Link to post

I had 800+ GB download mysteriously reported to a tracker, even though I only seed from this box. Is there anything you can help me with in diagnosing this? I stopped the container and moved everything to qBittorrent to make sure it doesn't get worse, but it's practically unusable with the number I'm seeding.

Link to post
14 minutes ago, psycho_asylum said:

I had 800+ GB download mysteriously reported to a tracker, even though I only seed from this box. Is there anything you can help me with in diagnosing this? I stopped the container and moved everything to qBittorrent to make sure it doesn't get worse, but it's practically unusable with the number I'm seeding.

Have a look at nginx logs for suspicious activity, particularly requests to /RPC2 from unusual IP addresses. Make sure to secure both ruTorrent and RPC2 with strong passwords (or disable RPC2 entirely I'd you don't need it). Don't use the defaulr auto-generated passwords as they are logged in plain text. If you can, do not expose anything over the internet (you can use a VPN to access your box). If you need to expose rutorrent do the internet then make sure to use a hardened reverse proxy (nginx-proxy / traefick, etc), Https only, with a real certificate (e.g., Let's Encrypt) and a strict fail2Ban configuration.

 

Having said all that, keep in mind that there are vectors of attack other than your torrent client (e.g., if someone got access to your private tracker username / password somehow, or if one of the private tracker admins messed up / if your own machine was compromised, etc).

 

I know that this is generic advice, but I hope it helps.

Link to post
On 6/5/2020 at 10:31 AM, Cat_Seeder said:

I know that this is generic advice, but I hope it helps.

I appreciate it. 

 

I don't have the container accessible at all from outside. The only thing I had accessible was a Windows 10 VM, but I disabled that port months ago in favor of using a VPN to get into it. The only port I have open currently on my network is for Plex. 

 

I should also mention that this happened just a day after firing up this container.  I previously had everything in qBittorrent but it is really slow. 

 

edit: I checked my logs in UniFi and it reports less than 6GB of traffic over the internet last night to/from my Unraid box.

 

edit2: https://github.com/rakshasa/rtorrent/issues/561  It may have something to do with this. I'll work with the tracker admin.

 

edit3: the tracker admin stated that they do not have this issue as described.

 

edit4: We discovered that it was a derivative of the issue above in rtorrent. 

Edited by psycho_asylum
Link to post
On 5/16/2020 at 12:41 AM, Calpulz said:

Hi, posted a while ago about rtorrent pinning a random thread at 100% usage. GUI completly locks up. Still havent managed to sort this, seems to only do it when im downloading. Have a thread ripper 1920x. If anyone can help or point me in the right direction that would be great.

I have the exact same issue. rtorrent is more or less frozen whenever it downloads. 

Did you resolve it? (I have a thread ripper as well)

 

Edited by Fidreus
Link to post
19 hours ago, Fidreus said:

I have the exact same issue. rtorrent is more or less frozen whenever it downloads. 

Did you resolve it? (I have a thread ripper as well)

 

Maybe I actually found a workaround. I pinned some cores 4+4HT to the container and now it seems to behave much better.

Edited by Fidreus
Link to post
20 hours ago, Fidreus said:

I have the exact same issue. rtorrent is more or less frozen whenever it downloads. 

Did you resolve it? (I have a thread ripper as well)

 

 

1 hour ago, Fidreus said:

Maybe I actually found a workaround. I pinned some cores 4+4HT to the container and now it seems to behave much better.

No i still havent found a solution. I have kind of just put up with it. I will try what you suggested and assign some cores to the container.

 

UPDATE:

So far so good!! The best ive been able to get is about 10 or 15 minutes before GUI locks up or the container crashes and restarts. Done as you suggested and assigned 4+4HT to the container and i have had the GUI up for 40 minutes now with no crash, reset or freeze. No threads pinned at 100%. Amazing, thanks for figuring that out, i never thought of trying something so simple. Had this issue for months and been driving me crazy!! I wonder why having access to all cores causes this issue though? Seems like it might be something relating to threadrippers.

Edited by Calpulz
Add update
Link to post
2 hours ago, Calpulz said:

UPDATE:

So far so good!! The best ive been able to get is about 10 or 15 minutes before GUI locks up or the container crashes and restarts. Done as you suggested and assigned 4+4HT to the container and i have had the GUI up for 40 minutes now with no crash, reset or freeze. No threads pinned at 100%. Amazing, thanks for figuring that out, i never thought of trying something so simple. Had this issue for months and been driving me crazy!! I wonder why having access to all cores causes this issue though? Seems like it might be something relating to threadrippers.

I was thinking what make threadrippers special - many cores.

I actually think this is a multi-core issue, maybe it isn't that common to have 64 cores available to rtorrent? :D

Link to post
7 hours ago, Fidreus said:

I was thinking what make threadrippers special - many cores.

I actually think this is a multi-core issue, maybe it isn't that common to have 64 cores available to rtorrent? :D

I had a thought, maybe its due to the threadripper having multiple numa nodes. So restricting the cores for the container keeps it inside a single numa node instead of having access to all cores across multiple numa nodes?

 

I know some games dont like working across numa nodes (think gta is one of them). Might be completly wrong as i dont fully understand it.

 

Link to post

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.