How to Fix “No route to host” SSH Error in Linux

SSH is the most secure means of connecting to Linux servers remotely. And one of the common errors encountered while using SSH is the “ssh: connect to host port 22: No route to host”. In this short article, we will show how to troubleshoot and fix this error.

Here is a screenshot of the error we are talking about. Note that the port may not necessarily be port 22, depending on your configurations on the remote host. As a security measure, system administrators can configure SSH to be accessed via a different port.

SSH No Route to Host Error
SSH No Route to Host Error

There are different reasons why this error appears. The first is normally that the remote server could be down, so you need to check whether it is up and running using the ping command.

# ping
Ping Linux Server
Ping Linux Server

From the ping command results, the server is up and running, that’s why it is accepting the pings. In this case, the reason for the error is something else.

If you have a firewall service running on your remote server, it is possible that the firewall is blocking access via port 22.

Therefore you need to access the server console physically or if it is a VPS, you can use any other means such as VNC (that’s if it is already setup) or other custom remote server access applications provided by your VPS service provider. Login, and access a command prompt.

Then use the firewall-cmd (RHEL/CentOS/Fedora) or UFW (Debian/Ubuntu) to open port 22 (or the port you configured to be used for SSH) in the firewall as follows.

# firewall-cmd --permanent --add-port=22/tcp
# firewall-cmd --reload
$ sudo ufw allow 22/tcp
$ sudo ufw reload 

Now try to re-connect to the remote server once more via SSH.

$ ssh [email protected]
SSH Login Successful
SSH Login Successful

That’s it for now! You will also find the following SSH guides useful:

  1. How to Change SSH Port in Linux
  2. How to Create SSH Tunneling or Port Forwarding in Linux
  3. How to Disable SSH Root Login in Linux
  4. 4 Ways to Speed Up SSH Connections in Linux
  5. How to Find All Failed SSH login Attempts in Linux

Remember, you can share your thoughts with us or ask any questions concerning this topic via the comment form below.

Hey TecMint readers,

Exciting news! Every month, our top blog commenters will have the chance to win fantastic rewards, like free Linux eBooks such as RHCE, RHCSA, LFCS, Learn Linux, and Awk, each worth $20!

Learn more about the contest and stand a chance to win by sharing your thoughts below!

Aaron Kili
Aaron Kili is a Linux and F.O.S.S enthusiast, an upcoming Linux SysAdmin, web developer, and currently a content creator for TecMint who loves working with computers and strongly believes in sharing knowledge.

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.


Leave a Reply
  1. Thank you. You are a live saver.

    I was busy checking for iptables and ufw on the problematic server that had many hands managing it, having forgotten about firewalld. Your tutorial pointed me in the right direction.

  2. First things first – Thank you very much for publishing the various articles on Linux. I use them as a quick reference when needed.

    I have noticed typo’s in several articles I have used recently. I used the setup vsftpd, vsftpd with a certificate, and samba articles. Each of them had a minor typo such as a missing "/" on the path or an omitted letter such as a missing “f” in conf (con vice conf). These were very minor discrepancies. Overall, I was very pleased with the results as the outcome was spot-on after fixing the minor errors.

    Thank You, again!


Got Something to Say? Join the Discussion...

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.