rTorrent
aMuTorrent connects to rTorrent via XML-RPC over HTTP, allowing you to manage BitTorrent downloads.
Requirements
Section titled “Requirements”- rTorrent with XML-RPC enabled over HTTP
- Typically requires a web server (nginx, lighttpd) to expose XML-RPC
Configuration
Section titled “Configuration”Via Settings UI
Section titled “Via Settings UI”- Go to Settings in aMuTorrent
- Expand the rTorrent section
- Enable rTorrent integration
- Configure connection settings:
- Host: rTorrent XML-RPC hostname (e.g.,
localhostorrtorrent) - Port: XML-RPC port (default:
8000) - Path: XML-RPC endpoint path (default:
/RPC2) - Username/Password: If HTTP authentication is required
- Host: rTorrent XML-RPC hostname (e.g.,
Via Environment Variables
Section titled “Via Environment Variables”RTORRENT_ENABLED=trueRTORRENT_HOST=localhostRTORRENT_PORT=8000RTORRENT_PATH=/RPC2RTORRENT_USERNAME=userRTORRENT_PASSWORD=passVia config.json
Section titled “Via config.json”{ "rtorrent": { "enabled": true, "host": "localhost", "port": 8000, "path": "/RPC2", "username": "", "password": "" }}rTorrent Setup
Section titled “rTorrent Setup”Using ruTorrent’s XML-RPC
Section titled “Using ruTorrent’s XML-RPC”If you’re running ruTorrent, XML-RPC is already exposed. Use the same host/port as ruTorrent with path /RPC2.
Standalone rTorrent with nginx
Section titled “Standalone rTorrent with nginx”Add to your nginx configuration:
location /RPC2 { scgi_pass unix:/path/to/rtorrent.sock; include scgi_params;}Or for TCP:
location /RPC2 { scgi_pass 127.0.0.1:5000; include scgi_params;}Docker Compose Example
Section titled “Docker Compose Example”services: rtorrent: image: crazymax/rtorrent-rutorrent:latest container_name: rtorrent ports: - "127.0.0.1:8000:8000" # XML-RPC (localhost only) - "6881:6881" # BitTorrent - "6881:6881/udp" # BitTorrent DHT - "50000:50000" # Incoming connections volumes: - ./data/rTorrent/config:/data - ./data/rTorrent/downloads:/downloads environment: - PUID=1000 - PGID=1000 - TZ=Europe/Rome restart: unless-stopped
amutorrent: image: g0t3nks/amutorrent:latest environment: - RTORRENT_ENABLED=true - RTORRENT_HOST=rtorrent - RTORRENT_PORT=8000 - RTORRENT_PATH=/RPC2 volumes: # Download directories (optional): Required for moving/deleting files - ./data/rTorrent/downloads:/downloads ports: - "4000:4000" restart: unless-stoppedCategories
Section titled “Categories”Categories created in aMuTorrent map to rTorrent labels. When a category has a configured path:
- New downloads with that category are saved to the category path
- Existing downloads (active or completed) can be moved to their category path via the UI
Troubleshooting
Section titled “Troubleshooting”Connection Failed
Section titled “Connection Failed”- Verify rTorrent is running and XML-RPC is accessible
- Test with curl:
curl http://host:port/RPC2 - Check firewall rules between containers/hosts
- Verify username/password if authentication is enabled
Downloads Not Appearing
Section titled “Downloads Not Appearing”- Ensure rTorrent integration is enabled in Settings
- Check the aMuTorrent logs for connection errors
- Verify the XML-RPC path is correct (usually
/RPC2)
Permission Issues
Section titled “Permission Issues”- Ensure aMuTorrent can write to download directories
- Check that rTorrent and aMuTorrent share the same UID/GID in Docker