
Jackett
API translator for private torrent trackers
Jackett works as a proxy server: it translates queries from apps (Sonarr, Radarr, Lidarr, etc.) into tracker-site-specific HTTP queries, parses the HTML or JSON response, and then sends results back to the requesting software. This allows for getting recent uploads (like RSS) and performing searches. Jackett is a single repository of maintained indexer scraping & translation logic—removing the burden from other apps. QuickBox Pro installs Jackett from the latest GitHub release at /opt/username/Jackett with automatic nginx reverse proxy configuration.
🔗 Tracker Support
Support for 500+ torrent trackers including private trackers requiring authentication and cookies
🔄 API Translation
Translates queries from *arr apps into tracker-specific formats and parses responses back into standard format
🔍 Manual Search
Built-in search interface for testing tracker connections and finding specific releases manually
⚙️ Custom Indexers
Add custom indexers using Cardigann definition format for sites not officially supported
📊 Statistics
Track indexer success rates, response times, and search performance from unified dashboard
🔐 Credential Management
Secure storage of tracker credentials and API keys with encryption support
Prowlarr vs Jackett
Prowlarr is the modern alternative to Jackett with enhanced features and *arr integration. Consider using Prowlarr for new installations. Jackett remains useful for trackers not yet supported by Prowlarr or when using non-*arr applications.
Installation
Symptoms
- QuickBox Pro v3 installed and configured
- At least one *arr app installed (Sonarr, Radarr, Lidarr, or Readarr)
- Private tracker accounts requiring API access
- User account created on the server
Resolution
- Use QuickBox's qb command for installation
- Automatic configuration with reverse proxy
- Per-user installation with isolated credentials
- Latest release from GitHub automatically installed
Basic Installation
Install Jackett for a specific user:
qb install jackett -u usernameCLI Commands
| Command | Description |
|---|---|
qb install jackett -u username | Install Jackett with automatic configuration |
qb reinstall jackett -u username | Reinstall Jackett (preserves configuration) |
qb update jackett -u username | Update to latest GitHub release |
qb remove jackett -u username | Remove Jackett and clean up files |
qb help jackett | Display comprehensive help information |
Automatic Port Assignment
QuickBox automatically assigns ports starting at 9117 (auto-incremented per user). Find your assigned port in the QuickBox dashboard or in ~/.config/Jackett/ServerConfig.json.
Automatic Updates
Jackett releases are fetched automatically from the official GitHub repository. QuickBox Pro downloads and installs the latest stable release with each update.
Accessing Jackett
After installation, access Jackett at:
https://your-server-ip/username/jackettQuickBox Dashboard Integration
Jackett is automatically integrated into your QuickBox dashboard. Find it in the Service Control panel with port and status information. Click the LAUNCH icon to open the web interface.
Initial Configuration
1. Add Indexers
Configure your torrent trackers:
- Click Add indexer button
- Search for your tracker by name
- Select the tracker from results
- Enter credentials:
- Username/Email
- Password
- API Key (if required)
- Cookie (for some trackers)
- Click Test to verify connection
- Click Save to add the indexer
Popular Private Trackers:
- IPTorrents, TorrentLeech, AlphaRatio
- HD-Torrents, BroadcastTheNet, PassThePopcorn
- Hundreds more supported
2. Connect to *arr Apps
Link Jackett to your applications:
Sonarr/Radarr/Lidarr/Readarr:
- Open your *arr app
- Go to Settings → Indexers → Add (+)
- Select Torznab (or Potato for older apps)
- Enter Jackett connection details:
- Name: Your indexer name (e.g., “IPTorrents via Jackett”)
- URL: Copy from Jackett indexer page (click “Copy Torznab Feed”)
- API Key: Copy from Jackett (top right corner)
- Categories: Select appropriate media types (TV: 5000, Movies: 2000)
- Click Test then Save
Per-Indexer Configuration
Each indexer in Jackett has its own Torznab feed URL. You’ll need to add each tracker separately in your *arr apps, or use Prowlarr for automatic sync.
3. Configure Proxy (Optional)
If using a VPN or proxy:
- Click gear icon (⚙️) in top right
- Go to Jackett Configuration
- Configure proxy settings:
- Proxy Type: SOCKS5 or HTTP
- Proxy Server: Your proxy address
- Proxy Port: Your proxy port
- Save configuration
Service Management
Jackett runs as a systemd service for reliability and automatic startup.
systemctl status jackett@username # Check status
systemctl restart jackett@username # Restart service
journalctl -u jackett@username -f # View live logs
systemctl enable jackett@username # Start on boot
systemctl disable jackett@username # Prevent auto-startTroubleshooting
Jackett Won’t Start
journalctl -u jackett@username -fCheck for port conflicts:
grep -i '\"Port\"' ~/.config/Jackett/ServerConfig.json
# Default: 9117Indexer Connection Failures
Symptoms
- Indexer test fails with authentication errors
- Tracker returns no results in searches
- Cookies expired or invalid
- Rate limit errors from tracker
Resolution
- Verify credentials are correct on tracker website
- Check if tracker requires fresh cookies (login via browser)
- Update Jackett: qb update jackett (may fix tracker definitions)
- Check tracker status page for downtime or maintenance
- Test indexer directly in Jackett manual search to isolate issue
CloudFlare Protection
Some trackers use CloudFlare protection:
# Option 1: Use FlareSolverr (advanced)
# Install and configure FlareSolverr separately
# Configure in Jackett: Settings → FlareSolverr
# Option 2: Manual cookie extraction
# 1. Login to tracker in browser
# 2. Export cookies using browser extension
# 3. Paste cookie string in Jackett indexer configurationPermission Issues
qb fix permissions -u username
systemctl restart jackett@usernameConfiguration Reset
# Backup current configuration
cp ~/.config/Jackett/ServerConfig.json ~/.config/Jackett/ServerConfig.json.backup
# Stop service
systemctl stop jackett@username
# Remove configuration (will be regenerated)
rm ~/.config/Jackett/ServerConfig.json
# Restart service
systemctl start jackett@usernameBest Practices
Do
- Use Prowlarr instead of Jackett for new installations if possible
- Test indexers regularly to catch expired credentials or API changes
- Keep Jackett updated via qb update jackett for latest tracker definitions
- Use different categories for different media types in *arr apps
- Document tracker credentials in a secure password manager
- Monitor indexer statistics to identify underperforming trackers
- Configure proxy if required by tracker rules
- Enable API key authentication for security
Don't
- Don't share Jackett API key publicly—it grants access to your trackers
- Don't add too many indexers—quality over quantity for better performance
- Don't ignore indexer errors—can result in account warnings or bans
- Don't use Jackett for public trackers—Prowlarr handles them better
- Don't forget to update cookies periodically for cookie-based trackers
- Don't disable authentication if Jackett is accessible from the internet
- Don't share tracker credentials—violates most tracker rules
- Don't ignore rate limit warnings—can result in tracker bans
Use Cases
Private Tracker Integration
- Connect private trackers to Sonarr, Radarr, and other automation tools
- Unified API access to trackers without native API support
- Automatic searches across multiple private communities
Legacy Application Support
- Use with older applications that don’t support modern indexer formats
- Bridge between trackers and custom automation scripts
- Manual searching when automation isn’t suitable
Tracker Not in Prowlarr
- Access trackers not yet supported by Prowlarr
- Use custom Cardigann definitions for niche trackers
- Test new tracker integrations before Prowlarr support
Related Applications
Alternative Indexers
Download Clients
Additional Resources
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.