Remote — Torrent Manager

qBittorrent / Android remote

qBittorrent remote control for Android.

Control qBittorrent on your seedbox, NAS, Raspberry Pi, Docker host, or home server through its Web API.

Get it on Google Play
Client
qBittorrent
Connection
Web API
Default
:8080

01 / Direct control

Built for your server.

Remote uses qBittorrent's Web API directly. It gives the Web UI controls a phone-first interface without routing your server traffic or credentials through a Remote-owned backend.

  • Add magnet links and .torrent files from Android
  • Start, pause, queue, rename, move, and remove torrents
  • Inspect files, priorities, trackers, peers, share limits, and ETA
  • Control bandwidth, alternative limits, queues, and peer discovery

02 / Connection guide

Connect in four steps.

  1. 01

    Enable the Web UI

    In qBittorrent, open Tools, Options, then Web UI and enable Web User Interface (Remote control).

  2. 02

    Choose the address

    The common Web UI port is 8080. Publish that port for Docker and confirm that the Android device can reach the host.

  3. 03

    Secure the login

    Configure a username and strong password. Review qBittorrent's host-header, CSRF, and authentication bypass settings before allowing remote access.

  4. 04

    Add it in Remote

    Open Settings, choose Add Server, select qBittorrent, enter the Web UI address and credentials, leave the path empty unless a proxy adds one, then test before saving.

03 / If it cannot connect

Check the route first.

Web UI disabled
The desktop interface can work while remote access is still disabled. Confirm that Web User Interface (Remote control) is enabled.
Wrong path
A direct qBittorrent Web UI normally uses an empty path. Add a path only when your reverse proxy serves qBittorrent below one.
Host or CSRF block
qBittorrent security settings may reject an unfamiliar hostname or reverse-proxy configuration even when the port is reachable.
Not reachable
Prefer WireGuard, Tailscale, or a carefully configured HTTPS reverse proxy for access outside your LAN. Avoid publishing a weakly protected Web UI directly.

Need the complete guide? Read the qBittorrent documentation. Already use Transmission? See the Transmission guide.