SSH errors and host keys
Use the exact SSH error to separate reachability, service and login problems.
Common symptoms
Connection timed out, timeout, Connection refused, Permission denied, publickey, host key mismatch, REMOTE HOST IDENTIFICATION HAS CHANGED
What to check
- Copy the current address, port and username from server details. Check power state, pending operations and maintenance, then compare access from another suitable network if available.
- For timeout, check routing and firewall rules. For Connection refused, use Console to check whether SSH is listening on the expected port. For Permission denied (publickey), check the username and matching installed public key.
- For a host key mismatch, first confirm the server identity and any reinstall or address change. Verify the current host key through a trusted path before replacing only the matching known_hosts entry.
Common questions
Does a timeout mean my SSH key is wrong?
A timeout usually occurs before authentication. Check the address, port, IPv4/IPv6 reachability, route and firewall first. Connection refused instead suggests the target rejected the connection or no service is listening.
Can I ignore REMOTE HOST IDENTIFICATION HAS CHANGED?
Check the server identity first. A reinstall can change its host key, but an unexpected change also needs investigation. Do not disable host key checking or remove every saved host key to bypass the warning.
Open the relevant page
Before contacting support
Share the server name, time with timezone, SSH error, client network type and sanitized relevant settings. Never send a password, private key, token or authentication code.
Keep secrets out of support requests · Remove passwords, private keys, access tokens, TOTP codes, backup codes and full payment details from screenshots and logs. Share the server or order name, time with timezone and exact sanitized error.
Official reference documentation
This opens an editable ticket draft. Nothing is sent automatically.