Connections, SSH, and SFTP
Troubleshooting connection issues
Diagnose failed server connections in ServerDesk using the most common SSH and SFTP checks.
Most common causes
Most failed connections are caused by incorrect hostnames, blocked ports, wrong usernames, invalid passwords, key mismatches, or a server that blocks SFTP.
Useful checks
Compare the same connection details in another trusted SSH client if needed, confirm the server is reachable on the expected port, and verify the selected root path exists for that account.
Error patterns
Permission denied points to bad user or credentials. Connection refused points to the wrong port or a stopped SSH service. Timeout usually points to firewalls, private networking, DNS, or host reachability.
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.