[Support] binhex - rTorrentVPN


Recommended Posts

Hello,

I am new in the use of this container and new in the use of docker.

Recently I set up this very good container but unfortunately I have low download speeds. (2.7MB / s for a 1Gbs connection)

The VPN that I own (Ivacy) gives me very good results on a debian VM (between 15MB / s and 25MB / s) The VPN is therefore not in question.

On the container settings I tried to change the NAME_SERVER by several other servers but without success (either the container does not start, or I get the same low speed)

I no longer know where to look.

Can you help me ?

Thank you

 

---------------------------

 

Bonjour,

 

Je suis nouveau dans l'utilisation de ce container et nouveau dans l'utilisation de docker.

Récemment j'ai mis en place ce très bon container mais malheureusement j'ai des débits faible en download. (2.7Mo/s pour une connexion de 1Gbs)

Le VPN que je possède (Ivacy) me donne de très bon résultat sur un VM débian (entre 15Mo/s et 25Mo/s) Le VPN n'est donc pas en cause.

Sur les paramètres du container j'ai essayé de changer le NAME_SERVER par plusieurs autres serveurs mais sans succès (soit le container ne démarre pas, soit j'obtiens les mêmes débit faible)

Je ne sais plus où chercher.

 

Pouvez-vous m'aider ?

 

Merci

Link to comment

Hi, I am new to Docker.  I set up binhex/arch-rtorrentvpn successfully, but for some reason when I try to change the port number for torrents, it stays stuck at default 6118 (which for some reason is banned by my tracker) even though the port I selected is listed in ruTorrent settings. Then when I restart the container, the port listed in ruTorrent settings also goes back to default. Is this a bug or am I doing something wrong? Thanks!

Link to comment
15 hours ago, kirk8999 said:

Hi, I am new to Docker.  I set up binhex/arch-rtorrentvpn successfully, but for some reason when I try to change the port number for torrents, it stays stuck at default 6118 (which for some reason is banned by my tracker) even though the port I selected is listed in ruTorrent settings. Then when I restart the container, the port listed in ruTorrent settings also goes back to default. Is this a bug or am I doing something wrong? Thanks!

You gotta change the config file the config folder /rtorrent/config/rtorrent.rc file. 

 

E.G.:

network.port_range.set = 6801-6801

Link to comment
On 5/14/2020 at 6:22 PM, Einsteinjr said:

Is there anyone else facing an issue where the port status is unknown?  I haven't changed anything and all-of-a-sudden it has gone back to that.

 

No VPN and I've confirmed port-forwarding is working.

 

Thanks in advance.

Note: latest container update fixed the issue.

Link to comment

another update and nothing works again..sigh

 

ErrorWarningSystemArrayLogin


Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2020-06-27 03:01:44.543185 [info] System information Linux df6e6c2269c7 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-06-27 03:01:44.584283 [info] OS_ARCH defined as 'x86-64'
2020-06-27 03:01:44.624394 [info] PUID defined as '99'
2020-06-27 03:01:44.787879 [info] PGID defined as '100'
2020-06-27 03:01:45.075328 [info] UMASK defined as '000'
2020-06-27 03:01:45.116211 [info] Permissions already set for volume mappings
2020-06-27 03:01:45.162833 [info] VPN_ENABLED defined as 'no'
2020-06-27 03:01:45.198937 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2020-06-27 03:01:45.242800 [info] ENABLE_AUTODL_IRSSI defined as 'no'
2020-06-27 03:01:45.286138 [info] ENABLE_RPC2 defined as 'yes'
2020-06-27 03:01:45.333826 [info] ENABLE_RPC2_AUTH defined as 'yes'
2020-06-27 03:01:45.372745 [info] RPC2_USER defined as 'admin'
2020-06-27 03:01:45.411866 [info] RPC2_PASS defined as 'xxxxxxx'
2020-06-27 03:01:45.451898 [info] ENABLE_WEBUI_AUTH defined as 'yes'
2020-06-27 03:01:45.491010 [info] WEBUI_USER defined as 'admin'
2020-06-27 03:01:45.529958 [info] WEBUI_PASS defined as 'xxxxxx'
2020-06-27 03:01:45.629492 [info] Deleting files in /tmp (non recursive)...
2020-06-27 03:01:45.667056 [info] Starting Supervisor...
2020-06-27 03:01:45,956 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2020-06-27 03:01:45,956 INFO Set uid to user 0 succeeded
2020-06-27 03:01:45,960 INFO supervisord started with pid 6
2020-06-27 03:01:46,962 INFO spawned: 'logrotate-script' with pid 112
2020-06-27 03:01:46,964 INFO spawned: 'pyrocore-script' with pid 113
2020-06-27 03:01:46,966 INFO spawned: 'rutorrent-script' with pid 114
2020-06-27 03:01:46,968 INFO spawned: 'start-script' with pid 115
2020-06-27 03:01:46,971 INFO spawned: 'watchdog-script' with pid 116
2020-06-27 03:01:46,971 INFO reaped unknown pid 7 (exit status 0)
2020-06-27 03:01:46,984 DEBG 'watchdog-script' stdout output:
[info] rTorrent config file already exists, skipping copy

