Troubleshooting

Fix Torrento and Torrento Connect issues fast

Troubleshoot qBittorrent, Transmission, Deluge, pairing, remote access, and Android notifications from one page.

This guide turns the current Torrento docs troubleshooting content into a dedicated checklist for the failures people search for most: direct torrent client login problems, unreachable companions, successful pairing with no imported clients, broken remote access, and missing Android alerts.

  • Direct connections depend on a reachable Web UI or RPC interface plus the right host, port, username, and password.
  • Torrento Connect companions expose their local dashboard on port 46901 for pairing, client setup, and diagnostics.
  • If pairing succeeds but nothing imports into Android, add and probe the saved clients on the companion first.
  • Remote access issues should be checked against companion health, diagnostics, and your active Torrento Connect subscription.
Back to DocsConnect Overview
Symptoms

Start with the failure you actually have

The fastest path is usually picking the right layer first: direct client access, companion reachability, remote access, or Android notification delivery.

Torrento cannot reach qBittorrent, Transmission, or Deluge

Most direct Android connection failures come down to Web UI or RPC reachability, wrong credentials, or trying to connect across networks without Torrento Connect.

Check the direct connection list

The Torrento Connect companion dashboard will not load

Start with the companion process, Docker container, or Linux service, then confirm that port 46901 is listening and allowed on your LAN.

Open the companion checklist

Pairing worked, but no clients appear in Android

A paired companion does not import clients automatically until those clients are added and tested on the companion side first.

Review pairing and import checks

Remote access or Android notifications stopped working

Use the Connect health view, companion diagnostics, subscription state, and Android background settings to separate networking issues from delivery issues.

Diagnose remote access and alerts

Direct Connections

Fix direct torrent client connection problems in Torrento

Use this checklist when Torrento on Android cannot log in to qBittorrent, Transmission, or Deluge directly on your local network.

  • Verify that the torrent client's Web UI or RPC interface is enabled and reachable from the device running Torrento.
  • Recheck the host, port, username, and password entered in Torrento against the client's live settings.
  • Make sure your Android device is on the same network as the torrent client unless you are intentionally using Torrento Connect for remote access.
  • Check whether a firewall is blocking the client's Web UI or RPC port.
Common defaults are qBittorrent on 8080, Transmission on 9091, and Deluge WebUI on 8112. Treat them as starting points, not guarantees.

Need the client-specific setup flow?

Go back to the main docs for the direct server setup steps and the supported client reference before changing more than one variable at a time.

Open Docs HubConnect Overview
Companion

Fix a Torrento Connect companion that is not reachable

Use this section when the companion dashboard does not load, pairing never starts, or pairing works but Android still shows no usable clients to import.

  • Verify the companion is running with sudo systemctl status torrento-connect-companion on Linux or by checking your Docker container logs.
  • Ensure port 46901 is listening and allowed through the server firewall if you want to open the dashboard from another device on the same LAN.
  • On firewalld-based systems, allow only your LAN subnet instead of exposing the dashboard broadly.
  • If pairing succeeded but no clients appear in Android, add and test qBittorrent, Transmission, or Deluge from the companion dashboard or with torrento-connect client add plus torrento-connect client probe first.
  • If Android shows a companion update card, follow that update path before chasing deeper networking bugs. Version drift can explain stale or incomplete behavior.
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.0.0/24" port port="46901" protocol="tcp" accept' && sudo firewall-cmd --reload

That rule keeps the dashboard restricted to a local subnet instead of opening it more broadly than necessary.

Need the install or headless companion guide?

Use the platform page that matches the machine running the companion, then come back here if the problem remains after a clean, verified install.

Companion DownloadsDocs HubLinux Install Guide
Remote Access

Fix Torrento Connect remote access when you are away from home

These checks apply when local control works, but remote access through Torrento Connect does not.

  • Confirm your Torrento Connect subscription is active.
  • Check the companion health view or diagnostics page. It should report the companion as online.
  • If the companion is behind a restrictive network, the relay path should still work. Check the companion logs for connectivity errors instead of assuming only direct networking matters.
  • If Android is prompting for a companion update, complete that update first so you are not debugging an already-known version mismatch.

Need the product overview instead of the repair steps?

The Connect overview explains what the companion does, when it stays local, and why you do not need to expose qBittorrent, Transmission, or Deluge directly to the public internet.

Read Connect OverviewDocs Hub
Android Alerts

Fix Torrento notifications that are missing or delayed

If torrent activity is happening but your Android device is not alerting you, check both app-side and system-side delivery rules.

  • Make sure notifications are enabled in Torrento settings and in Android system settings.
  • Ensure the app can run in the background, since some device makers aggressively stop background apps and break timely alert delivery.
  • Verify that Firebase Cloud Messaging is not blocked by your network environment.

Need the broader documentation?

The main docs page covers setup, remote access, Android usage, and the wider feature set in one place.

Open Docs
FAQ

Torrento troubleshooting FAQ for Android and Torrento Connect

These answers match the FAQ structured data on this page so the visible copy and search-facing markup stay aligned.

Why can't Torrento connect to qBittorrent, Transmission, or Deluge?

Verify that the torrent client's Web UI or RPC interface is enabled and reachable, then recheck the host, port, username, and password you entered in Torrento. Local direct connections also require your Android device to be on the same network unless you use Torrento Connect for remote access.

Why is the Torrento Connect companion dashboard not reachable?

Confirm the companion is actually running, then make sure port 46901 is listening and allowed through the server firewall when you open the dashboard from another LAN device. On Linux, check the torrento-connect-companion service; on Docker, inspect the container status and logs.

Pairing succeeded, so why don't my torrent clients appear in Torrento?

After pairing, you still need to add qBittorrent, Transmission, or Deluge on the companion itself and test them there first. If the companion cannot reach those saved clients, Torrento Android will have nothing usable to import.

Why is Torrento Connect remote access not working away from home?

Confirm that your Torrento Connect subscription is active and that the companion health or diagnostics view reports the companion as online. If the network is restrictive, the relay path should still work, so companion logs are the next place to look for connectivity errors.

Why are Torrento notifications not arriving on Android?

Make sure notifications are enabled both inside Torrento and in Android system settings, then confirm the app is allowed to run in the background. Some devices aggressively stop background apps, and some networks can also interfere with Firebase Cloud Messaging delivery.