← Directory

Jackett

Jackett is a proxy server that translates search queries from media apps such as Sonarr, Radarr, and Mylar into tracker-site-specific HTTP requests.

  • Downloaders
  • Media Applications
  • Media Servers
  • Tools & Utilities
Jackett is a proxy server that translates search queries from media apps such as Sonarr, Radarr, and Mylar into tracker-site-specific HTTP requests. It parses the HTML responses and returns the results to the requesting software, enabling real-time searches and recent-upload (RSS) feeds. By centralising indexer scraping and translation logic, Jackett removes that maintenance burden from individual media-management applications.

Platform availability

Available on 6 of 9 platforms

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

83/100 Excellent

Maintained
100last commit 6 days ago
Popular
54480 GitHub stars
Easy to install
856 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
480
Open issues
0
Last commit
2026-10-09
Latest release
v0.24.2810-ls53
License
GPL-3.0
Activity
steady

Checked 6 days ago - source: GitHub (linuxserver/docker-jackett)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Open port 9117 for Jackett's website Map the container port to your host as -p 9117:9117 so your browser can reach Jackett's web page. Without this, Jackett may start but you'll likely see a connection error when trying to log in. source
  • Match PUID/PGID to your host user Run id your_user on your server, then set PUID and PGID (the user and group IDs the container runs as) to the numbers it shows. Without it, Jackett may be blocked from saving settings or reading downloaded files. source
  • Save config and download folders Point /config to a real folder you can back up, and /downloads to the folder where Jackett should store downloads. If you lose the config folder, you lose your index accounts and settings, and wrong download paths can cause download problems. source

Fetched 17 days ago - each note links to its source

Alternatives (2)

  • Hatt - This tool allows to search for files through multiple websites, with an intuitive user interface.
  • Prowlarr - Prowlarr is an indexer manager and proxy for the arr suite that centralizes torrent tracker and Usenet indexer configuration.

Checked 14 days ago - source: AlternativeTo

Common questions

How do I make Jackett's web UI reachable from a browser?

Map the container port 9117 to the host as -p 9117:9117 so a browser can reach Jackett's web page. Without this, Jackett may start but you may see a connection error when trying to log in.

What PUID and PGID values should I use to avoid permission problems?

Run id your_user on the host and set PUID and PGID to the user and group IDs it shows. This prevents Jackett from being blocked from saving settings or reading downloaded files.

Which Jackett folders should I keep and back up?

Point /config to a real folder you can back up, because losing it loses your index accounts and settings. Also point /downloads to the folder where Jackett should store downloads to avoid download path problems.

How do I connect another app that supports Jackett as a parser?

Provide your server address and port 9117 along with the API key generated when the Jackett server was created. This is the connection method used in the example for an external parser-based app.

What should I try if Docker Jackett cannot access the network and all indexers fail?

Fetching the latest Docker image or shutting down the container and starting a fresh one may resolve the network access issue. If all Jackett indexers fail the same way, this is a troubleshooting step worth trying.

Answers sourced from github.com, github.com, www.reddit.com

Community

Collected 16 days ago - public community threads