2020-06-27 03:01:46,984 INFO success: logrotate-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-06-27 03:01:46,984 INFO success: pyrocore-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-06-27 03:01:46,984 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-06-27 03:01:46,984 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-06-27 03:01:46,984 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-06-27 03:01:46,994 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2020-06-27 03:01:46,994 DEBG fd 25 closed, stopped monitoring <POutputDispatcher at 140005636756864 for <Subprocess at 140005636697872 with name start-script in state RUNNING> (stderr)>
2020-06-27 03:01:46,995 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 140005636697920 for <Subprocess at 140005636697872 with name start-script in state RUNNING> (stdout)>
2020-06-27 03:01:47,033 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2020-06-27 03:01:47,033 INFO exited: start-script (exit status 0; expected)
2020-06-27 03:01:47,033 DEBG received SIGCHLD indicating a child quit
2020-06-27 03:01:47,033 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2020-06-27 03:01:47,034 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2020-06-27 03:01:47,036 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2020-06-27 03:01:47,065 DEBG 'watchdog-script' stdout output:
Script done.

2020-06-27 03:01:47,338 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 140005636655376 for <Subprocess at 140005636654704 with name pyrocore-script in state RUNNING> (stdout)>
2020-06-27 03:01:47,338 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 140005636756144 for <Subprocess at 140005636654704 with name pyrocore-script in state RUNNING> (stderr)>
2020-06-27 03:01:47,338 INFO exited: pyrocore-script (exit status 0; expected)
2020-06-27 03:01:47,338 DEBG received SIGCHLD indicating a child quit
2020-06-27 03:02:16,388 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries

2020-06-27 03:02:16,389 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

Edited by Spazhead
Link to comment

Just updated and now getting this...

 

