Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

“psql :could not connect to server: no route to host” – How we fix it

by | May 31, 2021

“psql: could not connect to server: No route to host”  often triggers when users try to connect to PostgreSQL.

A common reason for this error is Firewall restriction. As a part of our Server Management Services, we help our customers with PostgreSQL errors related to regularly.

Today, let us discuss the possible reasons and fixes for this error.


What causes “psql: could not connect to server: No route to host”

While connecting through pgAdmin users often notice the “could not connect to server: No route to host” in the format given below:

psql: could not connect to server: No route to host

Some of the common reasons for pgAdmin to show this error include:

  • Database server isn’t running
  • Server isn’t configured to accept TCP/IP requests on the address shown.

Other than the reasons above, our Support Engineers have noticed that this error could also trigger due to restrictions in the Firewall or using a different port for PostgreSQL. Let us now discuss the steps to fix this error.

How to fix “psql: could not connect to server: No route to host”

Restart PostgreSQL

As we saw earlier, this error could trigger when the PostgreSQL database is not working. We can fix this by performing a restart of the service.

sudo service postgresql restart

Once we restart the service, try reconnecting to PostgreSQL.

Accept TCP/IP requests

For security reasons, a PostgreSQL server “out of the box” doesn’t listen on TCP/IP ports. Instead, it must be enabled to listen for TCP/IP requests.

We need to edit the /var/lib/pgsql/data/postgresql.conf to enable this. Add the following line in the conf file to make the server accept connections on any IP interface.



Firewall restrictions

A common reason for this error is the firewall restrictions blocking the connections to the port 5432. We may try a telnet request to the port 5432 to check if t is reachable:

telnet 192.x1.xx.x1 5432

Trying 192.x1.xx.x1...
telnet: connect to address 192.x1.xx.x1: No route to host

We may need to run the following code to allow incoming connections through the OS firewall in Redhat\CentOS for postgresql default port 5432.

 firewall-cmd --add-service=postgresql --permanent

[Need help to fix PostgreSQL error? We are available 24*7]


In short, the “could not connect to server: No route to host” triggers while connecting to PostgreSQL due to a number of reasons. Today, we saw how our Support Engineers fix it.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.