Skip to content

ruTorrent in Docker on a Synology NAS

Last updated on 28th February 2021

In this guide I will take you through the steps required to get ruTorrent up and running on your Synology NAS, I will be making some assumptions that you know your way around the DSM interface but if you any specific questions let me know in the comments.

Downloading the Container

In the majority of my guides I use the containers made by Linux|Server, these have very good documentation and are very well maintained so should any issues arise there is a group of people to ask, plus these work really well on Synology.

Open up Docker within DSM and navigate to the ‘Registry’ section and search for ruTorrent in the keyword box. Right click and download the Linux|Server version. When it asks which version number you want to use just choose latest this will ensure the container updates to new versions when they are released.

Finding the container

Setting up a Docker User for RUTorrent and Obtaining the PGID and PUID

In previous versions of this guide we used your default admin account for each container, this is not very secure so please now follow the separate setup guide and then head back here.

Setting up the Container

Back in the ‘Image’ menu highlight the ruTorrent container and click on Launch. This will open up the setup wizard.


Tick the ‘Enable Auto Restart’ this will ensure the container starts up automatically if you reboot.


On the ‘Volume’ tab you need to add the paths to where you want to keep the config files and where you want all your downloads to take place.

I would recommend creating a ruTorrent folder within the main Docker directory the  same goes for any of my other guides this means you can store all the config files outside of the container, meaning you have easy access to modify and backup, this will save you a ton of time if you ever have to start from fresh. See the image below for the setup.


Next we move to the Port Settings tab, this is where you need to configure the various ports required by ruTorrent to both function correctly and allow you to access the web interface. There a quite a few ports used for Torrents for this tutorial with are leaving everything on Auto with the exception of port 80 which is used for the webUI,you must give this an alternative port number in this case I used 49999.


Last up is the Environment Variables, this is where we enter the details obtained earlier for our PGID and PUID values, all you need to do is enter the details as shown in the screenshot below, this will ensure you have full access to the shares we added earlier.

PGID and PUID Values

Now just click OK and you will be back at the first screen we saw, then click next to see a summary of your setup. You are now ready to roll and can start the container. On first startup it may take a minute of so for everything to setup you can see the status in the logs, you can then access the ruTorrent WebUI via the NAS IP and  port you entered earlier.

