NZBGet, managed from your phone.
Tillarr follows the maintained NZBGet, the nzbgetcom fork, since the original project was archived in 2022. The first beta watches it; during the beta its queue joins the shared download list.
NZBGetChecking…Up
AnsweredChecking…Home address · 18 ms
CheckedChecking…Just now
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: the queue, status and history. Pause or resume everything or one item, delete, set a rate limit and add an NZB by URL.
Connect NZBGet
What to have ready when you add it in Tillarr.
- Its address. Usually http://your-server:6789. 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 NZBGet. When full support arrives, Tillarr asks for its key.
Good to know
- Still on NZBGet's default login? Change it before you reach NZBGet from outside your network.
- An add-only NZBGet user can't read the queue, so give Tillarr a user that can.
- Deleting a group in NZBGet deletes its files too, so Tillarr asks first.
How Tillarr checks NZBGet
Without a key, Tillarr asks for / to see that NZBGet is up. Every request goes from your device straight to your server, never through us. Works with NZBGet 26 (nzbgetcom).
Questions
Which NZBGet does Tillarr support?
The nzbgetcom fork, which is the maintained one. The original NZBGet was archived in 2022.
Does NZBGet send notifications?
Not by itself; it only runs extension scripts. Download news reaches you through Sonarr and Radarr instead.