How to Fix the SSH Connection Refused Error on Linux

Encountering an SSH “Connection Refused” error on Linux can be frustrating, especially when you need remote access to manage your server or device. This error generally indicates that your SSH client cannot establish a connection to the server, often due to misconfigurations, service issues, or network problems. Fixing it involves a series of troubleshooting steps to identify and resolve the underlying cause. This guide provides a comprehensive, step-by-step approach to diagnose and fix the SSH connection refused error, ensuring you regain secure remote access efficiently. Before starting, ensure you have local access to the server or device, or alternative means of troubleshooting, as some steps require direct access to the system.

What You’ll Need

• Access to the Linux server via local terminal or console (if remote access fails)
• Administrator or root privileges on the server
• Basic knowledge of Linux command line
• Network information such as server IP address or hostname
• Optional: SSH client (like PuTTY on Windows or terminal on Linux/macOS)

Step-by-Step

1. Verify the SSH Service is Running
   First, confirm that the SSH server (sshd) is active and running on the target machine. If you have local access, open the terminal and run:
   sudo systemctl status sshd
   or, for some distributions:
   sudo service ssh status.
   If the service is inactive or not running, start it with:
   sudo systemctl start sshd or
   sudo service ssh start.
   Ensure it is enabled to start on boot with:
   sudo systemctl enable sshd.
2. Check SSH Port and Firewall Settings
   By default, SSH listens on port 22. Verify that the server is listening on this port:
   sudo netstat -tlnp | grep ssh or
   ss -tlnp | grep ssh.
   If SSH is configured to listen on a different port, ensure you’re connecting to that port.
   Next, check firewall rules. For example, on UFW (Uncomplicated Firewall):
   sudo ufw status.
   If port 22 (or your custom SSH port) is not allowed, add a rule:
   sudo ufw allow 22/tcp or
   sudo ufw allow /tcp.
   After making changes, reload the firewall:
   sudo ufw reload.
3. Test Local SSH Connection
   From the server itself, try SSHing to localhost to verify SSH is functioning internally:
   ssh localhost.
   If this works, the problem is likely network-related. If it fails, the issue is with SSH configuration or service.
4. Check SSH Configuration File
   Review the SSH server configuration at /etc/ssh/sshd_config. Look for common issues such as:
   – Port number (ensure it matches the port you’re connecting to)
   – PermitRootLogin (set to yes or no as needed)
   – PasswordAuthentication (enabled or disabled)
   – AllowTcpForwarding and other restrictions
   Make necessary adjustments and restart SSH service:
   sudo systemctl restart sshd.
5. Test Network Connectivity
   From your client machine, test if the server is reachable using ping:
   ping <server-ip>. If ping fails, there might be network issues or the server might be down.
   Next, test port connectivity with telnet or nc (netcat):
   telnet <server-ip> 22 or
   nc -zv <server-ip> 22.
   If these fail, troubleshoot network routes, VPNs, or NAT settings that could block access.
6. Review Server Logs for Errors
   Check SSH logs for detailed error messages. On most Linux systems, view logs with:
   sudo journalctl -u sshd or
   sudo tail -f /var/log/auth.log.
   Look for errors related to authentication, port issues, or configuration problems.
7. Verify Client-side Settings
   Ensure your SSH client is configured correctly. Check the command syntax:
   ssh user@server-ip. If you’re using a custom port, specify it:
   ssh -p <port> user@server-ip.
   Clear any cached credentials or SSH keys that might be outdated.
   Try connecting from a different client or network to rule out local issues.
8. Reboot the Server if Necessary
   If all else fails, a simple server reboot can sometimes resolve transient issues. Use:
   sudo reboot.
   Be cautious if you are remotely connected; ensure you have alternative access in case of failure.

Common Mistakes

• Failing to restart SSH service after making configuration changes.
• Incorrect firewall rules blocking port 22 or custom SSH port.
• Using the wrong server IP address or hostname during connection.
• Not verifying that SSH service is active and listening on the expected port.
• Misconfiguring SSH settings in sshd_config, such as disabling password authentication when needed.
• Overlooking network issues like VPN restrictions, NAT misconfigurations, or ISP blocks.

Tips

• Always back up your SSH configuration before making changes.
• Use verbose mode for SSH to get more detailed error messages:
  ssh -v user@server-ip.
• Keep your server’s system and SSH packages updated for security and stability.
• Restrict SSH access to specific IP addresses if possible for added security.
• Set up alternative access methods such as console access or remote management tools, especially for critical servers.
• Regularly review SSH logs to detect unauthorized access attempts or issues.

Troubleshooting

If the connection still refuses after following the above steps, consider these additional troubleshooting tips:

• Check for conflicting services or processes: Ensure no other service is occupying SSH’s port.
  Use sudo lsof -i :22 to see what is listening on port 22.
• Test from different networks: Sometimes, local network policies or firewalls block SSH. Try connecting from a different network or using a VPN.
• Disable SELinux or AppArmor temporarily: Security modules might block SSH. Test by disabling them temporarily and re-enabling after testing.
• Reinstall SSH server: If corruption or misconfiguration persists, reinstall the SSH server:
  sudo apt-get install --reinstall openssh-server.
• Consult online resources or community forums: Sometimes, specific distributions or setups have unique issues. Forums like Stack Exchange, Reddit, or distribution-specific communities can help.

Frequently Asked Questions

Why does SSH say “Connection Refused”?

This typically means the SSH server isn’t running, isn’t listening on the specified port, or network/firewall rules are blocking the connection.

How do I restart the SSH service?

Use sudo systemctl restart sshd or sudo service ssh restart depending on your Linux distribution.

What if I can’t access the server locally?

If local access isn’t possible, check physical access, console access, or use out-of-band management tools like IPMI or iDRAC.

Can firewall settings cause SSH connection refusal?

Yes, firewalls blocking port 22 or your custom SSH port will prevent connections. Ensure the port is open and allowed through firewall rules.

Is it safe to enable root login via SSH?

Enabling root login can pose security risks. It’s recommended to disable it or use SSH key authentication with a non-root user.

How do I change the SSH port?

Edit /etc/ssh/sshd_config, change the Port directive, and restart SSH service. Remember to update your client connection command accordingly.

Fixing SSH “Connection Refused” errors on Linux requires systematic troubleshooting, but with patience, most issues can be resolved quickly. Regular maintenance, monitoring logs, and ensuring proper configuration can prevent future problems and keep your remote connections secure and reliable.

Related

• How to Fix Slow App Store Downloads and Updates on iPhone
• Fix Slot Unbootable Load Error on Pixel Devices Without Data Loss
• How to Fix Slideshow Not Working in Windows 11