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.

[DEPRECATED] Linuxserver.io - Rutorrent

Featured Replies

linuxserver_medium.png

 

 

As off March 13, 2021 this image has been deprecated, read the notice here https://info.linuxserver.io/issues/2021-03-13-rutorrent/

 

Application Name: Rutorrent

Application Site: https://github.com/Novik/ruTorrent/

Docker Hub: https://hub.docker.com/r/linuxserver/rutorrent/

Github: https://github.com/linuxserver/docker-rutorrent

 

Please post any questions/issues relating to this docker you have in this thread.

 

If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

 

Rtorrent has a comprehensive list of options and this should be the first port of call for configuration option/issues

https://github.com/rakshasa/rtorrent/wiki/rTorrent-0.9-Comprehensive-Command-list-(WIP)#comprehensive-list-of-rtorrent-09-commands

 

**Attention - Latest Update - Image Rewrite** 11/12/2018

We have rewrite to our newest image, so much more lightweight, supports theme folders, fixes a known shutdown bug.

 

Please make sure you backup your appdata before updating in case of any issues.

 

IMPORTANT 23/08/2018

If after updating the image you see message in the webui about rtorrent connection etc, you will need to delete or comment out the following 2 lines in /config/rtorrent/rtorrent.rc.

You should comment or delete them regardless if they are set to yes or no. 

 

use_udp_trackers = yes

peer_exchange = yes

 

restart the container and the problem should be resolved.

Edited by linuxserver.io
.

  • Replies 688
  • Views 177.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • sparklyballs
    sparklyballs

    Just added note to the first post on how to resolve this.  

  • scubafossil
    scubafossil

    Done got it working. How I did it. 1.)  SSH into your machine   2.)  Enter the following command replacing your file structure.  Note I could not get it to work if I changed the 443 port. docke

  • gustomucho
    gustomucho

    @xthursdayx It is actually much easier than that. Simply copy the contents of your "/mnt/user/appdata/rutorrent/rtorrent/rtorrent_sess" into the following folder : "/mnt/user/appdata/binhex-rtorrentvp

Posted Images

  • Author

IMPORTANT

 

Anyone that was using the beta container, switch to this container.

 

The beta container has been removed.

Thanks for doing this. I had no problem setting up old CapInsano's but am not having luck here. Thoughts?

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="rutorrent" --net="bridge" -e PUID="99" -e PGID="100" -e TZ="America/New_York" -p 80:80/tcp -p 45566:45566/tcp -p 45567:45567/tcp -p 45568:45568/tcp -p 45569:45569/tcp -p 45570:45570/tcp -p 45571:45571/tcp -p 45572:45572/tcp -p 45573:45573/tcp -p 45574:45574/tcp -p 45575:45575/tcp -p 45576:45576/tcp -p 9527:9527/udp -v "/mnt/user/appdata/rutorrent2/":"/config":rw -v "/mnt/user/Torrents/":"/downloads":rw linuxserver/rutorrent

d75cb586aecd75570489e790ea3dd344a7e22cdfcc6dedfbaa5508aa9676b661
Error response from daemon: Cannot start container d75cb586aecd75570489e790ea3dd344a7e22cdfcc6dedfbaa5508aa9676b661: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use

unraid is on port 80.....

 

change the port 80 assignment (host side only) to something other than 80.

DOH [sigh] ... ermmm why is it defaulting to that out of curiosity?

Problem solved, up and running. Thank you very much for taking on this docker.

It defaults to that as that is rtorrents default port. 

 

It's been discussed before on the forum that port mapping should be left to the user not the docker author.

 

The reason is, if we changed it from default then whatever we changed it to would possibly cause someone else the same issue you had.

 

Plus, not everyone runs Unraid on port 80.

A perfectly fair explanation. I do feel like perhaps that is something to put in the actual docker comment just like where /config is mentioned.

 

Just a thought, and worth about as much :)

 

Cheers, -A

Is it possible to set this up through a reverse proxy? When I point it to http://ip:9091 I just get what looks like a white search box.

2016-03-09_122625.png.65d3018917885cb5fbb023f0f3d8d69e.png

Is it possible to set this up through a reverse proxy? When I point it to http://ip:9091 I just get what looks like a white search box.

 

muximux is not a reverse proxy.

 

I have muximux running through the Apache-Docker.

 

<Location /rtorrent>
ProxyPass http://ip:9091
ProxyPassReverse http://ip:9091
</Location>

Is it possible to set this up through a reverse proxy? When I point it to http://ip:9091 I just get what looks like a white search box.

 

muximux is not a reverse proxy.

 

I have muximux running through the Apache-Docker.

 

<Location /rtorrent>
ProxyPass http://ip:9091
ProxyPassReverse http://ip:9091
</Location>

 

But you're still adding another layer between rtorrent and apache by using Muximux...

Is it possible to set this up through a reverse proxy? When I point it to http://ip:9091 I just get what looks like a white search box.

 

muximux is not a reverse proxy.

 

I have muximux running through the Apache-Docker.

 

<Location /rtorrent>
ProxyPass http://ip:9091
ProxyPassReverse http://ip:9091
</Location>

 

But you're still adding another layer between rtorrent and apache by using Muximux...

 

The link in muximux is pointing to domain/rtorrent . even if I try going straight to the domain/rtorrent, it gives the same result.

 

