I am not sure whether it has been mentioned, but how do you set a password for this rTorrent container? I have an open port through my Asus router, so anybody can login if you they know the port. Thanks!!!

Edited April 8, 20188 yr by pervin_1

8 hours ago, pervin_1 said:

I am not sure whether it has been mentioned, but how do you set a password for this rTorrent container? I have an open port through my Asus router, so anybody can login if you they know the port. Thanks!!!

Then you probably have lots of bots trying to login right now.

delete

Edited April 8, 20188 yr by pervin_1

26 minutes ago, trurl said:

Then you probably have lots of bots trying to login right now.

There is no login, open house haha. I stopped the container though, can you help me? I know binhex has another container with rTorrent and password, but I need this docker container instead. Would appreciate any help and support!!!!

13 minutes ago, pervin_1 said:

There is no login, open house haha. I stopped the container though, can you help me? I know binhex has another container with rTorrent and password, but I need this docker container instead. Would appreciate any help and support!!!!

 

 

https://github.com/Novik/ruTorrent/wiki/Config#authentication

1 hour ago, sparklyballs said:

 

 

https://github.com/Novik/ruTorrent/wiki/Config#authentication

Thank you! 

should RSS be able to auto-download?  I thought I had this setup working but now it's doesn't seem to. Torrents come in via RSS as a status of RSS and I have to manually click on them to load them.

 

 

 

trying to configure the docker container but I get this error message.

I'm not sure how to check the ports in use and delete them. Anyone? 

login as: root
[email protected]'s password:
Linux openmediavault 4.15.0-0.bpo.2-amd64 #1 SMP Debian 4.15.11-1~bpo9+1 (2018-04-07) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Apr 14 16:02:12 2018 from 192.168.1.110
root@openmediavault:~# docker create --name=rutorrent \
> -v /home/docker/rutorrent/config:/config \
> -v /sharedfolders/media/downloads:/downloads \
> -e PGID=1001 -e PUID=1001 \
> -e TZ=Europe/Stockholm \
> -p 80:80 -p 5000:5000 \
> -p 51413:51413 -p 61318:61318/udp \
> linuxserver/rutorrent
e780ee012eadd5298fda964099cef9037d0fea1dda09e97e2e666e29c0c394e1
root@openmediavault:~# sudo docker start rutorrent
Error response from daemon: driver failed programming external connectivity on endpoint rutorrent (b39bbc2767a1b3e1f742c01f85b160ffe24e5a8dcb4304d1553b79dce96a45a1): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
Error: failed to start containers: rutorrent
root@openmediavault:~#

 

 

I changed the ports 80 -> 81 now the docker container is up but the web gui is not accessible at 192.168.x.x:81 firefox says "Unable to connect"

am I missing something here?

 

Edited April 15, 20188 yr by prynn
added a screenshot

5 hours ago, prynn said:

trying to configure the docker container but I get this error message.

I'm not sure how to check the ports in use and delete them. Anyone? 

 

Looks like you are trying to run this docker on a platform other than unRAID. This is the unRAID forum.

 

The first post of support threads often includes useful information that should be consulted, such as this:

Quote

If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support.

 

So ruTorrent keeps stopping all of my downloads and "resets" their progress.

I have ~8TB of free space left on my unraid server, with about 963GB worth of queued up data to be downloaded in my ruTorrent. 
 

I had everything stopped and was downloading one item at a time due to their size and I was wanting to manage as many as possible for organizational purposes while I was awake.  So because of this I have several items that are currently" stopped at any where from 0% completed to ~10% completed.  Now my torrents don't use my cache drive so it's not running into any storage issues from my cache drive running out of space.

Let's say I start up Torrent 1 which is currently at 10% completed.  For some reason, once it hits some random point, the torrent switches back to "stopped" and it's progress will say 10%.  Even though when it was downloading it hit say 60% before it stopped.  If I force recheck the file, it will find 60% completed and start back up from there, but then shortly will stop and reset back to 10%.

