Trackers settings
Use Settings → Trackers to enable supported tracker entries and configure only the fields advertised by the current tracker catalog.
Add a tracker
- Choose a tracker under Entries and select Add entry.
- Open its card and enter the required activation credential, such as an API key, passkey, announce URL, or account credentials.
- Configure only the upload options you understand.
- Select Save.
- If the tracker uses managed cookies or login, continue under Tracker Auth. For browser cookies, follow the Firefox export and import walkthrough.
Adding an empty card does not make an unusable tracker ready. upbrr determines configured state from tracker-owned activation fields supplied by the backend catalog.
Defaults and priority
| Control | Effect |
|---|---|
| Default trackers | Preselects configured trackers when starting a release. |
| Preferred tracker data source | Moves that tracker to the front of tracker-data lookup and qBittorrent tracker priority when present. |
Defaults do not bypass workflow eligibility, auth, duplicate checks, validation, or manual review.
Common tracker fields
Each tracker shows a different subset.
| Field family | Purpose |
|---|---|
| API key, passkey, announce URL | Authenticates tracker API, upload, or announce operations as required by that tracker. |
| Username, password, OTP URI | Supports tracker-owned login or automatic relogin. Managed cookie state is shown separately. |
| Anonymous upload, Opt into moderation queue, Upload as draft | Sets tracker-specific upload flags where supported. |
| Preferred image host for this tracker | Chooses an eligible host for that tracker instead of relying only on global priority. |
| Client receiving this tracker's torrents | Overrides global client handling for torrents registered by that tracker. |
| Link staging subfolder | Names the tracker staging directory when torrent-client linking is enabled. |
| Custom tracker icon URL | Overrides the tracker icon source used by the Web UI. |
| Skip when torrent regeneration is needed | Omits the tracker when preparation must generate new torrent data. |
| Client injection delay (seconds) | Overrides the global post-upload client-injection delay for that tracker. |
Other fields are tracker-owned. Their labels and defaults come from the running backend, not a universal schema. See Trackers for support boundaries.
Anonymous uploads
Anonymous upload requests anonymous attribution where the adapter supports it. Show group when anonymous, when shown for a tracker, requests release-group visibility only for an anonymous upload. An unchecked preference does not guarantee that the tracker's account default is disabled. These controls do not guarantee privacy from the tracker.
A per-upload anonymity choice overrides the stored Anonymous upload setting. Show group when anonymous continues to use its stored setting. When an upgrade changes the tracker review contract, unfinished reviews are rebuilt before their upload authority is reused. Compatible prepared source facts remain available, confirmed uploads are not repeated, and uncertain outcomes remain available for reconciliation.
Group policy lists
Every tracker card provides three independent comma-separated release-group lists. Configure each tracker separately; a group listed for one tracker has no effect on another.
| Field | Effect for a matching incoming group |
|---|---|
| Same-group duplicate-check groups | Ignores confirmed duplicate candidates from other groups. Same-group candidates, exact duplicates, and candidates whose group cannot be determined still receive normal duplicate handling. |
| Personal release groups | Selects the tracker API's personal-release option when that API supports one. An explicit Personal Release choice on the upload overrides this configured default, including an explicit false. |
| Internal release groups | Selects the tracker API's internal option when supported and applies the same-group duplicate behavior described above. |
Enter tags without the conventional leading -, for example GRP, OTHER. upbrr trims whitespace, removes one accidental leading hyphen, and removes repeated entries case-insensitively. Matching uses the complete group tag; wildcards and partial matches are not supported.
YAML accepts either a comma-separated value or a sequence:
trackers:
"<tracker-id>":
dupe_bypass_groups: GRP, OTHER
personal_release_groups:
- GRP
internal_groups: GRP
JSON uses arrays with the catalog field names DupeBypassGroups, PersonalReleaseGroups, and InternalGroups.
The older per-tracker Internal boolean is retained only so existing configuration can be read and exported. It no longer enables internal handling. Add the relevant tags to Internal release groups; a list match works even when the legacy value is false.
Remove a tracker
Remove resets the entry to catalog defaults, hides its card, and removes its default and preferred-source selections. Select Save to persist those changes. Unsupported preserved entries appear separately because no current implementation can use them; delete them only when you no longer need their retained config.
Tracker credentials are secrets. Leave [REDACTED] unchanged to preserve a value. After any tracker change, check Tracker Auth and run Dry Run before submission.