Docker Guide

Torrento Connect Docker setup for qBittorrent, Transmission, and Deluge

Run the official Torrento Connect Docker image on a NAS, Raspberry Pi, Docker host, or homelab server, then pair it from Torrento on Android so you can import qBittorrent, Transmission, or Deluge without exposing their Web UI directly to the public internet.

Current companion release: 1.2.25.

Companion DownloadsBack to Docs

Install Torrento Connect with Docker or Docker Compose

The Torrento Connect companion ships as a multi-architecture Docker image for amd64 and arm64, so it works well on NAS devices, Raspberry Pi systems, and container-first home servers.

docker run

Start the companion with a named data volume and the local Web UI port:

docker run -d \
  --name torrento-connect \
  --restart unless-stopped \
  -p 46901:46901 \
  -v torrento-connect-data:/data \
  torrentoapp/torrento-connect:latest

docker compose

Create a docker-compose.yml like this:

services:
  torrento-connect:
    image: torrentoapp/torrento-connect:latest
    container_name: torrento-connect
    restart: unless-stopped
    ports:
      - "46901:46901"
    volumes:
      - torrento-connect-data:/data

volumes:
  torrento-connect-data:

Then start it:

docker compose up -d

What this setup does

  • Pulls the official torrentoapp/torrento-connect image from Docker Hub
  • Persists companion state in a Docker volume mounted at /data
  • Exposes the local pairing and dashboard UI on port 46901
Networking note: if qBittorrent, Transmission, or Deluge lives elsewhere on your LAN, host networking is often the simplest path. Replace the ports section with network_mode: host in your compose file when that fits your Docker host.
Client hostnames:if the torrent client runs in another Docker container on the same bridge network, use that container or service name as the host in Torrento Connect. If it runs on another device, use that machine's LAN IP or hostname instead.

Open the Docker Web UI and pair from Torrento Android

After the container starts, open the companion Web UI in a normal browser at http://localhost:46901 on the Docker host, or http://<host-ip>:46901 from another device on the same LAN.

Use the host machine address, not a shell inside the container. You do not need to docker exec into the companion just to pair it or add clients.

Step 1.1
The Docker companion opens on the same local Web UI used for pairing, client setup, and diagnostics.

Pairing flow

  1. In the Docker Web UI, click Start Pairing.
  2. A one-time code appears together with a QR code and phone link.
  3. In Torrento on Android, open Connect and tap Pair a companion, or scan the QR code so the app opens with the code already attached.
  4. Approve the pairing, then return to the companion dashboard.
  5. Add and test your torrent clients on the companion before you import them into the Android app.
Step 2.1
After Start Pairing, the Docker Web UI shows the pairing code, QR code, and phone link in one place.
Android Approval
On Android, approve the companion from Torrento > Connect, or let the QR code open the same flow with the pairing code already attached.
Step 2.3
After pairing succeeds, the Docker companion dashboard is where you save, test, and manage torrent clients before importing them into Torrento.
LAN access: if you want to open the dashboard from another device on your network, make sure the Docker host firewall allows inbound TCP 46901.

Add qBittorrent, Transmission, or Deluge to the Docker companion

Torrento Android approves pairing and imports the saved clients, but the Docker companion is where the torrent-client host, port, username, and password are stored and tested.

Use the same Web UI or RPC credentials your torrent client already uses, then import the tested client into Torrento from the Android Connect screen.

Typical local values

  • qBittorrent: localhost and port 8080 when qBittorrent runs on the same machine as the companion
  • Transmission: localhost and port 9091 when Transmission runs on the same machine
  • Deluge: localhost and port 8112 when Deluge WebUI runs on the same machine
Same credentials, different place: the companion keeps the client connection details on the companion side. After the connection tests successfully there, the Android app can import that client with Add to Torrento.
Security: pairing uses X25519 key exchange and companion keys are generated locally on the device that runs Torrento Connect.

Update a Torrento Connect Docker container

Torrento Android compares each paired Docker companion against the latest published companion release. If an update is available, the companion card in the app links back to the Docker update path.

Pull the latest image, then recreate the container so it starts on the newest published build:

docker pull torrentoapp/torrento-connect:latest
docker compose up -d
Version tracking:the app and companion dashboard now rely on the companion's embedded build version. Older installs that still reported latest or dev should be updated once so future checks stay accurate.

Docker setup FAQ

These answers mirror the Docker setup guidance on this page and cover the most common Torrento Connect container questions.

Can I run Torrento Connect in Docker on a NAS, Raspberry Pi, or home server?

Yes. The official Torrento Connect Docker image supports amd64 and arm64, so it fits NAS devices, Raspberry Pi systems, and homelab servers well.

Which address should I open after the Docker container starts?

Open the companion Web UI on the Docker host itself at http://localhost:46901, or use http://<host-ip>:46901 from another device on the same LAN.

Do I need to expose qBittorrent, Transmission, or Deluge directly to the internet?

No. Torrento Connect is the remote-access layer. Pair the companion once, save and test the torrent client on the companion side, then use Torrento Android through Connect instead of publishing the torrent client Web UI directly.

What host should I use when the torrent client runs in another container?

If the torrent client runs in another Docker container on the same bridge network, use that container or service name as the host. If it runs on another machine, use that machine's LAN IP or hostname instead.

How do I update a Torrento Connect Docker install?

Pull the latest torrentoapp/torrento-connect image, then recreate the container with docker compose up -d so it starts on the latest published companion build.

Continue with Torrento Connect

Need another install path or the full docs index?

Use the downloads page for the latest companion options, or return to the documentation hub for Linux, macOS, pairing, troubleshooting, and platform-specific update guides.

Go to DownloadsBack to DocsConnect Overview