rTorrent + ruTorrent on a Seedbox: The Classic Setup

What rTorrent and ruTorrent Are

rTorrent is a command-line BitTorrent client written in C++. It's tiny, fast, and uses a fraction of the RAM of any GUI client. ruTorrent is the web UI most people pair it with; together they've been the seedbox standard since the late 2000s.

The combination still wins on big libraries. If you're seeding 10,000 torrents, rTorrent does it on resources that would make qBittorrent struggle.

Why Pick rTorrent on a Seedbox?

Three reasons people stick with rTorrent:

• Resource efficiency. Lightest client by a long way. Matters if you're seeding tens of thousands of torrents.
• Stability. Once it's configured it just runs. Years between issues isn't unusual.
• The plugin ecosystem in ruTorrent. RSS, scheduler, ratio rules, IP filters, theme support. Everything's there.

Trade-off: the configuration is via files, not a GUI, and the ruTorrent UI looks like 2010. If that bothers you, qBittorrent is probably the better fit.

Installing rTorrent

Open the Bytesized Panel, find rTorrent in the app catalog, click install. The panel sets up rTorrent itself, ruTorrent for the web UI, the reverse proxy, and a clean HTTPS URL.

Click "Open" to load ruTorrent.

First Login

Web UI uses your panel password by default. Once you're in, ruTorrent doesn't have a separate password layer; everything goes through the panel's auth.

For Sonarr and Radarr integration, they hit the rTorrent XMLRPC endpoint, not the ruTorrent UI. The panel exposes that; check the app settings page for the URL and auth.

ruTorrent Plugins Worth Enabling

ruTorrent's plugins are mostly enabled by default on a Bytesized install. The ones to know:

• RSS. Add feeds and set auto-download rules. Solid alternative to Sonarr if you only need a handful of feeds.
• Scheduler. Time-bound rules: turn off seeding at peak hours, throttle during the day.
• Autotools. Auto-extract archives, auto-move completed torrents.
• Theme. Cosmetic. The dark themes are easier on the eyes.
• DataDir. Move torrent data after import without breaking the seeding state.

Sonarr / Radarr Integration

In Sonarr's Settings > Download Clients > Add > rTorrent:

• Host: internal URL from the panel
• URL Path: typically /RPC2 or whatever the panel's app page shows
• Username / Password: the credentials from the panel

Categories in rTorrent are based on labels. Sonarr will set the label automatically when sending the torrent.

Folder Layout

By default rTorrent writes downloads under ~/files or ~/data depending on how it's been configured. The panel uses the byshlicer convention; check the app settings for the canonical path.

When pairing with Sonarr and Radarr, point them at subfolders inside the rTorrent download path so the import step finds the file where it's expected.

Common Gotchas

Web UI is blank. Almost always a session issue. Refresh hard (Ctrl+Shift+R) and re-login.

Sonarr says "Connection refused." rTorrent's XMLRPC endpoint isn't on a standard port; use the URL shown in the panel, not a guess.

Torrent stuck at "checking." Big torrents take time on first hash check, especially on heavily-seeded slices. Be patient; if it's been hours, restart rTorrent from the panel.

Plugin missing. Older third-party plugins can break with newer ruTorrent versions. Stick with the bundled plugin set unless you're sure a third-party one is current.

Magnet links never resolve. rTorrent's magnet handling is slower than qBittorrent's. Add the .torrent file directly if a magnet's been hanging.

rTorrent vs Alternatives

Quick version, full breakdown in the client comparison guide:

• rTorrent + ruTorrent. Most efficient, dated UI, classic seedbox pick.
• qBittorrent. Modern UI, built-in features, slightly heavier.
• Deluge. In between. Light, plugin-friendly.

FAQ

Is rTorrent free? Yes. Free and open source. ruTorrent too.

Why is it the seedbox standard? Resource efficiency on big libraries. It can seed tens of thousands of torrents on a fraction of the RAM other clients need.

Will it work with Sonarr and Radarr? Yes. Use the XMLRPC endpoint from your panel.

Is the web UI mobile-friendly? Not really. ruTorrent works on a phone but it's clearly built for desktop.

Can I run rTorrent alongside qBittorrent? Technically yes, on different ports. Most people pick one. If you do run both, set very different category names so neither client picks up the other's torrents.

Ready to Set It Up?

Browse Appbox plans, install rTorrent from the panel, and ruTorrent loads from the same one-click setup.