Postgresql – Unable to connect to posgres using pgadmin

kubernetespostgresql

I have a postgres instance inside a kubernetes cluster. I have setup a port forward and if I use the postgres CLI I can connect and perform queries as expected.

If I connect via pgadmin it appears to work as expected I am able to see the schemas and navigate to the tbles, but if I attempt to open the query tool I receive the following error:

could not send data to server: Socket is not connected (0x00002749/10057) could not send SSL negotiation packet: Socket is not connected (0x00002749/10057)

Does anyone know what I need to configure to allow pgadmin to connect to this system?

Best Answer

Unfortunately the error message you get isn't very specific. You may need to configure additional access in pg_hba.conf file which controls client authentication in PostgreSQL. Check its current content and if needed, add the corresponding entry according to this article.

Related Solutions

Postgresql – Cannot connect to PostgreSQL DB Via pgAdmin

Your tcpdump pretty much confirms that iptables is dropping the packets on the server side. tcpdump inspects the packets before they're touched by the firewall. If the firewall was not dropping the packets and postgres wasn't working, the kernel would RST the connection attempt:

07:39:14.878008 IP localhost.12343 > localhost.35259: Flags [R.], seq 0, ack 1980582372, win 0, length 0

and you'd immediately get a connection refused rather than a timeout.

The only other thing I can think of is if you set an absurdly low connection limit on the server and it's already full. I've never tried that to see what would happen, though I have a feeling it would reject connections rather than timing them out based on the behavior of various websites with db errors I run across all the time. You could check postgresql's log to see if it mentions the connection attempt.

Postgresql – pgpool2 parallel mode: Non-superusers must provide a password in the connection string

This could be because pgpool sees this query as read-only, but since it's actually calling a function (which may contain INSERT UPDATE or DELETE statements) it breaks while connecting to the read-only server.

Best Answer

Related Solutions

Postgresql – Cannot connect to PostgreSQL DB Via pgAdmin

Postgresql – pgpool2 parallel mode: Non-superusers must provide a password in the connection string

Related Topic