Published inDockerSynology


  1. Stephen Stephen

    hi There,

    I used your excellent guide to setup rutorrent on my synology nas and all has run well for 3 years.
    Suddenly utorrent has stopped working – i have tried updating it but i always get this error below.

    There’s nothing in the container logs and i can see in processes rtorrent trying to start but it immediately stops again.

    [18.04.2021 08:15:30] WebUI started.
    [18.04.2021 08:15:30] 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.
    [18.04.2021 08:15:30] _cloudflare: Plugin will not work. Webserver user can’t access external program (python).
    [18.04.2021 08:15:30] _task: Plugin will not work. Webserver user can’t access external program (pgrep).
    [18.04.2021 08:15:30] create: Plugin will not work. It requires plugin(s) _task

    Any ideas?

    • Dr_Frankenstein Dr_Frankenstein

      Are you using the cloudflare plugin? I change clients so often not used rutottent for a while

      • Stephen Stephen

        I didn’t set it up I just used the image as is and it stopped working after an update. What client are you using now?

  2. NineInchPlaya NineInchPlaya

    Got this up and running but I’m having a problem only when it comes to downloading magnet links. It gets stuck on “Downloading” and the filename looks like something along the lines of “D44234234824802.meta” DHT and peer exchange are on, DHT port is 6881. Anyone run into this or have ideas for a fix?

  3. Burger Burger

    Got this installed, and have my Synology Router port forwarding all of the correct ports to my DSM. I’m using Cloudflare for security purposes, have a domain name pointing at my DDNS, and a sub domain pointing my DDNS with a reverse proxy that then points at the GUI. Using a port checker, all of the following say the port(s) I’ve specified in the container are open:

    – Straight IP address (ex.
    – Synology DDNS (ex.
    – Domain name (
    – Subdomain (

    But I cannot for the life of me get it to see that the listening port is open (always says “#####: Port status is unknown”). And I believe because of this, every single torrent I add (from a variety of trackers) turns red because the attempts to communicate with the tracker timeout (Tracker Status: Tracker: [Timed out]).

    Things I’ve tried:

    – Changing ports (and making sure to update the port forwarding rules in my Synology Router)
    – Restarting the container
    – Restarting the DSM
    – Restarting the router
    – Turning off Cloudflare proxying, so the DNS rules are purely just that

    I’ve searched for issues with the port status and found this (, but that should be fixed because that was fixed in May.

    Any help would be really appreciated. Thanks

  4. Robert Robert

    Thx for the guide. I’m getting a error-message when trying to add a torrent-file (*.torrent) from the webinterface, same problems in both ie and chrome. Adding a torrent from URL works fine.

    “[06.06.2020 19:27:04] JS error: [ : 72] Access is denied. ”

    Anyone have a clue what it could be?

  5. finnlugg finnlugg

    Got it working, here is how you do it:
    In container Terminal(create-new bash): htpasswd -c /config/.htpasswd yourusername
    You will be asked for password -create one
    Edit your Nginx: ##
    # Basic settings
    auth_basic “Administrator’s Area”;
    auth_basic_user_file /config/.htpasswd;
    (exactly like this if you have followed Frankenstein guide)
    Restart the container

    • Dr_Frankenstein Dr_Frankenstein

      Thanks much appreciated

  6. finnlugg finnlugg

    HI! Me too want to know how to add a user/password. It would be great if you could provide that in your guide. Thanks for all your work.

  7. Frog Frog

    Hi all,
    Is it possible to add a user / password please

  8. mike holm mike holm

    Can you explain howto setup password for the webif, else everyone in the world can login.

    • Dr_Frankenstein Dr_Frankenstein

      I seem to remember it was just an option in the Web interface itself, I will Check when my torrent box comes on later.

  9. opalOpal opalOpal

    I have “Use hard links instead of copy” selected Settings >Media Management. However, I think the files are actually just being copied, leading to twice the amount of disk space being used for all seeding torrents. Anyone know how to verify this and perhaps fix it if this is the case?

  10. Frog Frog


    Rutorrent takes half of my bandwidth, even when all the torrents are at rest.
    The Docker is in Bridge.

    thank you for your work

  11. broncky broncky

    how can i add a login for rutorrent ? i already read something from the config file but don’t wee it in there.

    • Dr_Frankenstein Dr_Frankenstein

      This is probably covered in the actual rutorrent setup outside of Docker itself

  12. Mike Mike

    Do you have a write up for a Docker for torrents that has VPN as well? I setup one already deluge and it works for downloads only, it will not upload anything. I have the ports right too.

  13. Geoff Geoff

    added the port & opened port 51413 on my Router now showing as green / open , how ever all my torrents i add only stay as queued.
    any pointers what to try

    • Random Internet Guy Random Internet Guy

      Hmmmm. That’s a strange behavior.

      It isn’t a permissions issue, bc you would not have been able to add the torrent to ruTorrent, if ruTorrent weren’t able to see/access the destination folder.

      Try right-clicking on a file, stopping it, then do a Force re-check… then report back what happens.

      • mikesssbb mikesssbb

        I am having the same issue with the torrents being stuck as “Queued”
        Any ideas as to why? Any fixes?

        • mikesssbb mikesssbb

          It was a PGID issue. Even though the PGID I got when through the SSH was 100, it needed to be running as 101. I assume that it is because the user was an admin user and is technically in both groups. Needed to be running in the admin group (101)

  14. ben ben

    Great guide. used to install: diameter/rtorrent-rutorrent. I would like to add ‘filemanager’ plugin. Would you please tell me how

  15. RandomInternetGuy RandomInternetGuy

    This guide was very useful, but you left out a critical step: If you look in the bottom of the ruTorrent UI, you will see a red ball that says “51413 Port is Closed”

    With this port closed, you can download files and it will appear you are actively seeding them, but you arent – you are passively seeding, which means most users wont be able to connect to you.

    For anyone who sees this in the future, to fix this you need to add one additional port setting, for Local Port 51413 : Container Port 51413.

    To do that, go to your Container and stop it. Then click Edit > Port Settings. Click the Add button (at top left) and add a new entry. The GUI will set Local Port to Auto, but need to manually change to 51413 (or whatever your listen port was set to). The GUI may tell you that the number you entered isnt correct, but it is.

    Once you do this, go back to RuTorrent and right click on the Red ball icon and it should change to a green checkmark. If it doesnt, you also need to add a port forwarding rule in your router (which I also had to do) by selecting your NAS IP and the port number for TCP/UDP.

    • brtoncky brtoncky

      thannk you for this info

    • Dr_Frankenstein Dr_Frankenstein

      Thanks I will get the guide updated

    • RxmyB RxmyB

      Hey! It’s been a while since you’ve posted. I hope you read this. I tried almost everything I could but this simply doesn’t work. It keeps saying there is a problem with the local port. It says it is in use of other services or something. Could you help me please?

      • Dr_Frankenstein Dr_Frankenstein

        Hey, just use a different local port when you do the setup I used 49999 for port 80

        • RxmyB RxmyB

          Thanks, I actually got it to work except the portforwarding of 80 hahah… I always used it in the LAN but when I tried to acces outside of my home, I could get to the GUI. I tried forwarding the 80 routerport but it seems like it blocked or something. Any tips?

          • Dr_Frankenstein Dr_Frankenstein

            You will just need to forward the same port you use to access it locally.

          • RxmyB RxmyB

            Hey, Thanks for your reply. I’m sorry to keep asking questions here, but that doesn’t fix the problem. Still can’t acces the GUI from outside of my LAN.

            So here’s a quick overview. I hope you can help.
            Docker ports:
            Local 49999, ContainerPort 80

            Routerport forwarding:
            Local: 49999, Routerport …. (Here, I can’t say 80 so it gives a random number or something).

            So I used TCP and tried to acces on my private/local IP:49999

            I’m stuck here… haha. I’d really appreciate the help 🙂

          • Dr_Frankenstein Dr_Frankenstein

            Your router port will just be local Diskstationip:49999 the router port will be the same port 49999. You don’t access externally from the local ip address. It will be your Internet ip address and the port number.. Or if you have setup the Synology DDNS service it will be that address and the port number

          • RxmyB RxmyB

            You’re the best! Thanks man 🙂 It works. Got the wrong IP like you said… Won’t make this dumb mistake in the future haha

  16. 1.3EPR 1.3EPR

    Is there a way to add autodl-irssi to this setup?

  17. Greg Greg

    I noticed that ruTorrent set up this way doesn’t have a login or password. Does this mean others can access it? Is this only accessible to people who are logged into the NAS or can anybody access it? If so can a login and password be added into the settings for ruTorrent somehow?

  18. RandomInternetGuy RandomInternetGuy

    This is a great post and excellent write-up – but one thing is missing: Once you get this setup, how do you connect RuTorrent to a Proxy VPN like Private Internet Access so you can mask your IP address?

    I tried adding the Proxy info under Control Panel > Network > Proxy… but my actual IP address is still leaking out, so there is some additional step that is required but I am not sure what. I know the port number used by RuTorrent for incoming connections… but not sure what to do past that.

    • RandomInternetGuy RandomInternetGuy

      For anyone who sees this later… to place your NAS behind a VPN, this is one way to do it:
      1. Go to Control Panel > Network > Network Interface.
      2. Click Create > Create VPN Profile

      Then follow the steps here:

      One thing to note: QuickCOnnect will still work, but you wont be able to access your NAS via your external IP:Port anymore – bc now the entire NAS is behind the VPN.

  19. Roel Roel

    Dr_Frankenstein do you have a tutorial to get rutorrent working on a non-docker Synology?
    I have a DS414 what cannot run docker.

  20. c0rck c0rck

    Thanks for posting this. It helped me getting it up and running, but I still have a question about the Listening Port for incoming connections. I have it set to 6881-6999, which are also NAT’ed on my router to my Synology. Still, ruTorrent says the ports are closed.

    Should I all set them up in the Docker config? That’s going to be a lot of work…

    • RandomInternetGuy RandomInternetGuy

      For what it’s worth, I am having the same problem – I got everythign set up, but ruTorrent says the listening port is closed – and nothing I have tried seems to get it to open up.

  21. gary gary

    Rutorrent does not work at all.
    Instead of Webui, there is a login page for synolgy

    • RandomInternetGuy RandomInternetGuy

      This write-up definitely does work, so you possibly did something wrong. To access RuTorrent, you simply type in the IP address of your NAS and the port number you selected for rTorrent.

      It sounds like you are hitting the login page for the NAS, which is a different port number.

  22. matty matty

    Nice tut, thank you.
    Two already mentioned things:
    – Ports not working
    – delete the .rars after extracting
    who could help here?

  23. Chris Chris

    Thank you for this setup guide, it’s been a great help. I’m rebuilding my 1815+ and I’m trying to use the Docker route for my installs. When I set up the Synocommunity build of rutorrent, there was a problem with _getdir and viewing the file structure, which I got around by using symlinks. However, no luck here.
    To my questions – can you imagine a way to link a Shared folder on an external drive (USB) so that rutorrent can access it. If I add the volume in the DockerGUI it doesn’t work, the container won’t start. But using a symlink to the folder doesn’t work either. It doesn’t show in the directory browser (in rutorrent) although the link is in the /downloads folder.
    Any ideas on where to look?

  24. Kevin Kevin

    I’ve been reading through all your guides as I get ready to start deploying some docker containers. I have two questions.

    1) Do you recommend creating a specific user to be used for all the docker containers? Or are you using something like admin?

    2) If I am not mistaken, when using bridged connections you can specify the ports to be the same. For example for SABnzb you can use 8080 for both the local and container ports. Is there a reason you do not do this?

    Otherwise, great work on these, The efforts of people like you are a tremendous asset to the community,

    • Dr_Frankenstein Dr_Frankenstein

      1) I just use my default admin login (not the actual user called ‘admin’ as that is disabled on my setup for security) you can use whoever you like as long as they have access to the shares you want to add to the containers.

      2) When I first started writing the guides I was port forwarding to the Internet so I would tend to change to a random port number just to obfuscate the connection, in case anyone was trying known ports to get into the NAS. I now use the VPN server and just VPN into my network. So you can use whatever ports you want, either the same ones as the original container or make them up. You will find some ports are already used by DSM for those cases you may want to use a bridge or just use a different port. (I have not used a bridge yet so I may have a play around)

      Glad everyone is finding these useful, I am learning as I go and thought I would share my knowledge (good time to use the domain I have owned for 15 odd years!)

      • Kevin Kevin

        Appreciate the quick response. Very helpful. I hope to carve out some time to get this going over the weekend. Going to give Radarr a try.

  25. Pat Pat

    Your screenshot of the environmental variables shows an incorrect variable for the group ID. The correct variable is PGID like you mentioned in the written portion. The screenshot shows GUID, which does nothing. It looks like the same mistake is in all guides

    • Dr_Frankenstein Dr_Frankenstein

      Hi Pat I will double check the screen shots as I swear I fixed these once already.

      — Update I fixed it, looks like an old screen shot snuck in!

  26. brp brp

    Thanks very much for the guide!

    I’m testing this now, and so far it’s been working pretty well.

    Download station has an issue where the auto-extract feature is SLOW as hell, but it is super fast now when using the RUTorrent auto-extract.

    The one issue I see is that the RUTorrent auto-extract feature doesn’t have the option to auto-delete the archives once done extracting. The Synology Download Station does have this feature. Do you know anyway to get this working on my Synology Box?


    You ROCK!!!!! TY!!! I can now download MASSIVE torrent files!!

  28. Amareto Amareto

    Hi, nice site and guides. Why do you prefer ruTorrent over Deluge?

    • Dr_Frankenstein Dr_Frankenstein

      I don’t really use torrents so this was to cover a request from a Reddit user. I can do a Deluge write up. I just need to test it and make sure it’s working first.

      • NG80 NG80

        Did you manage to get Deluge Docker working on Synology? I’d be interested to read your guide on this!

        • Dr_Frankenstein Dr_Frankenstein

          I have been extremely busy the last couple of months. It’s still on the pad.

    • RandomInternetGuy RandomInternetGuy

      Because Deluge is a very young product and lacks many of the features of ruTorrent.

  29. Crimsonsage Crimsonsage

    This guide was great (just as your others were), but I’m running into one issue. ruTorrent tells me that port 45566 is closed (Default listening port). I’ve tried opening this port on the Synology Firewall, and also on my Router. I know that within docker it’s port 45566, but the “local” port is set to “auto”. I tried manually setting that local port to a specific value, and forwarding it on both the synology and router.. still no luck.

    Any suggestions on the port forwarding?

    • RandomInternetGuy RandomInternetGuy

      Im having the same problem…. the default listening port is closed and nothing I have tried seems to work to get it open.

      • Just like when you set the webui port to 49999, add an other port like 51413 as local and internal and redirect the correct port to your nas IP address

        • Just a dude on the internet Just a dude on the internet

          I am still having the issue with port 51413 showing as closed. I added it as a forwarded port like the others, even in my router pointing to the nas, but no change.

          I’m not sure how to resolve it. Has anyone had any luck?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.