-
-
Notifications
You must be signed in to change notification settings - Fork 67
Backup
SSH Pilot lets you back up your settings, connections, snippets, and credentials. You can export them to a file, sync them to Bitwarden/Vaultwarden, or copy a backup archive to a remote server.
| Item | Included |
|---|---|
| App settings (UI preferences, shortcuts, themes) | Yes |
| Connections and groups | Yes |
| Snippets library | Yes |
| SSH config file | Yes |
| Known hosts file | Yes |
| Private keys | Optional (off by default) |
| Passwords and passphrases | Yes |
Note: Your ~/.ssh/config and private keys are managed by OpenSSH. SSH Pilot backs up its own copy and settings.
- Open the application menu (hamburger menu on Linux, File menu on macOS)
- Go to Backup/Restore
- Click Start Backup
- Choose a location to save the backup file
- The backup is saved as an archive
- Open the application menu
- Go to Backup/Restore
- Click Restore Configuration
- Select your backup file
- SSH Pilot applies the settings and restarts if needed
If you use SSH Pilot on multiple machines, you can store configuration backups as secure notes in Bitwarden or Vaultwarden -- separate from credential login items.
For credential backend setup, the rbw option, and performance notes, see Bitwarden & Vaultwarden.
- Open Settings > Security
- Select Bitwarden / Vaultwarden (or Bitwarden via rbw) as your credential backend
- Complete the setup wizard (email and master password, plus 2FA if enabled)
- Unlock the vault
You do not need Bitwarden as the credential backend only for backups, but the vault must be signed in and unlocked for Import/Export Bitwarden actions.
- Open the application menu
- Go to Import/Export
- Click Export to Bitwarden
- Optionally set a passphrase for the backup archive
- Confirm -- the backup is saved as a secure note (prefixed with
sshpilot_backup)
- Install SSH Pilot on the new machine
- Sign in to the same Bitwarden vault and unlock it
- Open Import/Export
- Click Import from Bitwarden
- Select a backup from the list (sorted by date), preview if needed, then confirm
You can also copy backup archives to or from another host over SSH:
- Open Import/Export
- Choose the remote export or import option
- Pick a server and a remote directory (default:
~/sshpilot-backups) - Complete the transfer, then import locally if you downloaded a backup
| Destination | How it works |
|---|---|
| Local file | Export Configuration / Import Configuration |
| Bitwarden/Vaultwarden | Export to Bitwarden / Import from Bitwarden (secure notes) |
| Remote server | Upload or download backup archives over SSH |
If you restore a backup on a different machine, SSH Pilot automatically adjusts file paths to match the new system.
If your ~/.ssh/config uses Include directives, SSH Pilot backs up the entire config tree, not just the main file.
Backup archives can be encrypted for extra security.
Backups include version information so SSH Pilot knows what format they are in.
Secure notes have a maximum size. If a backup is too large (many private keys or a large SSH config), SSH Pilot warns you. Exclude private keys to reduce size.
Tip: Back up regularly, especially before upgrading SSH Pilot or making big changes to your configuration.
Tip: If you use Bitwarden on multiple machines, cloud backups are the easiest way to stay in sync.
Tip: Your snippets library is included in backups, so you don't lose your saved commands.
- Bitwarden & Vaultwarden -- Credential and backup vault details
- Credentials -- Set up password storage
- Settings -- Customize SSH Pilot
- Troubleshooting -- Solutions to common problems
- 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