Transmission, without the web page.
The first beta watches Transmission, and it knows Transmission's quirks: a stock install refuses requests from your network with a 403, and Tillarr still recognises it. During the beta, its torrents join the shared queue.
What you see
- Whether it answers, how quickly, and which address answered
- A tap to open its own web page
What's next
During the beta: torrents and stats in the shared Downloads list. Start, stop and remove torrents, set speed limits, and add a torrent.
Connect Transmission
What to have ready when you add it in Tillarr.
- Its address. Usually http://your-server:9091, with /transmission/web/ for its page. Add a remote address too, and Tillarr uses it when home doesn't answer.
- Nothing else. Watching needs no key and no login, so it's free and can't change anything in Transmission. When full support arrives, Tillarr asks for its key.
Good to know
- Transmission's stock allowlist only accepts 127.0.0.1. Add your network, or turn the allowlist off, before connecting.
- A hostname that isn't in Transmission's host whitelist gets a 421.
Behind a sign-in page
If a sign-in page guards Transmission, let /transmission/web/ through so the check can reach it. The remote access guide shows how.
How Tillarr checks Transmission
Without a key, Tillarr asks for /transmission/web/ to see that Transmission is up. Every request goes from your device straight to your server, never through us. Works with Transmission 4.0 and 4.1.
Questions
Why does Transmission answer 403?
Its allowlist accepts only 127.0.0.1 out of the box. Tillarr still recognises Transmission from the answer; add your network to the allowlist to manage it.
Does Transmission send notifications?
No, it only runs scripts. Download news reaches you through Sonarr and Radarr.