If I start all the files, at some point, everything will stop at the same time, and reset back to it's original progress completed from when I started them all (so any where from 0% to ~15% depending which file it is).  During this time, my download limit changes from unlimited back to it's default 9.7MiB/s.

Any ideas?

3 hours ago, Meller said:

Any ideas?

Double check that all your paths defined inside ruTorrent correspond to container side mapped paths in your docker config. It sounds like your in progress downloads may be sitting inside your docker image file instead of being mapped to a server drive.

They are... as up until day before yesterday it was downloading just fine.  In fact, when I got sonarr to download about 10 new episodes of a few shows last night they all downloaded no problem. 

Grant it, for some reason ruTorrent didn't auto move them to completed like it always does and it didn't auto unpack the files like it always has done, but it did download.

Then ruTorrent has it's "incoming" folder in the /downloads/ and it's completed folder it's suppose to move things too.  The auto move works like 75% of the time now.  If i navigate to the share for downloads/incoming I see the files it's downloading.

In this case, I even tried completely deleting them and starting fresh on them all.  But then all they do is reset do 0% and change their status to "stopped"

2 hours ago, Meller said:

Then ruTorrent has it's "incoming" folder in the /downloads/ and it's completed folder it's suppose to move things too.  The auto move works like 75% of the time now.  If i navigate to the share for downloads/incoming I see the files it's downloading.

In this case, I even tried completely deleting them and starting fresh on them all.  But then all they do is reset do 0% and change their status to "stopped"

Are any of your array drives low on space? Do you have proper minimum free space set for your shares?

Um, one of my 8TB drives is at 90%, the other two combined give me 8TB of free space.  One is sitting at 3TB full, the other is at 5TB full.

35 minutes ago, Meller said:

Um, one of my 8TB drives is at 90%, the other two combined give me 8TB of free space.  One is sitting at 3TB full, the other is at 5TB full.

 

And what are the settings for your Torrents User Share?

 

Post a screenshot or just go to Tools - Diagnostics and post complete zip.

 

Thanks for the docker.

 

Just quick question, what options would I need to change to enable /RPC2 under https/ssl? It works fine over http/80 however when I change the nginx config todo SSL everything works apart from that.

 

No point in posting nginx extensive nginx log for it it simply says:

Quote

upstream prematurely closed connection while reading response header from upstream, client: 192.168.1.2, server: localhost, request: "GET /RPC2 HTTP/1.1", upstream: "scgi://unix:/run/php/.rtorrent.sock:", host: "hostname.x"

 

EDIT: Tried serving /RPC2 over port 80 with SSL still no luck.

Edited April 18, 20188 yr by user457453944

I have change the default port of rutorrent, in the docker template, software and rtorrent.rc file

After many days and restarts I get in my fw (pfsense) many blocks to the port 51413 which was the previous default, it like every minute a get  few of those. Does it make sense? why are there IP trying to contact to the old port? is the setting still maybe embeded somewhere in docker? ruttorents reports my current port as open and is working fine bur having so many ip's calling to the old/default rtorrent port smells bad.

 

	May 6 00:31:36	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:51043	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:31:36	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:27913	xx.xxx.xxx.146:51413	UDP
	May 6 00:31:39	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:51043	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:31:39	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:27913	xx.xxx.xxx.146:51413	UDP

 

	May 6 00:26:04	WAN	Default deny rule IPv4 (1000000103)	68.63.214.93:36440	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:26:05	WAN	Default deny rule IPv4 (1000000103)	68.63.214.93:36440	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:26:07	WAN	Default deny rule IPv4 (1000000103)	68.63.214.93:36440	xx.xxx.xxx.146:51413	TCP:S

9 hours ago, L0rdRaiden said:

I have change the default port of rutorrent, in the docker template, software and rtorrent.rc file

