Troubleshooting

Connection issues

Using Test Connection

The Test Connection button (on both the server and Search configuration screens) is the best starting point for diagnosing issues. It reports specific error types:

Result	Meaning	What to check
Connected	Everything is working	Nothing, you are good
HTTP Error: ...	The server returned an error HTTP status	Verify the host, port, and path are correct. Check that the Transmission daemon is running.
Unexpected response (HTTP ...)	The server responded but it is not a valid Transmission RPC response	The host and port are likely correct, but the path is wrong. Verify the RPC path (default: /transmission/rpc). This can also happen if a reverse proxy is intercepting the request.
Transmission Error: ...	Connected to Transmission but it returned an error	Usually an authentication problem. Check your username and password.
Error: ...	Could not connect to the server at all	Network issue. Check the sections below.

Common connection problems

Wrong port The default Transmission RPC port is 9091. If you changed it in settings.json, make sure the app matches. If using SSL/HTTPS with a reverse proxy, you likely need port 443 or your custom proxy port.

Wrong path The default RPC path is /transmission/rpc. If you changed rpc-url in Transmission's settings.json, the path in the app must match. The app's path field corresponds to {rpc-url}rpc.

SSL/HTTPS issues

• Make sure the Use SSL/HTTPS toggle matches your server setup
• If using a self-signed certificate, see the SSL section in Connection Setup
• If using a reverse proxy, ensure it is configured to forward requests to Transmission's RPC port

Authentication errors

• Verify rpc-authentication-required is true in Transmission's settings.json
• Check that the username and password match
• Transmission hashes the password in settings.json after first startup, so you cannot read it back from the file

Server not reachable

• Verify the Transmission daemon is running on the server
• If connecting over the local network, ensure your phone is on the same network
• If connecting remotely, verify port forwarding, VPN, or reverse proxy is configured correctly
• Check firewall rules on the server

IP whitelist blocking connections If rpc-whitelist-enabled is true in Transmission's settings.json, only whitelisted IPs can connect. Either add your IP to rpc-whitelist or set rpc-whitelist-enabled to false.

Search connection issues

If the Search test connection fails:

• Verify your Jackett or Prowlarr instance is running and accessible
• Check the host, port, and API key
• Make sure the default path has not been changed unless you have a custom setup
• If Jackett/Prowlarr is behind a reverse proxy or on a different network than your phone, the same network reachability rules apply as for Transmission

Torrents not downloading

If torrents are added but not downloading:

• Check if the torrent is in a Stopped state. Start it manually or enable Start Automatically when adding.
• Check the download queue size in Server Configuration. If the queue is full, torrents wait until a slot opens.
• Verify the download directory exists and is writable by the Transmission daemon.
• Check tracker status in the Torrent Details Trackers tab for errors.
• Try Reannounce to refresh tracker connections.