Also, would it be possible to include autodl-irssi?https://github.com/autodl-community/autodl-irssi

 

thanks for the docker

Thanks a lot for supporting this docker! Makes life a lot easier not having to run a linux VM and set up via the command line.

 

1 question though, I just set this up and it didn't prompt me for any credentials. How should we secure this?

Looking for clarification on an error I'm getting and was hoping for some help.

Initially I was using the captinsano version of the ruTorrent docker, but after it was released by Linuxserver.io I decided to move to that version since all my other dockers are compiled by them. Had everything up and running fine, downloading and seeding files, then the other day we had several days of thunderstorms rolling through. My system had to shutdown, which is fine because I needed to reboot for the 6.1.9 upgrade. Didn't pay any attention till today when I went to add a new torrent and found that all the downloads and seeds I had running were no longer listed and I'm getting the bellow error in the log.

 

[16.03.2016 19:46:32] WebUI started.

[16.03.2016 19:46:32] 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.

 

Renamed the config directory and restarted the docker to rebuild the config and then got following errors.

 

[16.03.2016 20:06:12] WebUI started.

[16.03.2016 20:06:13] Bad response from server: (0 [error,getplugins]) NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'http://192.168.0.20:8089/php/getplugins.php'.

[16.03.2016 20:06:13] Bad response from server: (0 [error,getuisettings])

 

Application no longer looks like it wants to run correctly. Any clue on resolving this? Thanks.

I know you said you renamed config but try deleting the container and repulling it as well. 

Deleted and rebuilt. Get the following error again.

 

[16.03.2016 20:54:44] WebUI started.

[16.03.2016 20:54:45] Bad response from server: (0 [error,getplugins]) NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'http://192.168.0.20:8089/php/getplugins.php'.

[16.03.2016 20:54:45] Bad response from server: (0 [error,getuisettings])

 

Thanks.

Not sure what else to suggest.  Fresh pull works for both Sparklyballs and me...  ???

 

Just to confirm,

 

  • You've deleted the appdata folder (or are using a completely fresh config)?
  • Appdata share is set to cache only and hasn't been moved to the array?
  • You've removed the docker container and done a fresh pull?

Not sure what else to suggest.  Fresh pull works for both Sparklyballs and me...  ???

 

Just to confirm,

 

  • You've deleted the appdata folder (or are using a completely fresh config)?
  • Appdata share is set to cache only and hasn't been moved to the array?
  • You've removed the docker container and done a fresh pull?

 

1. Yes, stopped the container, deleted the config folder on my cache drive, restarted the container to rebuild the config directory and files.

2. appData folder is on the cache drive along with configs for all my other containers. No issue with any of the others that I can see.

3. Removed the docker container as well as the image and reinstalled/pulled. No effect.

 

If no other resolution can be found, I'll reboot the server tomorrow when I get home from work and see if that does the trick. When in doubt, reboot I guess. lol.

 

Thanks.

If no other resolution can be found, I'll reboot the server tomorrow when I get home from work and see if that does the trick. When in doubt, reboot I guess. lol.

 

Are you on your LAN at the moment then? Or accessing it over WAN? Or over VPN?

I was on my LAN accessing my server from my gaming computer.

Rebooted my system and reinstalled ruTorrent, but it will still not run correctly. Unsure of the problem.

 

Still getting the following error upon starting the container and accessing the webhost.

 

[17.03.2016 18:05:21] WebUI started.

[17.03.2016 18:05:22] Bad response from server: (0 [error,getplugins]) NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'http://192.168.0.20:8089/php/getplugins.php'.

[17.03.2016 18:05:22] Bad response from server: (0 [error,getuisettings])

 

I did notice that when I was reinstalling, I kept seeing that some of the image already was installed:

 

IMAGE ID [f70b0c417072]: Pulling fs layer.

IMAGE ID [f7eef3e8d2a5]: Already exists.

IMAGE ID [f504bc93666d]: Already exists.

IMAGE ID [9e58b20b58ab]: Already exists.

IMAGE ID [97b492236f76]: Already exists.

IMAGE ID [1e4ce1496f97]: Already exists.

IMAGE ID [b3260a41280d]: Already exists.

IMAGE ID [a4e1f7d8ab53]: Already exists.

IMAGE ID [35100966404c]: Already exists.

IMAGE ID [f6953bdb8339]: Already exists.

IMAGE ID [6e9b74243288]: Already exists.

IMAGE ID [83770ba1bc9a]: Already exists.

IMAGE ID [82d40d68893f]: Already exists.

IMAGE ID [87c5ffca2485]: Already exists.

IMAGE ID [f38bff93c51e]: Already exists.

IMAGE ID [497ee53addc1]: Already exists.

IMAGE ID [4ede16d1bc02]: Downloading 100% of 32 B. Verifying Checksum. Download complete.

 

Is this normal, or is there a way to delete everything in case something in these pieces, that already exist, is causing the issue?

 

Thanks.

That is normal as some of the data will be in place from other containers that share the same base image for example.  I'm at a loss of what else to try though.

 

 

Can you post a screenshot of your setup... Like this...

 

R7jlfdd.png

Screen shot posted below.

 

Noticed your's looks different, but then I saw you were using 6.2 beta. :)

 

Thanks

Capture.PNG.dd45c9a19caea484d1abed69cde71988.PNG

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...

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.