Client Login

Connecting ruTorrent to the ***arrs

How-to

Connecting ruTorrent to the *arrs

Radarr, Sonarr, and Lidarr can all add ruTorrent as a download client using the built-in rtorrent client type. The settings you enter depend on which ruTorrent version you’re running.

1. Which version am I running?

We currently run two versions of ruTorrent side by side. The legacy 3.10 build is being phased out, while 5.3 is an installable application from your available applications page. Installing 5.3 removes the legacy version, so you’ll only ever have one active at a time.

Both versions connect over port 443 with Use SSL ticked, through ruTorrent’s HTTPRPC plugin. The main difference is the Host you enter. Because 5.3 uses a local address, it also needs certificate validation relaxed in your *arr app.

VersionHostPortUrl Path
3.10 (legacy)Server hostname443HTTPRPC plugin
5.3 (latest)rutorrent_ + your username (lowercase)443HTTPRPC plugin
→

Not sure which one you have? Check your available applications page. If ruTorrent 5.3 is listed as installed there, use the 5.3 settings below even if you set things up on 3.10 in the past.

2. Add rtorrent as a download client

1

Open the download client settings

This step is the same regardless of which ruTorrent version you’re on.

  1. In your Radarr, Sonarr, or Lidarr instance, go to Settings → Download Clients.
  2. Click the + button to add a new client.
  3. Select rtorrent from the list.

3. ruTorrent 3.10 (legacy)

2

Configure the client Legacy

Version 3.10 runs over port 443 and talks to ruTorrent through the HTTPRPC plugin’s action.php endpoint, using your server’s hostname as the Host.

Namertorrent
EnableYes
Hostnlxxxx.dediseedbox.com
Port443
Use SSLYes — tick the box
Url Path/rutorrent/plugins/httprpc/action.php
Usernameyour-username
Passwordyour-password — reset via “Change Password”

4. ruTorrent 5.3

3

Allow the local address certificate Required

Version 5.3 is reached through a local address (rutorrent_ plus your lowercase username), so your *arr app must be told not to validate the certificate for local addresses. Without this, the connection test will fail.

  1. In Sonarr (and likewise in Radarr or Lidarr), go to Settings → General.
  2. Find Certificate Validation and change it to Disabled for Local Addresses.
  3. Click Save.
4

Configure the client Current

Version 5.3 also runs over port 443 and uses the same HTTPRPC action.php endpoint. The difference is the Host: instead of the server hostname, enter rutorrent_ followed by your username, all in lowercase.

Namertorrent
EnableYes
Hostrutorrent_yourusername — e.g. username David → rutorrent_david
Port443
Use SSLYes — tick the box
Url Path/rutorrent/plugins/httprpc/action.php
Usernameyour-username
Passwordyour-password — reset via “Change Password”
!

For 5.3, the Host is not your server hostname, and it’s not just your username. It’s rutorrent_ followed by your username, all lowercase. For example, if your username is David, the Host is rutorrent_david. Remember to set Certificate Validation to Disabled for Local Addresses first (step 3).

5. Troubleshooting

Unable to connect to download client
Confirm you’re using the correct Host for your ruTorrent version: the server hostname for 3.10, rutorrent_ plus your username in lowercase for 5.3 (e.g. rutorrent_david). Entering just your username, or using capital letters, will fail. Port should be 443 with Use SSL ticked, and the Url Path /rutorrent/plugins/httprpc/action.php on both.
SSL or certificate errors on 5.3
In your *arr app, go to Settings → General, set Certificate Validation to Disabled for Local Addresses, and click Save. This is required when connecting to the local address rutorrent_ plus your lowercase username.
Client tests fine but downloads never appear
Double-check the category/label settings match what the *arr app expects, and that the download path mapping is correct if you’re running Radarr/Sonarr/Lidarr in Docker.
401 or authentication errors
Re-enter your username and password, or reset the password via “Change Password” on your service page.
Worked before, broken after an upgrade
If you recently installed ruTorrent 5.3, change the Host in your *arr download client from the server hostname to rutorrent_ plus your username in lowercase (e.g. rutorrent_david), and set Certificate Validation to Disabled for Local Addresses under Settings → General. Port, Use SSL and Url Path stay the same.
→

Moving off legacy? Since 3.10 is being phased out, we recommend installing ruTorrent 5.3 from your available applications page and updating the Host and Certificate Validation settings in your *arr app ahead of time rather than waiting for it to be removed.

Popular KB Articles