Contents
SSHive Agent
When SSHive Agent does not answer
SSHive names the cause rather than failing silently. Each message below says what it means, and what it takes to get the connection going again.
By Lucas Russo, developer of SSHive · Updated
| What happened | What it means | What to do |
|---|---|---|
| SSHive Agent is not answering | It is not installed, or not running | Install it, or open it if it is already there |
| SSHive Agent is installed, but is not answering | It is stopped | Open SSHive Agent, or open it from Applications. If it stops again: System Settings > General > Login Items, Allow in the Background |
| SSHive Agent refused the request: it did not recognise this copy of SSHive | It answers only the SSHive of the App Store, in the Applications folder | Install SSHive from the App Store, straight into Applications and not into a subfolder, and update both |
| SSHive Agent is too old for this version of SSHive | Its version is behind | Update it |
| SSHive Agent did not understand the request | The two versions do not match | Update SSHive and SSHive Agent |
| SSHive Agent is already serving the maximum number of connections | More than 256 connections through the agent at once | Close a few sessions, then try again |
| This path does not lead to the socket of an SSH agent | The agent path set in SSHive or in ~/.ssh/config is wrong | Check the path in Settings > Connection > SSH Agent |
| This socket does not belong to your macOS account | The agent is running under another account | Start the vault in your own session |
| SSHive Agent cannot serve this macOS account: its socket path is over 103 bytes | A home folder with a very long name | Tell us |
| The SSH agent of the vault refused the request | The vault said no: locked, or Touch ID cancelled | Unlock the vault, then try again |
Applies to SSHive 2.0.8 on Mac