After many days and restarts I get in my fw (pfsense) many blocks to the port 51413 which was the previous default, it like every minute a get  few of those. Does it make sense? why are there IP trying to contact to the old port? is the setting still maybe embeded somewhere in docker? ruttorents reports my current port as open and is working fine bur having so many ip's calling to the old/default rtorrent port smells bad.

 

	May 6 00:31:36	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:51043	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:31:36	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:27913	xx.xxx.xxx.146:51413	UDP
	May 6 00:31:39	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:51043	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:31:39	WAN	Default deny rule IPv4 (1000000103)	91.105.85.183:27913	xx.xxx.xxx.146:51413	UDP

 

	May 6 00:26:04	WAN	Default deny rule IPv4 (1000000103)	68.63.214.93:36440	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:26:05	WAN	Default deny rule IPv4 (1000000103)	68.63.214.93:36440	xx.xxx.xxx.146:51413	TCP:S
	May 6 00:26:07	WAN	Default deny rule IPv4 (1000000103)	68.63.214.93:36440	xx.xxx.xxx.146:51413	TCP:S

 

we don't recommend or support changing the container side ports

 

if you need a different port change the host port side only

So, back again with another rutorrent issue.  Just started today.  Haven't changed a single thing.  the program has been working pretty much exactly as intended for the last couple of weeks. 

As of today, as soon as it starts to download anything, the entire app becomes unreachable.  If you hit refresh it just spins and spins until it finally loads the rutorrent webui with this error in the log " Bad response from server: (504 [error,getplugins]) Gateway Time-out".  If nothing is downloading though, I have no issues navigating the webui, force checking previous downloads that are currently  paused or anything. 

I haven't changed any settings on anything in my network or on my unraid server so... i don't know.

I'm getting plugin errors such as Unpack plugin: rTorrent user can't access 'unrar' program.   The only things I use in rutorrent is unpack and auto move.  But they've been working no problem for weeks. 

Edited May 7, 20188 yr by Meller

It's just continuously "timing out" over and over and over.

If I restart my entire unraid server, it'll work no problem until I start a new download.  Then it just goes on this "timing out" thing again.

Every time I download something new I dont have permisions to modify it with samba (windows explorer), then I run un unraid tools->new permisions and it works

How can I fix this permanently? the share is shared as public.

Edited May 15, 20188 yr by L0rdRaiden

So I've run into a dead end, and now rutorrent isn't working for me...

 

I needed to expose the SCGI Port of rtorrent to get a couple other media-downloading-related dockers to connect to it.

 

I downloaded the rtorrent.rc file using SMB and modified it on a windows machine.

 

I used the FTP server to put the new rtorrent.rc in its proper place, ran chmod 777 on the rtorrent.rc in Appdata using filezilla, opened up port 5000 on the docker and rebooted the rutorrent docker. 

 

It says the following: 

[30.05.2018 17:41:05] WebUI started.

[30.05.2018 17:41:06] 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.

 

I honestly don't know what else to do other than deleting the docker, wiping out the appdata for rutorrent, and re-downloading it and re-setting it up. 

 

Another problem is where it is set to download: It always wants to put new torrents at "/downloads/incoming/" when I want it to JUST download to "/downloads/." I modded the settings but everytime I restart the docker, it reverts back to /downloads/incoming/.

 

EDIT: Blew away the appdata and reinstalled rutorrent, now it's working, but I still need to know how to expose SCGI and how to fix it to download to just "/downloads/""

EDIT2: Got SCGI to work. 

Edited May 31, 20188 yr by urbanracer34

Small thing I just noticed, if ruTorrent creates the folder (say, moving torrents from /test/ -> /test/sub/ when sub isn't already created) it creates the folder with 755, owner of nobody, meaning that even if unraid has permissions set, you can't write to it. I can just set newperms or set folder permissions to 777, but I'd prefer not having to if possible.

4 hours ago, nZero said:

Small thing I just noticed, if ruTorrent creates the folder (say, moving torrents from /test/ -> /test/sub/ when sub isn't already created) it creates the folder with 755, owner of nobody, meaning that even if unraid has permissions set, you can't write to it. I can just set newperms or set folder permissions to 777, but I'd prefer not having to if possible.

 

Default user perms of Unraid are nobody:users