Repository navigation
Settings Server
The Server tab (labeled rTorrent Server in the sidebar) connects the Nebulae desktop app to a headless nebulae-server instance running alongside rTorrent on a remote machine — such as an Unraid box, TrueNAS, or a Docker container.
| Setting | Description |
|---|---|
| Drive torrents on a Nebulae Server (rtorrent) instead of locally | Switches the engine from the local embedded Transmission daemon to the remote rTorrent bridge. The change applies the next time Nebulae restarts. |
| Server address | Full URL of the nebulae-server bridge, including port (e.g., http://tower.local:9174). |
| API token | The NEBULAE_SERVER_TOKEN shared secret configured on the server side. Stored securely. |
Click Test connection to verify the server address and token are reachable. A green "Connected" message confirms a successful handshake; a red message describes the failure.
Important
The engine choice takes effect only after Nebulae restarts. Apply your settings and restart the application to switch engines.
Note
The server bridge currently serves plain HTTP on your LAN. Use a trusted private network or put a TLS-terminating reverse proxy (e.g., nginx) in front for external access.
Some features are unavailable when Nebulae is connected to a remote rTorrent server:
- Per-file download priority
- Torrent rename
- Category management
- Super-Seeding toggle
These options will indicate their unavailability in the UI when remote mode is active.
Next: Settings — Media · Previous: Settings — Web UI