The dev automation account's SSH logins from the deploy runner are refused, and scheduled deploy jobs cannot reach the host.
Stage 2 of 4 in Breach Response.
Containment on this host finished an hour ago, and the cleanup that went with it swept more home directories than intended.
Since then the automation account dev has failed to log in from the deploy runner at 10.0.4.17 every ten minutes.
Security approved re-installing dev's public key from ticket OPS-4471, and only that key.
The runner team suspects their own key rotation.
The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.
The alert fires and the clock starts. Read the page and the briefing.
Work in a simulated shell with realistic output: logs, configs, services.
Change the system the way you would in production. Hints are there if you get stuck.
Automated checks verify the recovery, then the debrief explains what happened.
Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.