Indexers

Torsher ships with no sources. It finds releases through Torznab indexers that you run and fill yourself: any Torznab indexer works, for example Prowlarr or Jackett. Connect a manager once, and Torsher picks up all its indexers; when you change them in the manager, sync it in the panel.

What you'll get

An indexer manager connected to Torsher, and releases appearing when you select Watch.

Before you start

• Torsher is running. See Docker Compose.
• You know which sources you are allowed to use. Torsher does not include or recommend any.

Option A: Prowlarr next to Torsher

The install file already has Prowlarr as an optional service. Skip to Option B if you already run Prowlarr or Jackett.

1. Start it in the folder with docker-compose.yml:

   docker compose --profile prowlarr up -d

2. Open http://<server-address>:9696. On the first visit Prowlarr may ask you to set up its own sign-in.

3. In Prowlarr, open Indexers and add the indexers you are allowed to use. Prowlarr starts empty.

4. Copy the API key from Settings → General → API Key in Prowlarr.

5. In the Torsher setup wizard, the Sources step finds Prowlarr at http://prowlarr:9696 by itself. Paste the API key and select Connect.

Already past the wizard? Use Option B with the address http://prowlarr:9696.

Option B: a manager you already run

1. Find the API key:

   • Prowlarr: Settings → General → API Key;
   • Jackett: the API Key field at the top of the dashboard.

2. In the Torsher panel, open Sources and select Import from Prowlarr or Jackett.

3. Choose the manager and enter the address and the API key.

   The address is how the Torsher server reaches the manager, not your computer:

   Where the manager runs	Address
   In the same docker-compose.yml	http://prowlarr:9696 or http://jackett:9117
   On the same machine, outside Compose	http://<server-address>:9696 or http://<server-address>:9117
   On another machine	http://<that-machine-address>:9696 or http://<that-machine-address>:9117

   For Jackett you can paste the address straight from your browser, such as http://<server-address>:9117/UI/Dashboard, or the Torznab feed address Jackett copies for an indexer: Torsher keeps the part before /UI or /api. If Jackett runs under a base path, it stays in the address: http://<server-address>:9117/jackett.

   For Prowlarr you can paste the address straight from your browser on any Prowlarr page, such as http://<server-address>:9696/settings/general, or an indexer's Torznab feed address: Torsher keeps the part before the page or /api. If Prowlarr runs under a URL base, it stays in the address: http://<server-address>:9696/prowlarr.

4. Select Import. Torsher adds every indexer of the manager. Jackett hands over only the indexers you have configured in it; with none, Torsher connects the manager and adds nothing until you configure indexers in Jackett and sync.

Torsher doesn't watch the manager by itself. When you add or remove indexers there, open Sources and use the sync button on the manager's card: new indexers are added, and ones gone from the manager are marked rather than deleted.

Option C: one Torznab indexer

For an indexer that isn't in a manager, open Sources, select Add manually and enter its Torznab address and API key. The server checks the indexer before saving it.

Releases in other languages

Torsher reads release titles in English and Russian, including season and episode ranges, quality, and voice-over studios and markers. Indexers with Russian-language releases work as well as English ones: the showcase shows the voice-over of each release and filters by it.

Check

Open any title on the TV and select Watch. The Sources screen lists releases from your indexers. Sources in the panel shows each indexer with its status.

If something went wrong

• Prowlarr and Jackett not found. The manager runs at another address or port: connect it by address as in Option B.
• The import fails. Check the address from the Torsher server's point of view and the API key. A localhost address points at the Torsher container itself, not at your machine.
• Jackett runs outside Docker and the server can't reach it. On Windows and macOS Jackett accepts only connections from the same computer by default. In the Jackett dashboard, turn on External access and select Apply server settings.
• The import adds no indexers. The manager has none configured. Add indexers in it, then use the sync button on the manager's card.
• Some indexers are not responding. The Sources screen says how many didn't answer; the others are searched anyway. Check them in the manager. If the server can't reach a site directly, add a route through your proxy in Network.

Next

TMDB key, if the catalog is empty, or Connect a device.