Remote for Transmission - jgalat/remote-app GitHub Wiki
Connection Setup
This page keeps its original Remote-for-Transmission URL so existing links continue to work. Remote now supports both Transmission and qBittorrent.
Installation
Google Play
Install the app from the Google Play Store.
Building from source
git clone https://github.com/jgalat/remote-app.git
cd remote-app
pnpm install
pnpm build:android:development
Connect a server
Open Settings > Servers > Add Server, then choose Transmission or qBittorrent.
| Field | Description | Transmission default | qBittorrent default |
|---|---|---|---|
| Name | Display name, up to 16 characters | Required | Required |
| Host / IP address | Hostname, domain, or IP of the server | Required | Required |
| Port | Web or RPC port | 9091 |
8080 |
| Path | API path | /transmission/rpc |
Empty |
| SSL/HTTPS | Use HTTPS for the connection | Off | Off |
| Authentication | Send the configured username and password | Off | Off |
| Connection addresses | Ordered LAN, VPN, or public routes to the same server | One primary | Multiple with Pro |
Multiple addresses are useful when the same server is reachable through LAN, VPN, and reverse-proxy routes. Authentication is shared. Remote remembers the last successful address and retries network failures and selected gateway errors in list order; it does not hide invalid credentials by retrying them elsewhere.
Test the connection
Tap Test Primary Address before saving. A successful result confirms that Remote can authenticate and call the selected client API. After saving, open any row under Connection addresses to edit and test it independently.
Common failures include:
- HTTP Error - The endpoint returned an error status
- Invalid credentials - Transmission or qBittorrent rejected authentication
- Unexpected response - The URL reaches a service, but not the expected API
- Timeout or network error - The device could not reach the endpoint
See Troubleshooting for specific fixes.
HTTPS with a user-installed CA
Remote supports HTTPS certificates signed by a CA installed by the Android user. The certificate must contain a Subject Alternative Name matching the hostname or IP used in the connection.