pgAdmin3 connection problems

Question

I'm recently setting up and running a Windows 2008 r2 server with VMware Workstation 8.

I'm running a Centos 6.2 virtual linux box with Postgresql 9.1. Everything seems ok locally and I can connect to the CentOS box via a bridged network connection.

I have followed David Ghedini's walkthrough for setting up Postgresql 9.1. So I am able to start a putty session window, log in as root and start psql shell and issue statements as postgres user. My problem is that I cannot connect using pgAdmin III from my Windows 7 client. I have updated the /var/lib/pgsql/9.1/data/postgresql.conf to enable listen_addresses '*', etc.

Could anyone give me any tips on finding my fault. Have ensured Windows Firewall is disabled on the Windows server, too.

The pgAdmin III client reports;

'Server doesn't listen'

The server doesn't accept connections: the connection library reports

could not connect to server: Connection timed out (0x0000274C/10060) Is the server running on host "192.168.1.26" and accepting TCP/IP connections on port 5432?

This is the pg_hba.conf file entry added:

#TYPE DATABASE   USER   ADDRESS          METHOD
host  all        all    192.168.1.0/24   trust

And the iptables file entries added:

-A INPUT -p tcp -s 0/0 --sport 1024:65535 -d 192.168.1.26 --dport 5432 -m state --state NEW,ESTABLISHED -j ACCEPT
-A OUTPUT -p tcp -s 192.168.1.26 --sport 5432 -d 0/0 --dport 1024:65535 -m state --state ESTABLISHED -j ACCEPT

Answer 1

You need to adjust pg_hba.conf:

http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html

Once you add your own host and corresponding user, restart postgresql server so hopefully you can connect.

Also you might need to enable it's port on the network: http://www.cyberciti.biz/tips/postgres-allow-remote-access-tcp-connection.html

Answer 2

i have the same problem. I disabled all my third party antiviruses and firewalls and reinstall PostgreSQL again and its now working fine... :)

Answer 3

Make sure PostgreSQL Server is allowed through the firewall:

On the server machine, go to

Control Panel > System and Security > Windows Firewall > Allow an app through Windows Firewall

Scroll through Allowed apps and features, make sure 'PostgreSQL Server' is checked.

Answer 4

Probably a firewall issue, check it by

systemctl status firewalld.service

you could simply disable it by:

systemctl stop firewalld.service
systemctl disable firewalld.service

Answer 5

Is the server running on host "192.168.1.26" and accepting TCP/IP connections on port 5432?

Check that the server has that IP address. Check that there are postgres processes running. Use netstat to confirm that the server is listening on port 5432.

Answer 6

Adding to the great answers above, after implementing all the firewall rules and the configuration file changes, it still wasn't connecting to my host's IP address. Then I realized I had installed pgadmin locally on the host that my postgres db was installed on. I didn't need to use the external IP address for the host, I simply needed to connect to "localhost" in the pgadmin connection process. Extremely frustrating but made sense. So, if you

• host pgadmin from the same server as your postgres database
• have ruled out that the firewall is not in your way
• have ruled out that any security groups are not blocking you
• have fiddled enough with your configuration files pg_hba.conf and postgresql.conf

then maybe... just maybe, try connecting to "localhost" or "127.0.0.1".

it's worth a shot right!

Answer 7

I had the same problem of yours:

could not connect to server: Connection timed out (0x0000274C/10060) Is the server running on host "192.168.1.26" and accepting TCP/IP connections on port 5432?

Maybe you need to set your reversed ip to the whitelist:
26.1.168.192

Answer 8

You should also allow port 5432 on the firewall.

example on centos 8:

sudo firewall-cmd --zone = public --add-port = 5432 / tcp --permanent