[28.06.2020 12:46:56] JS error: [http://192.168.1.50:9080/js/jquery.js line 2 > eval : 5360] TypeError: this.actLbls is undefined

 

Literally all 600-something of my torrents have disappeared too and I can't click on anything on the UI without getting this error.

 

EDIT: Going to settings still works. > General > Change theme to standard. Now I can see my torrents again.

EDIT2: Back to Oblivion Theme, now it works.

EDIT3: Rebooted docker container, same error, and same above fix worked. So it's an error thrown at runtime.

 

 

fuck.png

Edited by plantsandbinary
Link to comment
15 hours ago, koth said:

These torrents are not able to actually upload, and any downloads I add will find peers but cannot download.

have you set the incomplete and completed download locations correctly so that they reference /data (assuming you kept with the default name).

Link to comment
22 hours ago, plantsandbinary said:

Just updated and now getting this...

 


[28.06.2020 12:46:56] JS error: [http://192.168.1.50:9080/js/jquery.js line 2 > eval : 5360] TypeError: this.actLbls is undefined

 

Literally all 600-something of my torrents have disappeared too and I can't click on anything on the UI without getting this error.

 

EDIT: Going to settings still works. > General > Change theme to standard. Now I can see my torrents again.

EDIT2: Back to Oblivion Theme, now it works.

EDIT3: Rebooted docker container, same error, and same above fix worked. So it's an error thrown at runtime.

 

 

fuck.png

possibly related?:-

https://github.com/Novik/ruTorrent/issues/1920

 

also do a complete wipe of your browser cache, try another browser too, i suspect it is going to be a script blocker or caching issue with your browser, i am not seeing this error at all and im running latest.

Link to comment
17 hours ago, koth said:

Forgot to add, I did also set the port_range in rtorrent.rc to 57717-57717. It's forwarded through my provider and works with the same .ovpn with qbittorrent.

is the incoming port indicator in rutorrent shown as green (bottom of the rutorrent web ui)?, it should look like this if the incoming port is visible externally:-

image.png.775de5638c084c7f6042e862ed673216.png

 

if its not green then the port assignment from your vpn provider is not working or you have misconfigured rutorrent/rtorrent.

Link to comment
14 minutes ago, koth said:

Yes, I rechecked the port as well and it was still good, correct ip/port is reported to trackers

ok in that case i would suspect your vpn provider is blocking torrent traffic, you could try another vpn endpoint, perhaps they permit torrent traffic on certain endpoints only, who is your vpn provider?.

Link to comment

Is the auto port assign of PIA working correctly?

 

I see the messages in the logs about retrieving and assigning the port from PIA:

 

[info] Successfully assigned incoming port 55730
[info] Checking we can resolve name 'www.google.com' to address...
[info] DNS operational, we can resolve name 'www.google.com' to address [REDACTED]
[info] Attempting to get external IP using Name Server 'ns1.google.com'...
[info] Successfully retrieved external IP address [REDACTED]
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP [REDACTED]different, marking for reconfigure
[info] rTorrent not running
[info] rTorrent incoming port 49160 and VPN incoming port 55730 different, marking for reconfigure

However, the port reported in the interface bottom bar is a different one (the one I had previosuly configured) and it shows the red icon saying the port is not open.

Link to comment
1 hour ago, Jeffarese said:

Is the auto port assign of PIA working correctly?

yes, leave the container running and it will sort it all out for you, i just had my port close (vpn provider issue) and my scripts kicked in to reconfigure for a new incoming port automagically.

Link to comment
13 minutes ago, binhex said:

yes, leave the container running and it will sort it all out for you, i just had my port close (vpn provider issue) and my scripts kicked in to reconfigure for a new incoming port automagically.

Correct! it sorted it out after a while and now it shows green!

 

Unrelated question about PIA:

Is there any problem if I have multiple instances of your script using different server configs (one container has sweden.ovpn, another one has france.ovpn) so each one of the containers requests a different port?
I run multiple containers of your image to organize better my files.
It seems to be working OK and all of them show the green icon now and seem to be seeding ok.

Link to comment
1 minute ago, Jeffarese said:

Is there any problem if I have multiple instances of your script using different server configs (one container has sweden.ovpn, another one has france.ovpn) so each one of the containers requests a different port?

im assuming bad use of the word 'script' here, you mean multiple containers with different endpoints?, if so then yep you can do that no problem, just make sure no host ports conflict.

Link to comment

lol sorry, my mind was in another place. Yeah, I meant of your image :P
Each one of the containers are using different PIA servers (endpoints) so each one of them receive a different IP & request a different port, even though all the containers are running in the same server.

 

How would I have host port conflicts? I don't need to forward host ports since the ports are open by the VPN, right?

Link to comment
2 minutes ago, Jeffarese said:

Each one of the containers are using different PIA servers (endpoints) so each one of them receive a different IP & request a different port, even though all the containers are running in the same server.

correct

 

3 minutes ago, Jeffarese said:

How would I have host port conflicts? I don't need to forward host ports since the ports are open by the VPN, right?

correct, you dont need to forward ports but you do still need a port to connect to rutorrent web ui, and this will have to be unique for each container, change only the host side NOT the container port.

Link to comment
10 minutes ago, binhex said:

correct, you dont need to forward ports but you do still need a port to connect to rutorrent web ui, and this will have to be unique for each container, change only the host side NOT the container port.

Ah yes! I already had this setup in the past, I have that sorted out :) Thanks!

Link to comment
20 hours ago, binhex said:

is the incoming port indicator in rutorrent shown as green (bottom of the rutorrent web ui)?, it should look like this if the incoming port is visible externally:-

image.png.775de5638c084c7f6042e862ed673216.png

 

if its not green then the port assignment from your vpn provider is not working or you have misconfigured rutorrent/rtorrent.

but you just said to me earlier this plugin/indicator has been broken for years. The best way to check if you are connectable is to use a tracker that can test for you or some kind of torrent-vpn checker that can test if your port is open or not, at least that's what I use to confirm it.

 

EDIT: Here's what I mean. ruTorrent shows closed, but the tracker says I am connectable and my port is open.

 

I haven't trusted that ruTorrent plugin for years.

open.png

 

closed.png

Edited by plantsandbinary
Link to comment
40 minutes ago, plantsandbinary said:

but you just said to me earlier this plugin/indicator has been broken for years.

nope, you said that and i corrected you:- 

https://forums.unraid.net/topic/46127-support-binhex-rtorrentvpn/?do=findComment&comment=865127

 

if the indicator at the bottom of the screen is red then you do not have a working incoming port, that plugin IS reliable, at least it is now that it got fixed (was broken for around 2 months).

 

grab your external ip address from settings/bittorrent/ip-host to report to tracker, grab your incoming port from settings/connection/port used for incoming connections and head over to this website:- https://www.yougetsignal.com/tools/open-ports/

 

paste in the ip and port and click on 'check', i think you will find your port is not open.

Link to comment
16 hours ago, binhex said:

nope, you said that and i corrected you:- 

https://forums.unraid.net/topic/46127-support-binhex-rtorrentvpn/?do=findComment&comment=865127

 

if the indicator at the bottom of the screen is red then you do not have a working incoming port, that plugin IS reliable, at least it is now that it got fixed (was broken for around 2 months).

 

grab your external ip address from settings/bittorrent/ip-host to report to tracker, grab your incoming port from settings/connection/port used for incoming connections and head over to this website:- https://www.yougetsignal.com/tools/open-ports/

 

paste in the ip and port and click on 'check', i think you will find your port is not open.

I'm tellin' ya. That thing does not work. 3 sites all tell me it's open. I have never, ever seen a green tick on that thing. Plus I am able to download and upload at line speed. Might want to check it again, but I don't think it's worth the hassle.

 

dfdf.png

Edited by plantsandbinary
Link to comment
7 hours ago, plantsandbinary said:

I'm tellin' ya. That thing does not work. 3 sites all tell me it's open. I have never, ever seen a green tick on that thing. Plus I am able to download and upload at line speed. Might want to check it again, but I don't think it's worth the hassle.

and i'm tellin' ya its always worked for me :-), i have a green icon right now, when it goes red then i check and sure enough the port is closed, my scripts then kick in and reconfigure the port and it goes back to green, dunno what to say dude but for the vast majority of people this just works *shrug*.

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