Contents
Troubleshooting
An SSH connection fails
The message appears at the bottom right of the window. Look for it in this table.
By Lucas Russo, developer of SSHive · Updated
| Message | What it means | What to do |
|---|---|---|
| Connection refused (SSH port closed or server unreachable) | Nobody is listening on that port | Check the port of the server, and that the SSH service is running |
| Timeout: server not responding | No answer at all: wrong address, a firewall, a machine that is off | Check the address; try a port check |
| A message saying the host is unreachable and that macOS may be blocking SSHive on the local network | macOS does not allow SSHive on the local network | System Settings > Privacy & Security > Local Network, turn SSHive on |
| Network unreachable: verify your connection | The Mac has no network | Wi-Fi, cable, VPN |
| Authentication failed: verify username, password, key, or passphrase | The server refused | Check the user; see Passwords and SSH keys |
| The server disconnected after too many authentication attempts (MaxAuthTries). | Too many keys were offered | Choose the Agent key of the server, or one precise key in the profile |
| A message saying the server closed the connection because nobody answered its question | A code or a password it asked for did not come in time | Connect again and answer faster |
| Key file unreadable: re-select it via "Browse". | SSHive has lost access to the key file | Edit the server, Browse, choose the key again |
| Connection interrupted by server | The server cut the connection | Its own logs; see reconnection |
| The SSH Security Warning dialog | The fingerprint of the server changed | Server fingerprints |
Applies to SSHive 2.0.6 on Mac