Skip to main content

Direct Client Injection

If you use rTorrent, Transmission, Deluge, or qBittorrent, cross-seed can inject the torrents it finds directly into your torrent client. This feature is extremely robust and can be leveraged manually or through automation external to cross-seed.

tip

If you are having issues with injection errors, and it reverting to save, please check our FAQ

Setting up your client​

Arr Users

You need to configure linking or use duplicateCategories: true if you are using qBittorrent or Deluge. This will prevent injected cross seeds from being added to your Arr's import queue.

rTorrent setup​

cross-seed will inject torrents into rTorrent with a cross-seed label.

  1. Edit your config file:
    1. Set your action option to inject.
    2. Set your rtorrentRpcUrl option. It should look like an http url that looks like http://user:pass@localhost:8080/rutorrent/RPC2 (if you have ruTorrent installed). See the reference for more details.
  2. Start or restart cross-seed. The logs at startup will tell you if cross-seed was able to connect to rTorrent.
Docker

In order for cross-seed to prove to rTorrent that a torrent is completed, it must check the modification timestamps of all the torrent's files.

Make sure that your cross-seed container has read access to the data directories of your torrents, mapped to the same path as rTorrent.

qBittorrent setup​

  1. Edit your config file:
    1. Set your action option to inject.
    2. Set your qbittorrentUrl option. It should look like an http url that looks like http://user:pass@localhost:8080/ See the reference for more details.
  2. Start or restart cross-seed. The logs at startup will tell you if cross-seed was able to connect to qBittorrent.

Transmission setup​

  1. Edit your config file:
    1. Set your action option to inject.
    2. Set your transmissionRpcUrl option. It should look like an http url that looks like http://user:pass@localhost:9091/transmission/rpc
  2. Start or restart cross-seed. The logs at startup will tell you if cross-seed was able to connect to Transmission.

Deluge setup​

  1. Edit your config file:
    1. Set your action option to inject.
    2. Set your delugeRpcUrl option. It should look like an http url that looks like http://:pass@localhost:8112/json (the colon before pass is intentional)
  2. Start or restart cross-seed. The logs at startup will tell you if cross-seed was able to connect to Deluge.

Manual or Scheduled Injection​

danger

cross-seed is the only program that understands how to properly link and inject its partial and seasonFromEpisodes matches. Other programs, like autotorrent, will not work. You do not need to do anything with torrents saved to outputDir—cross-seed will handle them unless the torrent is stalled.

DO NOT USE outputDir AS A WATCH FOLDER FOR YOUR TORRENT CLIENT!

In v6, cross-seed has the ability to add .torrent files for injection directly. You can either opt to wait for the hourly cadence, or alternatively run the cross-seed inject command to attempt injection for .torrent files in your outputDir. You can alternatively use cross-seed inject --inject-dir /path/to/folder to specify another directory.

For torrent files being injected manually, if using flatLinking: false will require a [mediatype][tracker] prefix (where tracker is the name corresponding to that tracker's linkDir folder) in order to inject within your existing folder structure.

tip

To achieve optimal injection behavior, adding the prefix [mediatype][tracker-name] as you would normally see it in outputDir when saving the torrent file is recommended.

Current "mediatypes" support are episode, pack, movie, anime, video, audio, book, and unknown.

This is the same format in which cross-seed normally saves .torrent files. If you do not specify both of these parameters, cross-seed will link the torrents into the UnknownTracker directory for you, and will require your intervention to sort them if you wish to do so.

Using this command or utilizing the injection hourly cadence will perform minimal filtering on injection attempts. This means there is the possibility of slightly increased chance of false-positives with .torrent files you add for injection. All torrent files saved by cross-seed for retrying have already been filtered for matching.

If the .torrent files follow the naming format above, they will be elligible for cleanup if they fall into one of these categories:

  • The torrent is in client and complete (successful injection or already exists)
  • The torrent has no matches (source torrent/data was likely removed)
  • The torrent matches your blocklist

Stalled torrents (either the cross seeded torrent or it's source) will require your intervention before cross-seed will remove the .torrent file. You will need to remove these torrents from your client and the .torrent file from outputDir. If you wish to keep them in client, only remove their .torrent file from outputDir.

tip

You can find more information about this feature in the v6 migration guide.