Failed Scanner Auth
A scanner exists in the database but has lost its api_key_hash. The scanner cannot authenticate to ingest, so it cannot pick up its assigned jobs.
How to
Repair (recommended)
- Open the affected state row in Health > Job Errors
- Choose "Regenerate token" — generates a fresh provisioning token (24h expiry)
- Copy the install URL from the response and re-provision the scanner host
- On next successful auth, the alarm and state row auto-resolve
Repair (alternate)
- Reassign jobs to a different scanner with a valid key
- Or fail the jobs if they are no longer needed
Gotchas
- Regenerating the token does NOT modify scan_jobs — only the scanner row.
- The scanner must reconnect within 24h or the new provisioning token expires.
- If the scanner was rotated by mistake, you may have a previous_api_key_hash usable for grace-window rotation; check Config > Scanners for the rotation history.
API calls (1)
| Method | Path | Description |
|---|---|---|
| POST | /api/health/job-errors/:stateId/repair | action=regenerate_token |
Related
- Job Errors Overview — Category model
- Scanners — Manage scanner provisioning