SABnzbd, on your phone.
The first beta watches SABnzbd and reads its version without a key. During the beta its queue joins the shared download list, so a Usenet download sits next to the torrents and the arrs that asked for it.
What you see
- Whether it answers, how quickly, and which address answered
- Its version, read without a key
- A tap to open its own web page
What's next
During the beta: the queue, history and speed in the shared Downloads list. Pause or resume everything or one item, delete, set a speed limit and add an NZB by URL.
Connect SABnzbd
What to have ready when you add it in Tillarr.
- Its address. Usually http://your-server:8080. 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 SABnzbd. When full support arrives, Tillarr asks for its key.
Good to know
- SABnzbd treats a Tailscale address as external, so allow external access for it in SABnzbd's settings.
- Add your remote hostname to SABnzbd's host whitelist, or it refuses the request.
- Use 5.1.3 or later: earlier 5.1 releases had sign-in bypasses.
Behind a sign-in page
If a sign-in page guards SABnzbd, let /api through so the check can reach it. The remote access guide shows how.
How Tillarr checks SABnzbd
Without a key, Tillarr asks for /api?mode=version&output=json to see that SABnzbd is up, and reads its version from the answer. Every request goes from your device straight to your server, never through us. Works with SABnzbd 5.1, with 5.2 checked as it lands.
Questions
Does Tillarr support Usenet?
Yes. SABnzbd and NZBGet join the shared download queue during the beta. Today both are watched by address.
Why does SABnzbd refuse my Tailscale address?
SABnzbd counts Tailscale's 100.64.0.0/10 addresses as external. Set External internet access in SABnzbd's settings to allow them.