Connections, SSH, and SFTP
Using SSH keys with ServerDesk
Connect servers with SSH keys, keep permissions correct, and troubleshoot key-based login failures.
What ServerDesk needs
ServerDesk needs the private key that matches a public key already installed on the target server user account. If the key is passphrase-protected, enter the passphrase when the connection is created.
Common key problems
Key authentication usually fails because the wrong key is used, the public key is missing from `authorized_keys`, or the server rejects the file permissions for the home directory, `.ssh`, or `authorized_keys`.
- Confirm the key belongs to the selected server user.
- Check `~/.ssh/authorized_keys` on the server.
- Verify strict permissions on the user home directory and `.ssh` directory.
Operational advice
Use separate keys for separate environments where possible. This reduces blast radius and makes it easier to rotate access without affecting unrelated servers.
Need something else?
Move back into the searchable Help Centre, open the Support Hub, or use the public bug report and feature request routes if this article does not cover your workflow.