-
Notifications
You must be signed in to change notification settings - Fork 0
Web UI
Inspectarr's web UI runs on port 8585 (configurable via web.port). All pages share a sidebar and support light and dark themes.
The landing page. Recent scan activity, flagged and actioned counts over your retention window, the most recent catch (with a Historical tab for earlier ones), and current scheduler state.
Controls the scan scheduler:
- Start / Stop the scheduler
- Current polling interval and next scheduled scan
- Webhook URLs (when
scanning.webhooks.enabledistrue) — copy these into your *arr apps under Connect → Webhook - Retry queue depth
- Trigger a manual scan
Every torrent in the categories your rules watch, paginated. Shows file-level detail including which files triggered a match and why.
Catches being held for review rather than deleted. Each entry shows its risk level, the rule that fired, the offending files, and how long it has been held.
Three actions per entry — Release (resume it), Keep paused (stop asking, leave it paused), and Delete (blocklist and remove). An entry flagged not paused means the torrent client refused to pause it and it is still downloading.
Empty by default: quarantine only holds anything once you open a review band. See Quarantine & Severity.
The Prowlarr hub, with tabs:
- Overview — health scores, per-indexer actions (Rescore, Reorder & Sync, Ignore, Reset stats, Enable/Disable)
- AI Scoring — deterministic vs AI score per indexer, the model's reasoning, and a trend chart
- Stats — per-indexer query, grab, and failure statistics
Only meaningful when prowlarr.enabled is true. See Prowlarr Indexer Scoring.
Panes down the left, one Save Configuration button. Changes are written to config.yaml and picked up on the next scan cycle — no restart needed, except for web.port.
| Pane | Contains |
|---|---|
| Connections | Torrent client (qBittorrent / Transmission / Deluge) and *arr apps, each with a test button |
| Rules | The rule builder, plus Remediation & Severity — the two thresholds, quarantine timeout, and timeout action |
| Prowlarr | Connection, scoring weights, auto-manage |
| Notifications | Apprise URLs, event types, digest and periodic summary |
| AI | The Enable AI features master switch (off by default), then Ollama URL and timeout, model selection and validation, cache TTL, system prompt |
| General | Behaviour, dry run, scan triggers, retry, web UI authentication |
| Advanced | Logging, state, and less-common options |
| Backups | Snapshot and restore config.yaml and the state database |
A Raw YAML toggle in the top bar edits the file directly — needed for settings without a form field, such as remediation.severity_overrides.
| Page | Shows |
|---|---|
| Status | Version, Python version, platform, storage usage, and live connection checks for every configured service |
| Tasks | Background jobs (scan cycle, retry processing, Prowlarr reorder, pruning) with last and next run |
| Updates | Current version against the latest GitHub release |
| Logs | The event log, filterable by level, with live streaming and export |
Set web.auth.enabled: true to password-protect the UI. See Authentication.
The one exception is /api/health, which stays reachable without credentials so container healthchecks work — it exposes only version, database, and scheduler state. See the JSON API.
The UI is responsive; the sidebar collapses into a hamburger menu on narrow screens.