Jackett – General Configuration Guide

Purpose: Jackett is a secondary indexer manager that acts as a bridge between automation apps (Sonarr, Radarr, etc.) and torrent trackers or Usenet indexers that Prowlarr cannot natively handle. While Prowlarr covers most supported indexers out-of-the-box, Jackett fills the gaps by providing access to additional private and public trackers, ensuring your automation stack has maximum coverage.

Jackett also integrates with Flaresolverr, which allows it to access websites that use anti-bot measures like Cloudflare, expanding the number of indexers you can reliably use.

—

• Secondary Indexer Manager – Jackett is not a replacement for Prowlarr, but a complement. It provides access to additional indexers and passes results back to your automation apps in a standardized format.
• Flaresolverr Integration – Many private trackers or websites use Cloudflare or other anti-bot protections. Flaresolverr is a headless browser service that Jackett uses to bypass these protections automatically, allowing searches and RSS feeds to function reliably.
• API Proxy – Like Prowlarr, Jackett exposes an API endpoint that automation apps can query, making it seamless to integrate into your existing workflow.

—

• Network: Ensure the VM hosting Jackett has stable internet access. If using a VPN, verify that the NIC used can reach both your automation apps and the external indexers.
• Access: Assign a static port (default is <vm-ip>:9117) so your automation apps can consistently connect.
• Authentication: Enable admin login with a strong password. Jackett can be exposed to multiple apps, so securing access is critical.

• Install Flaresolverr on the same VM or a reachable host.
• Configure Jackett to point to the Flaresolverr instance.
• Test indexers that use Cloudflare or similar protections to ensure searches work properly.
• Flaresolverr should run as a background service and restart on boot for consistent operation.

• Use Jackett’s pre-configured indexer templates whenever possible.
• For private trackers, enter credentials or API keys as required.
• Test each indexer after adding to confirm connectivity and Flaresolverr functionality.
• Categorize indexers for easier management, such as “movies” vs “TV.”

• Copy the Jackett API URL for each indexer and add it to your automation apps (Sonarr, Radarr, etc.) as a custom indexer.
• Test each connection to ensure Jackett is responding and returning search results correctly.
• Only use Jackett for indexers that Prowlarr does not natively support to avoid duplication of results.

• RSS Sync Interval: Adjust to avoid overloading indexers or triggering bans on private trackers.
• Search Limits: Limit the number of simultaneous searches to maintain system stability.
• Update Jackett Regularly: Indexer templates are frequently updated. Keeping Jackett current ensures ongoing compatibility.
• Monitor Logs: Jackett logs will indicate failed searches, indexer changes, or Flaresolverr issues.

—

In short, Jackett ensures no indexer gaps remain, allowing your automation stack to function with maximum coverage and reliability. Flaresolverr ensures that protected websites remain accessible, keeping your “set it and forget it” setup truly automated.

—

This page is intentionally general to introduce Jackett concepts and workflow. Detailed per-indexer setup, private tracker authentication, or troubleshooting should be captured in dedicated guides for each indexer or app.