Cross-seed with autobrr
If you run qBittorrent, check out qui, our multi-instance qBittorrent WebUI with first party cross-seed support. It integrates directly with autobrr and needs no extra daemon or config; see Cross-seed with qui.
This is meant for advanced users. If you're not familiar with cross-seed already, we suggest you read their documentation before you continue.
Don't expect any support for setting this up. If you need help setting up cross-seed, you need to reach out to them directly.
With this setup you can use autobrr with cross-seed to automatically cross-seed newly announced torrents from indexer Y that matches existing torrents in your torrent client from indexer X.
Install cross-seed
See cross-seed's documentation on how to get started.
Create the cross-seed filter in autobrr
The way this works is you create a filter with a higher priority set than any other filter to make sure every cross-seed match is forwarded to the cross-seed daemon instead of being run through other filters.
-
Get your API key with the following command:
cross-seed api-keyKeep this key at hand since we will need it at step 5 later on. In the rest of this tutorial, we will refer to this as
YOUR_API_KEY. -
Create a filter and name it eg.
cross-seed. -
Select all the indexers you want to use, preferably all of them.
-
Set a really high
priorityto make sure it's always higher than your other filters. -
Go to the
Externaltab, and add a new External filter.- Type:
Webhook - Host:
http://localhost:2468/api/announce - Headers:
x-api-key=YOUR_API_KEY - HTTP Method:
POST - Expected http status:
200 - Data (JSON):
{"name": {{ toRawJson .TorrentName }},"guid": "{{ .TorrentUrl }}","link": "{{ .TorrentUrl }}","tracker": {{ toRawJson .IndexerName }}} - Type:
-
Go to the
Actionstab and create a Test action. This is required for the webhook to work. -
Finally, make sure the filter is enabled and you're all set.
You can set up a Notifiarr or Apprise webhook for cross-seed notifications within the cross-seed config.