SSH Remote Administration & Key Authentication

I wanted remote administration between my Linux servers, including key-based access and the ability to launch Hermes from an SSH session.

I installed and enabled OpenSSH on the receiving machine. Earlier sessions reported an active service and successful remote connections.

I worked through key authentication with ssh-copy-id. Its preserved warning said the keys already existed on the destination, so I did not need to force another copy; I confirmed that access worked.

A remote Hermes launch returned command not found after SSH had connected. Using the executable's absolute path resolved the launch problem. A different remote shell PATH is the likely explanation, but its value was not captured.

Remote login worked, the key-copy output showed an already-authorized key, and Hermes launched after I used its absolute executable path.

The October 3 record preserves the key-copy warning and successful connection reports; earlier sessions report the SSH service running.

The absolute-path fix was confirmed. Additional PATH and non-interactive authentication checks in the source document are suggestions, not captured execution output. Private account paths and destinations are omitted.

I practiced separating network reachability, SSH authentication, and command discovery into distinct problems.

I learned that an already-installed-key warning does not call for overwriting a working key, and that access in one direction does not establish the reverse.