Skip to content

Cardigann Indexers

Mydia includes built-in Cardigann indexer support, allowing direct indexer connections without Prowlarr or Jackett.

Public indexers are covered, private ones are not

Mydia's Cardigann engine is tested against public trackers, which are the ones it handles well. Private and semi-private trackers need a login, and several login mechanisms (CAPTCHA, selector-derived inputs, separate submit paths) are not implemented. Expect those to fail. If you hit a problem, please report it on GitHub.

Cardigann is the community indexer definition format from Jackett, also used by Prowlarr. Mydia reads those definitions natively, so you can point it at trackers without running a separate indexer manager.

For why Mydia ships its own engine and what that trades away, see Why Mydia ships its own indexer implementation. The short version: use Prowlarr or Jackett when reliability matters more than running fewer services.

Enabling Cardigann

Cardigann is enabled by default:

ENABLE_CARDIGANN=true

To disable:

ENABLE_CARDIGANN=false

Supported Indexers

Mydia syncs the full upstream definition catalogue. Coverage is strongest for public trackers.

Covered by regression tests:

These indexers have captured responses in the test suite, so their parsing is verified on every build.

  • 1337x
  • blueroms
  • EZTV
  • KickassTorrents
  • LimeTorrents
  • MagnetDownload
  • Nyaa.si
  • ShowRSS
  • The Pirate Bay
  • TorrentGalaxy (clone)
  • TorrentLT
  • YTS

Everything else:

The remaining definitions are included and may well work, but nothing pins their behaviour, so an upstream site change can break them silently. Private trackers in particular are likely to fail at login.

To see what the engine actually supports against the current upstream catalogue, run the compatibility report:

mix mydia.cardigann_compat --type public

It lists, per unsupported feature, how many definitions that feature blocks.

Dead and moved domains

Public trackers rotate domains often. Mydia probes every link a definition ships, including its historical ones, picks the first that responds, and stores it. If that host later stops answering, a search transparently fails over to the next candidate and remembers the new one. No configuration is involved.

Configuration

Adding a Cardigann Indexer

  1. Navigate to Admin > Configuration, then the Indexers tab
  2. Click Add Indexer
  3. Select the indexer from the Cardigann list
  4. Enter required credentials (if applicable)
  5. Test and save

Indexer Settings

Each indexer may have specific settings:

  • Username/Password
  • API Key
  • Cookie authentication
  • Site-specific options

Refer to the indexer's requirements in the Admin UI.

FlareSolverr Integration

Some indexer sites are protected by Cloudflare or similar anti-bot services. You can use FlareSolverr to bypass these challenges automatically.

Setup

  1. Run a FlareSolverr instance (e.g., via Docker)
  2. Configure the following environment variables:
FLARESOLVERR_URL=http://flaresolverr:8191
# FLARESOLVERR_ENABLED is auto-enabled when URL is set
# FLARESOLVERR_TIMEOUT=60000
# FLARESOLVERR_MAX_TIMEOUT=120000

See Environment Variables for the full reference.

Limitations

Known Issues

  • Some indexers may not parse results correctly
  • Authentication may fail on some sites
  • Rate limiting varies by indexer
  • CAPTCHA challenges not supported

Troubleshooting

Search Returns No Results

  1. Test the indexer connection
  2. Check if the site is accessible
  3. Verify credentials if required
  4. Check application logs for errors

Authentication Errors

  1. Verify credentials are correct
  2. Some sites require manual cookie refresh
  3. Check if site requires 2FA (not supported)

Rate Limiting

  1. Reduce search frequency
  2. Add delay between requests
  3. Consider using fewer indexers

Reporting Issues

When reporting Cardigann issues:

  1. Include the indexer name
  2. Describe the expected vs. actual behavior
  3. Include relevant log entries
  4. Specify if it works with Prowlarr/Jackett

Next Steps