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.
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.
They connect differently because of compatibility issues between the *arrs and ruTorrent’s HTTPRPC plugin.
| Version | Port | Connects via |
|---|---|---|
| 3.10 (legacy) | 443 | HTTPRPC plugin |
| 5.3 (latest) | Custom port | RPC2 |
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.
This step is the same regardless of which ruTorrent version you’re on.
Version 3.10 runs over port 443 and talks to ruTorrent through the HTTPRPC plugin’s action.php endpoint.
| Name | rtorrent |
| Enable | Yes |
| Host | nlxxxx.dediseedbox.com |
| Port | 443 |
| Url Path | /rutorrent/plugins/httprpc/action.php |
| Username | your-username |
| Password | your-password — reset via “Change Password” |
Version 5.3 runs on its own custom port and connects over RPC2 instead of the HTTPRPC plugin.
| Name | rtorrent |
| Enable | Yes |
| Host | nlxxxx.dediseedbox.com |
| Port | custom port — taken from the URL you use to access ruTorrent |
| Url Path | RPC2 |
| Username | your-username |
| Password | your-password — reset via “Change Password” |
The port for 5.3 is not 443. Check the address bar while you have ruTorrent open in your browser the number after the colon in the URL is the port you need here.
Moving off legacy? Since 3.10 is being phased out, we recommend installing ruTorrent 5.3 from your available applications page and switching your *arr download client settings over ahead of time rather than waiting for it to be removed.
