Add Remote Torrent

Add Remote Torrent

Add Remote Torrent is a browser extension for power users who manage remote file-transfer clients. It streamlines adding new transfers (via magnet links or .torrent file URLs) to various client WebUIs. It supports multiple server profiles, giving you a centralized experience directly from your browser. Privacy and security: all server configurations are stored locally on your device and are never transmitted to external servers. It also works with private trackers by fetching the .torrent file content in the browser (with your session cookies) before sending it to your client when needed. Key features: - Add via magnet links or .torrent URLs - Multiple server profiles (different clients / different seedboxes) - Right-click context menu “send to…” per server - Optional on-page link catching / quick add - Per-server defaults (tags/categories/directory/paused; varies by client) - URL-based rules to auto-select a server by site Reporting issues: If you encounter a bug, please open an issue on GitHub: https://github.com/jgkme/Add-Remote-Torrent/issues Please include: - Extension version - Torrent client name + version - Steps to reproduce (what you did / expected / what happened) - Exact error text from the popup under “Last Action” For deeper logs: - Options page → Debug & Log Settings → enable content-script + background-script logs - Reproduce the issue - Options page → Inspect → Console → copy relevant lines - Please remove sensitive info (passwords/tokens/IPs) before posting Recent updates: v0.4.40 (2026-05-12): Fix (qBittorrent): Accept successful auth/login with an empty body or HTTP 204 (Web API 5.2+), not only legacy Ok. text—fixes false “connection failed / CSRF” errors when username and password are correct. v0.4.39 (2026-05-13) Fix (qBittorrent): Cookie-based Web UI login is now tracked per server profile instead of one global session. After logging into one qBittorrent server, calls to another profile no longer skipped auth/login, which previously caused HTTP 401 on the API and confusing messages about needing a Web API key (common with multiple seedboxes and qBittorrent 5.2+). Fix (qBittorrent): Refined unauthorized and connection-test wording so users check username/password and CSRF first; the optional Web API key (5.2+) is described only as a fallback when cookie access still cannot reach the API. Build: Generated release artifacts for v0.4.39. - v0.4.38 (2026-05-08): Deluge — apply custom label/category after adding (Label plugin); create missing label; retry for Deluge 2.x timing. - v0.4.37 (2026-05-05): qBittorrent — Web API 2.14+ torrents/add JSON responses (incl. 202/409) with legacy “Ok.” fallback; optional Web API key (Bearer); clearer auth vs network errors; startup status checks; packaging/signing fixes. Supports qBittorrent 5.2. Full changelog: https://github.com/jgkme/Add-Remote-Torrent/releases