Host Key Verification
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”Use the commands in this guide when attempting to SSH into an asset and you receive the following error:
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!Someone could be eavesdropping on you right now (man-in-the-middle attack)!It is also possible that a host key has just been changed....Offending ECDSA key in /Users/<you>/.ssh/known_hosts:<line>Host key for p2-dock-# has changed and you have requested strict checking.Host key verification failed.Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
use-these-commands-when-a-user-home-di["<small><b>Step 1</b></small><br/>Action: Use these commands when a user/home d..."]
style use-these-commands-when-a-user-home-di fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
- Compute:
ssh-keygen -f ~/.ssh/known_hosts -R "p2-zip-#-compute-a"- Crossfire:
ssh-keygen -f ~/.ssh/known_hosts -R "p2-zip-#-crossfire"- Dock:
ssh-keygen -f ~/.ssh/known_hosts -R "p2-dock-#"Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.