Main Settings
Configure Huntarr's core settings including authentication, network, UI preferences, feature flags, and reverse proxy integration.
Accessing Settings
Navigate to Settings from the sidebar. The main settings page is the first item. All changes require clicking Save at the top of the page before they take effect. Some changes (like port or base URL) require a container/service restart.
General Settings
| Setting | Default | Description |
|---|---|---|
| Timezone | UTC | Used for scheduling, log timestamps, and calendar views. Set this to your local timezone
for accurate scheduling (e.g., America/New_York,
Europe/London).
|
| Web Server Port | 9705 | The internal port Huntarr listens on. If changed, you must also update your Docker port mapping or firewall rules. Most users should leave this at default. |
| Web Server Threads | 8 | Number of concurrent worker threads (4–32). Increase if you have many simultaneous users or heavy API usage. Decrease on low-resource systems. |
| Base URL | / | Path prefix for reverse proxy setups. Set this to match your proxy path (e.g.,
/huntarr). Leave as / if accessing Huntarr directly by port.
|
Authentication Modes
Huntarr supports three authentication modes. Choose the one that fits your network setup:
Login Mode (Default — Recommended)
All connections require a username and password. This is the most secure option and is recommended for any deployment accessible from outside your local network. Supports optional 2FA and Plex SSO as additional login methods.
Local Bypass Mode
Connections from your local network (same subnet) skip the login screen automatically. Connections from outside your network still require authentication. This is useful if you trust everyone on your LAN but want to protect external access.
Huntarr checks the connecting IP against private address ranges (10.x.x.x, 172.16-31.x.x,
192.168.x.x). If you're behind a reverse proxy, make sure the proxy forwards the real client IP
via X-Forwarded-For headers, otherwise all requests will appear local.
No Login Mode
Authentication is completely disabled. Anyone who can reach the URL has full admin access. Only use this if Huntarr is behind a properly secured reverse proxy that handles authentication (e.g., Authelia, Authentik, or a VPN).
No Login mode exposes your entire media infrastructure (API keys, instance URLs, user data) to anyone who can reach Huntarr. Never use this on a publicly accessible server without proxy-level authentication.
| Setting | Default | Description |
|---|---|---|
| Session Timeout | 24 hours | How long a login session lasts before requiring re-authentication. Shorter timeouts are more secure; longer timeouts are more convenient. Range: 1–720 hours. |
| Two-Factor Auth (2FA) | Disabled | Adds TOTP-based 2FA using any authenticator app (Google Authenticator, Authy, 1Password, etc.). Requires entering a 6-digit code after password login. |
| Plex SSO | Disabled | Allows users to sign in with their Plex account. Especially useful for Requestarr — users can request media without creating separate Huntarr accounts. Requires linking the owner's Plex account first. |
Feature Flags
Feature flags let you enable or disable entire sections of Huntarr. This is useful if you only use some features and want a cleaner sidebar.
| Flag | Default | What it controls |
|---|---|---|
| Enable Requestarr | On | Shows/hides the Requests section in the sidebar and all request-related functionality. |
| Enable Media Hunt | On | Shows/hides Media Hunt (the built-in Radarr/Sonarr alternative) and NZB Hunt in the sidebar. |
| Enable 3rd Party Apps | On | Shows/hides the Apps section (Sonarr, Radarr, Lidarr, etc. connections). |
UI Preferences
| Setting | Default | Description |
|---|---|---|
| Theme | Dark | UI color theme. Dark mode is the default and recommended for the best visual experience. |
| Dashboard View | List | Default home page layout. List view shows app status in rows; Grid view shows status cards. |
| Custom Logo URL | Default | Replace the Huntarr logo with your own by entering an image URL. Appears in the sidebar and login page. |
Reverse Proxy Setup
If you're running Huntarr behind a reverse proxy, follow these steps:
- Set the Base URL in Settings to match your proxy path (e.g.,
/huntarr) - Configure your proxy to forward traffic to Huntarr's port (default 9705)
- Ensure real client IPs are forwarded (important for Local Bypass mode)
- Restart the Huntarr container after changing the Base URL
Nginx Example
location /huntarr/ {
proxy_pass http://localhost:9705/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
Caddy Example
your-domain.com {
handle_path /huntarr/* {
reverse_proxy localhost:9705
}
}
Traefik Example (Docker Labels)
labels:
- "traefik.enable=true"
- "traefik.http.routers.huntarr.rule=Host(`your-domain.com`) && PathPrefix(`/huntarr`)"
- "traefik.http.services.huntarr.loadbalancer.server.port=9705"
- "traefik.http.middlewares.huntarr-strip.stripprefix.prefixes=/huntarr"
- "traefik.http.routers.huntarr.middlewares=huntarr-strip"
Some features (like live log streaming) use WebSockets. Make sure your reverse proxy forwards
WebSocket connections — the Nginx example above includes the necessary Upgrade
headers.
Docker Environment Variables
Some settings can also be configured via Docker environment variables, which take precedence over UI settings:
| Variable | Default | Description |
|---|---|---|
TZ |
UTC | Container timezone |
PUID |
1000 | User ID for file permissions |
PGID |
1000 | Group ID for file permissions |
Performance Tuning
For most users, the defaults work well. If you experience slow responses with many concurrent users or heavy API traffic:
- Increase worker threads — Try 12–16 threads if serving multiple users
- Monitor memory — Huntarr typically uses 150–300 MB RAM. If it exceeds 500 MB, check your log settings (verbose logging uses more memory)
- Database size — Large libraries with thousands of items may slow the first load. The activity/history views are paginated to keep things fast
After changing any settings, verify they're working by checking the Logs page (System → Logs) for any errors or warnings.