Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - rTorrentVPN

Featured Replies

Hi binhex, I'm running this in a container in a QNAP NAS, trying to create a new user for the rutorrent webui with "docker exec -it arch-rtorrentvpn-1 /home/nobody/createuser.sh XXXXX. I get "-sh: line 7: docker: command not found".

I'm a noob. How should I proceed? Thank you.

  • Replies 3k
  • Views 609.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most 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

  • @binhex Any plans to update this docker now when ruTorrent 4.0.1 is released? Seems like a very nice update from them.

  • its very possible that there was an issue with autodl-irssi at the time of the build (pulls from master branch), and this issue has now been resolved, so subsequent builds are ok, i will create a new

Posted Images

Hey Binhex, had everything working this morning, and as time goes on i notice the following in the logs when ever I try to connect to the webgui : 

 

 

2018/12/15 18:09:49 [error] 848#848: *344 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.128.90:9080"

 

I am getting a timeout on rutorrent and it finally loads up with the following errpr : 

 

[15.12.2018 18:13:53] The request to rTorrent has timed out.

 

 

Is there something im doing wrong?

How is cpu usage? You will get timeouts with high cpu usage.

Hey Binhex, had everything working this morning, and as time goes on i notice the following in the logs when ever I try to connect to the webgui : 
 
 
2018/12/15 18:09:49 [error] 848#848: *344 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.128.90:9080"
 
I am getting a timeout on rutorrent and it finally loads up with the following errpr : 
 
[15.12.2018 18:13:53] The request to rTorrent has timed out.
 
 
Is there something im doing wrong?


Sent from my Pixel 2 XL using Tapatalk

Its a dell r510 with quite a beefy cpu, i rarely ever see it go over 10% usage : 

CPU_usgae.PNG

If you go to docker what it show for cpu usage? Also that one core has high cpu

Its a dell r510 with quite a beefy cpu, i rarely ever see it go over 10% usage : 
CPU_usgae.thumb.PNG.18e94b6292c482d02a6275586d3deac3.PNG
7e3b518addaacca19bfdcf9e439658e2.jpg

Sent from my Pixel 2 XL using Tapatalk

Also I'll trade you my r710

Sent from my Pixel 2 XL using Tapatalk

1 minute ago, scubieman said:

Also I'll trade you my r710

Sent from my Pixel 2 XL using Tapatalk
 

Hah! I am quite happy with the r510, but thank you for the offer! 

The CPU spike is I'm currently rsycing servers into mine. Its about 8TB of data total incoming right now.

 

As far as that CPU, it just started working right now, but the CPU is low : 

 

cpu_docker.PNG

I'm out of ideas.
Sidenote I'll pm my address to ship r510 lol

Hah! I am quite happy with the r510, but thank you for the offer! 
The CPU spike is I'm currently rsycing servers into mine. Its about 8TB of data total incoming right now.
 
As far as that CPU, it just started working right now, but the CPU is low : 
 
cpu_docker.thumb.PNG.966a800302c82abd6ea6fa3ed76510d7.PNG


Sent from my Pixel 2 XL using Tapatalk

Just crashed again, does not look like the CPU shot up at all...

Is it up to date?

Sent from my Pixel 2 XL using Tapatalk

Just updated it, see anything wrong wiith my config : 

1.PNG

2.PNG

3.PNG

by update i mean force updated it.

Your network is 192.168.128 ??

Rest looks fine

Sent from my Pixel 2 XL using Tapatalk

Host path 2 I have set to my downloads share.

 

The media share key should be fine

 

You may need to set key 13 the timezone.15287db5ad6fea8524534600e55115f7.jpg&key=e90363bbd6bc3c7af012abc93d36ce8f38ae12b38a7638178e2dad3e3379d5aa

 

Also I don't see the movies key. Which should not be a problem. You may need to update key 13 the timezone

 

Sent from my Pixel 2 XL using Tapatalk

 

 

 

 

Edited by scubieman

i made a change, i will report back when i get home if its still working, thank you for the help! ~3 hours

Just now, denellum said:

i made a change, i will report back when i get home if its still working, thank you for the help! ~3 hours

not sure which change you made. however the movies key should be fine.

 

Also not saying the timezone has anything to do with it. Its just something different.

 

Also you seeing this in the unraid log file? i can check mine for issues

Alright it had SOMETHING to do with adding YTS as an RSS feed. No idea why, but when I removed it, it worked. Thanks a ton @scubieman.

Then I didn't help. I didn't suggest that ha ha

Alright it had SOMETHING to do with adding YTS as an RSS feed. No idea why, but when I removed it, it worked. Thanks a ton@scubieman.


Sent from my Pixel 2 XL using Tapatalk

