SSH Connection Refused: Causes and Fixes

SSH “Connection refused” is one of the most-frequent error messages Linux administrators encounter. You try to connect to a server; you get “ssh: connect to host example.com port 22: Connection refused.” The message is unambiguous about what happened (TCP connection rejected) but unclear about why. Possible causes: SSH server isn’t running; firewall blocking port 22; SSH on a non-standard port; deliberate refusal. Each cause has a specific diagnostic and fix. This free guide is the complete diagnostic and repair manual for SSH connection refused errors in 2026, plus the related SSH failure modes (timeout, hung, key issues, permission denied) that look similar but have different root causes.

Written for the developer setting up SSH access to a fresh cloud instance, the engineer locked out after a botched config change, the admin debugging why SSH works from one network but not another, the team setting up SSH bastions for secure access, and anyone whose ssh user@host isn’t doing what they expected. No assumptions about prior network administration experience — every error mode is explained with the symptom, the diagnostic command, and the exact fix.

The guide is honest about SSH realities. Connection refused vs timeout vs no-route-to-host are different errors with different fixes. Firewalls are layered (host, network, cloud); any layer can block. SSH keys (Ed25519) beat passwords. Hardware-backed keys beat software keys for high stakes. ProxyJump beats agent forwarding for security. Managed bastion solutions (Teleport, IAP) beat ad-hoc bastions for enterprise scale. Working with these realities — including the 60-second triage, server status checks, firewall configuration, port changes, timeout diagnosis, key auth patterns, ssh-agent, bastion patterns, cloud-specific quirks, and the recovery recipe — produces a durable SSH practice. Every command has been mentally tested for accuracy.

What This Guide Covers

• How SSH connections actually work in 2026 — TCP, handshake, auth
• Prerequisites and the 60-second triage
• “Connection refused” — the basic diagnosis
• SSH server not running
• Firewall blocking the connection (UFW, firewalld, cloud SGs)
• Non-standard SSH port
• SSH connection timeout (different from refused)
• “Permission denied” — authentication issues
• SSH key problems and ssh-agent
• Host key verification failures
• Network configuration — NAT, IPv4 vs IPv6
• Tunnels, ProxyJump, bastion hosts
• Cloud-specific SSH — AWS, GCP, Azure
• FAQ and the connection recovery recipe

This guide is free. No signup, no email required. AI Learning Guides publishes free troubleshooting eguides for the most common AI platform and developer-tool issues because saving you from a frustrating SSH session is a useful thing to do whether or not you ever buy one of our paid guides.