Opening the Connection Dialog
- Go to Go -> Connect to SFTP Server in the menu bar
- Or press Cmd+K
Connection Settings
Basic Settings
| Host | Server hostname or IP address (e.g., server.example.com) |
| Port | SSH port (default: 22) |
| Username | Your SSH username |
| Initial Path | Directory to open after connecting (optional) |
Authentication
Choose one of these methods:
SSH Key (Recommended)
- Uses your existing SSH keys from
~/.ssh/ - Most secure and convenient option
- Supports RSA, ECDSA, and Ed25519 keys
Password
- Enter password in the connection dialog
- Can save password to Keychain for future connections
Setting Up SSH Keys
If you don't have SSH keys set up:
Generate a New Key
ssh-keygen -t ed25519 -C "[email protected]"
Copy to Server
ssh-copy-id [email protected]
Test Connection
ssh [email protected]
Once this works in Terminal, Captain's Deck will use the same keys automatically.
Saving Connections
To save a connection for quick access:
- Fill in the connection details
- Enter a name in the "Save as" field
- Check "Save password to Keychain" if using password auth
- Click Connect
Saved connections appear in the dropdown for future use.
Browsing Remote Files
Once connected, you can:
- Navigate directories just like local files
- Copy files between local and remote (with F5)
- Move files between local and remote (with F6)
- Rename and delete remote files
- Create directories on the server
- View and edit text files
Tip: Open a local folder in one pane and the remote server in the other for easy file transfers.
Disconnecting
To disconnect from the server:
- Navigate to a local path (use bookmarks or Cmd+G)
- Or close the tab with Cmd+W
Troubleshooting
"Connection refused"
- Verify the hostname and port are correct
- Check if the server's SSH service is running
- Ensure firewall allows SSH connections
"Permission denied"
- Verify your username is correct
- Check your SSH key is added to the server's
~/.ssh/authorized_keys - If using password, verify it's correct
"Host key verification failed"
- The server's identity has changed (could be server reinstall or security issue)
- Remove old key:
ssh-keygen -R hostname - Connect again and verify the new fingerprint
Slow connection
- Try a closer server location if available
- Check your network connection
- Large directories may take time to list