Hey Binhex, I've been using quite a few of your containers for a couple of years now without any trouble up until now (thank you for the awesome containers and support!) Recently I decided to set up all of my rTorrent containers to use a VPN.. I know after 2 years it's long overdue but I exclusively use private trackers so it wasn't something I really worried about too much. I just want to note that I did get them up and running, but I start running into a lot of trouble when I don't use the Bridged network type. What I really want to use is use br0: Custom so I can set different IPs for all of the containers, but when I do that for rTorrent I can't access the webUI. I did however notice that the torrents will all start and show up as seeding according to the trackers I'm seeding content on. I can also ping the container from a different computer on my network, just can't connect to the webui or with Sonarr/Radarr.

 

Setting the network type to bridged allows me to connect to the webUI just fine, however, I still have issues with Sonarr and Radarr not being able to connect if they are on br0, so I have to set those to the bridged adapter as well. Before when I had the VPN option turned off on all of my rTorrent containers everything was working perfectly together on the br0 adapter. 

 

I have already tried enabling iptable_mangle since you mentioned it for a similar issue in your Q&A, but it didn't seem to help. Do you have any insight as to what is going on here and how I can start using br0 with custom IPs for all of my containers again, or if it is even possible?

When I had this issue the VPN was not set correctly. I believe squid has that in his post somewhere as well. Vaderspaceone also had video on VPN and web UI blank

Hey Binhex, I've been using quite a few of your containers for a couple of years now without any trouble up until now (thank you for the awesome containers and support!) Recently I decided to set up all of my rTorrent containers to use a VPN.. I know after 2 years it's long overdue but I exclusively use private trackers so it wasn't something I really worried about too much. I just want to note that I did get them up and running, but I start running into a lot of trouble when I don't use the Bridged network type. What I really want to use is use br0: Custom so I can set different IPs for all of the containers, but when I do that for rTorrent I can't access the webUI. I did however notice that the torrents will all start and show up as seeding according to the trackers I'm seeding content on. I can also ping the container from a different computer on my network, just can't connect to the webui or with Sonarr/Radarr.
 
Setting the network type to bridged allows me to connect to the webUI just fine, however, I still have issues with Sonarr and Radarr not being able to connect if they are on br0, so I have to set those to the bridged adapter as well. Before when I had the VPN option turned off on all of my rTorrent containers everything was working perfectly together on the br0 adapter. 
 
I have already tried enabling iptable_mangle since you mentioned it for a similar issue in your Q&A, but it didn't seem to help. Do you have any insight as to what is going on here and how I can start using br0 with custom IPs for all of my containers again, or if it is even possible?


Sent from my Pixel 2 XL using Tapatalk

  • Author
8 hours ago, Velodo said:

Setting the network type to bridged allows me to connect to the webUI just fine, however, I still have issues with Sonarr and Radarr not being able to connect if they are on br0, so I have to set those to the bridged adapter as well. Before when I had the VPN option turned off on all of my rTorrent containers everything was working perfectly together on the br0 adapter. 

this is your problem, all of the vpn images i have created were before custom networks were available (years ago) and none of the vpn images have been tested with custom networks, unfortunately i dont have the time at the moment to investigate this, and its non trivial due to iptable rule changes which always require extensive testing, so if it doesnt work then you kinda out of luck for now.

 

Having said that i have made some changes unrelated to this which MAY (or may not) allow this to work, i shall be building this as a new image once i have done further testing.

9 hours ago, scubieman said:

When I had this issue the VPN was not set correctly. I believe squid has that in his post somewhere as well. Vaderspaceone also had video on VPN and web UI blank

 

As far as I can tell the VPN and torrent client still work great, so I think the VPN settings are all correct.

 

1 hour ago, binhex said:

this is your problem, all of the vpn images i have created were before custom networks were available (years ago) and none of the vpn images have been tested with custom networks, unfortunately i dont have the time at the moment to investigate this, and its non trivial due to iptable rule changes which always require extensive testing, so if it doesnt work then you kinda out of luck for now.

 

Having said that i have made some changes unrelated to this which MAY (or may not) allow this to work, i shall be building this as a new image once i have done further testing.

Ah.. I was afraid you were going to say something like that. Since I have everything working great as is now I'll probably leave it alone, but once your changes are ready I'll be happy to test them out to see if it helps with this! 

On 12/15/2018 at 9:05 PM, tomllic said:

Hi binhex, I'm running this in a container in a QNAP NAS, trying to create a new user for the rutorrent webui with "docker exec -it arch-rtorrentvpn-1 /home/nobody/createuser.sh XXXXX. I get "-sh: line 7: docker: command not found".

I'm a noob. How should I proceed? Thank you.

Sorry for the bump, I hope it's allowed, I was hoping someone could help with the issue. Thank you.

  • Author
14 hours ago, tomllic said:

docker: command not found

that is your problem, you need to figure out how to issue docker commands at the command line for QNAP.

  • Author
On 12/17/2018 at 12:53 PM, Velodo said:

but once your changes are ready I'll be happy to test them out

new image got built a day or two ago.

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.