-
-
Notifications
You must be signed in to change notification settings - Fork 67
Known Hosts
Mehdi edited this page Sep 2, 2026
·
2 revisions
When you connect to a server for the first time, SSH remembers its fingerprint in a known_hosts file. That protects you from connecting to a fake server later.
If a server was reinstalled or its key changed, you may see Host key verification failed. The Known Hosts Editor lets you remove the old fingerprint so you can connect again.
- Application menu (hamburger on Linux, File on macOS) → SSH → Known Hosts Editor
- Or press
Shift+Shiftand typeknown hosts
- Open Known Hosts Editor
- Search for the server name or IP
- Click the trash icon on the old entry
- Click Save
- Connect again and accept the new fingerprint when asked
Nothing is removed for good until you click Save. Cancel closes without saving.
- In normal use this edits
~/.ssh/known_hosts(the same file thesshcommand uses) - If you use Isolated Mode, SSH Pilot keeps its own known hosts file instead
- This editor only removes entries. New fingerprints are added when you accept a host key while connecting
- For managing login keys (who can access an account), see Authorized Keys
- Troubleshooting -- Other connection problems
- Authorized Keys -- Manage installed login keys
- Key Management -- Generate and deploy your SSH keys
- Home
- Installation
- Quick Start
- Main Window
- Sidebar
- Connections
- Groups
- Terminal
- File Manager
- Credentials
- Key Management
- Known Hosts
- Authorized Keys
- Keyboard Quick Reference
- Omni-search
- Snippets
- Keyboard Shortcuts
- Plain Terminal Mode
- Docker Console
- Protocols
- Security
- Bitwarden & Vaultwarden
- Settings
- Isolated Mode
- Backup
- Plugins
- FAQ
- Troubleshooting