[Support] binhex - rTorrentVPN


Recommended Posts

1 minute ago, learningunraid said:

1. How is the current update helps us? (Since, we are mostly layman who doesn't understand technical terms, I wish to know what benefit latest update brings in comparison to the previous stable version)?

multiple fixes and improvements - resources usage is improved for one example.

 

1 minute ago, learningunraid said:

2. VPN are going to work as good as the previous version?

yes

 

1 minute ago, learningunraid said:

3. This update is going to fix any bugs of rutorrent/rtorrent?

see 1.

  • Like 1
Link to comment
Just now, binhex said:

multiple fixes and improvements - resources usage is improved for one example.

 

yes

 

see 1.

Thanks for the reply again, I will try the solution as you have suggested and will report back here.

 

One more question: Are we ever going to have Discord Server for the Binhex Fan Club? And if there is any channel in other discord server where you provide support, please let me know.

 

Thanks.

Link to comment
7 minutes ago, learningunraid said:

Thanks for the reply again, I will try the solution as you have suggested and will report back here.

 

One more question: Are we ever going to have Discord Server for the Binhex Fan Club? And if there is any channel in other discord server where you provide support, please let me know.

 

Thanks.

lol didn't realise i had a Fan Club 🙂

Link to comment
15 hours ago, VVnnXXzzAA said:

I've been trying to figure out the port forwarding situation for a while but not having any luck.  I use TorGuard which has facilities for port forwarding (you go on their customer portal and request a port to be forwarded for a given VPN server, then configure your ovpn file to hit that server so that with your credentials, they know to set up the forwarding on connect).  I've worked with their support team to validate that traffic is flowing through the forwarded port, but still, open port checker websites report the port is closed (although weirdly, if I hit a random port, I get an answer right away, but with my targeted port it takes a longer time to determine --as if it is timing out).  In any case, @binhex I'm not sure what's the best way to debug.  Privoxy works, torrent files work, but magnet links relying on DHT do not.  rtorrent also gives me MUCH higher speeds for the torrents that DO work vs deluge (saturating my internet bandwidth), so I really want to get this to work.  I'm running this on a QNAP NAS.  Is it possible that the iptables settings or the ip route are doing funny things?

 

Bump on this question, but also in trying to debug, I noticed that the iptables settings for INPUT allow all incoming traffic from the VPN tun0 interface.  Isn't that a security hole?  Shouldn't we be more selective about what ports to open for incoming traffic from the VPN network?

Link to comment
18 minutes ago, binhex said:

This will be a configuration option in your /config/rtorrent/config/rtorrent.rc file that is no longer compatible with the newer version of rtorrent (now v0.9.8).

 

The permanent fix for this is to simply rename or delete the existing config file /config/rtorrent/config/rtorrent.rc and then restart the container, then re-edit the config file if required to re-apply any settings you want, sadly this is not something i can automate for you.

 

I renamed the old .rc file, updated the container again to the new one and let a new .rc file get generated but im still getting:

 

2021-02-11 12:31:38,726 DEBG 'watchdog-script' stdout output:
[warn] Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...

2021-02-11 12:32:08,909 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.x.xxx.101 different, marking for reconfigure

2021-02-11 12:32:08,912 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2021-02-11 12:32:08,916 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2021-02-11 12:32:08,919 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2021-02-11 12:32:08,920 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2021-02-11 12:32:08,942 DEBG 'watchdog-script' stdout output:
Script done.

2021-02-11 12:32:19,994 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries

2021-02-11 12:32:19,994 DEBG 'watchdog-script' stdout output:

 

Link to comment
19 minutes ago, VVnnXXzzAA said:

I noticed that the iptables settings for INPUT allow all incoming traffic from the VPN tun0 interface.  Isn't that a security hole?

not for 99% of providers, no, nearly all (there is only 1 I'm aware of that doesnt block) block all incoming ports, allowing to define a single port for port forwarding, so by default everything inbound is blocked.

Link to comment
17 minutes ago, DontWorryScro said:

I renamed the old .rc file, updated the container again to the new one and let a new .rc file get generated but im still getting:

ok thats really odd!, im running the latest image here myself so it has been tested. ok can you attach (not paste) your rtorrent.rc file and i will take a look at it and see if i can spot a problem with it.

Link to comment
16 minutes ago, binhex said:

you have changed quite a bit from the default there!, i believe this is your issue, but there could be more:-

 

line 155:- set_max_file_size = 300G

 

remove that line, save the file and restart the container.

 

Yep that last line was the doozy.  Removed it and all is well now.  Do we know if there is an updated way to indicate a larger max file size that wont sink the launch?

Thanks for the help.

Edit: Found it, I think. 

 

"set_max_file_size" was deprecated. 

 

The new way to accomplish this is with:

 

system.file.max_size.set = 

 

Edited by DontWorryScro
the answer
  • Like 1
Link to comment
 
Yep that last line was the doozy.  Removed it and all is well now.  Do we know if there is an updated way to indicate a larger max file size that wont sink the launch?
Thanks for the help.
I don't know the answer, but I'm sure Google does

Sent from my iPlay_40 using Tapatalk

Link to comment
15 hours ago, VVnnXXzzAA said:

I've been trying to figure out the port forwarding situation for a while but not having any luck.  I use TorGuard which has facilities for port forwarding (you go on their customer portal and request a port to be forwarded for a given VPN server, then configure your ovpn file to hit that server so that with your credentials, they know to set up the forwarding on connect).  I've worked with their support team to validate that traffic is flowing through the forwarded port, but still, open port checker websites report the port is closed (although weirdly, if I hit a random port, I get an answer right away, but with my targeted port it takes a longer time to determine --as if it is timing out).  In any case, @binhex I'm not sure what's the best way to debug.  Privoxy works, torrent files work, but magnet links relying on DHT do not.  rtorrent also gives me MUCH higher speeds for the torrents that DO work vs deluge (saturating my internet bandwidth), so I really want to get this to work.  I'm running this on a QNAP NAS.  Is it possible that the iptables settings or the ip route are doing funny things?

 

For those who might run into this problem.  The issue was the firewall on the QNAP.  The basic firewall from the ControlPanel->Security is employing something very restrictive and not configurable.  Switching to use QuFirewall without any additional changes actually fixed the issue...

Link to comment
15 minutes ago, DontWorryScro said:

file manager was meant to work?? ive never had it working for me, figured it was some limitation of the containerizing of rtorrent.

 

 

 

I've installed an old version manually. Can't get the newer version working for the life of mine.

Link to comment

I've been using this container for years, and I've been running into a lot of issues lately. I've pinned the container to the last working version: binhex/arch-rtorrentvpn:rtorrent-ps-1.1.r54.ga787dd9-1-28

 

For some reason, it's failing to start rtorrent. I did a dist upgrade from Ubuntu 18.04 and 20.04 a few weeks ago and I'm not sure if that's part of it. What else can I look through if Rtorrent is failing to start? Is there another log?

 

I'm also getting this error:

 Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken'

 

 

I'm also getting this a minutes after the last healthy log message:

2021-02-12 03:48:05,459 WARN received SIGTERM indicating exit request

 

Edited by bumperjeep
Link to comment

I'm getting a warning message in my log every 30 minutes (I'm using the latest ( ? ) docker image as of 3 days ago). 

 

2021-02-11 18:08:37,353 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

 

I found a post for DelugeVPN that had the same issue almost a year ago that was resolved per this post:

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/page/243/?tab=comments#comment-857506

 

@binhex I'm assuming a similar cause and fix can be made or is this something on my end?

Link to comment

Hello,

I'm also having trouble after the update.  I've renamed the old /appdata/binhex-rtorrentvpn/rtorrent/config/rtorrent.rc.  A new rtorrent.rc was created after updating and restarting, and I've made no modifications to it.  All of my torrents are missing. 

The log gives me this error:

[12.02.2021 10:02:04] JS error: [http://admin:XXXX@192.168.1.2:9080/js/stable.js : 1783] TypeError: this.dBody is undefined

Link to comment
11 hours ago, Cat_Seeder said:

Well, with the last update my ancient version of rutorrent's file manager plugin is officialy dead.

Did anyone get the newer version of https://github.com/nelu/rutorrent-filemanagerhttps://github.com/nelu/rutorrent-filemanager-media and https://github.com/nelu/rutorrent-filemanager-share to work?

 

I can't live without file manager.

no idea on this one as i dont use that plugin, but take a look at the open issues, there are some possible workaround for some of them:- https://github.com/nelu/rutorrent-filemanager/issues

Link to comment
8 hours ago, ATEglauer said:

I'm getting a warning message in my log every 30 minutes (I'm using the latest ( ? ) docker image as of 3 days ago). 

 


2021-02-11 18:08:37,353 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

 

I found a post for DelugeVPN that had the same issue almost a year ago that was resolved per this post:

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/page/243/?tab=comments#comment-857506

 

@binhex I'm assuming a similar cause and fix can be made or is this something on my end?

you can ignore this, i need to fix this up at some point, but its non fatal so can be ignored for now.

Link to comment
2 minutes ago, Cessquill said:

Hi - renamed the .rc file, updated the container, didn't make any other changes.  Can't get into the web GUI (took too long to respond).  As far as I'm aware, I'm running stock.  Attached log with user/pass redacted.

 

Any ideas?

supervisord.log 84.38 kB · 0 downloads

there are no issues in that log, i can see rtorrent starts ok so the issue is not related to the rtorrent.rc file, check your browser, clear cache and cookies, also try another browser and machine too if possible.

Link to comment
12 minutes ago, binhex said:

there are no issues in that log, i can see rtorrent starts ok so the issue is not related to the rtorrent.rc file, check your browser, clear cache and cookies, also try another browser and machine too if possible.

Cleared cookies, tried two different browsers on another machine, just times out. Was definitely working before update, so a bit confused.

Link to comment
7 minutes ago, Cessquill said:

Cleared cookies, tried two different browsers on another machine, just times out. Was definitely working before update, so a bit confused.

it maybe related to a change in session data (guessing here), try renaming /config/rtorrent/session/ folder to /config/rtorrent/session-old/ then restart, this will mean any torrents listed will need to be re-added though, so be aware of this before try it, you can of course always revert this change by renaming the session folder back again. 

 

if you have not done much configuration changes and you are willing to re-input config you could always simply delete /config/rtorrent/ and /config/rutorrent/ to reset it back to defaults - to confirm i am running this image myself with no issues so i know it works - tested upgrade from the previous image and a clean install.

Link to comment
1 hour ago, binhex said:

it maybe related to a change in session data (guessing here), try renaming /config/rtorrent/session/ folder to /config/rtorrent/session-old/ then restart, this will mean any torrents listed will need to be re-added though, so be aware of this before try it, you can of course always revert this change by renaming the session folder back again. 

 

if you have not done much configuration changes and you are willing to re-input config you could always simply delete /config/rtorrent/ and /config/rutorrent/ to reset it back to defaults - to confirm i am running this image myself with no issues so i know it works - tested upgrade from the previous image and a clean install.

Progress - kind of.  Tried all of the above, no difference.  Then tried accessing from externally via reverse proxy, and I'm in.  Restored original config/session and it's back to how it was (externally).

 

Just can't access the web GUI from inside my network.  All other dockers are fine internally (incl 7 other binhex), and I've made no changes to pfSense.  Hadn't tried external links for a year because of lockdown here. My network here isn't complicated, so I'm scratching my head. 

  • Like 1
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.