cannot connect to proxy in Docker

[fridlundisme]

I tried running this in docker so I could hook it up to my current setup.
The logs show that I have successful connection but the connection just stops.

If I try to access the db with psql -U postgres -p 5433, or with my docker container thorugh docker ompose, then the end of these logs are the result, and I never enter into the psql shell.

dbpill-proxy  | [proxy] Certificate loaded successfully
dbpill-proxy  | [proxy] Key bytes: 1708 cert bytes: 977
dbpill-proxy  | Database connection successful. Starting proxy on port 5433
dbpill-proxy  |
dbpill-proxy  | [proxy] PostgreSQL proxy listening on port 5433 (TLS MITM ready, IPv4/IPv6)
dbpill-proxy  | → Connect to dbpill SQL proxy at postgresql://postgres:postgres@localhost:5433/postgres to intercept queries.
dbpill-proxy  | → Go to dbpill web UI at http://localhost:3000 to manage the results.
dbpill-proxy  | [proxy] TCP connection accepted from ::ffff:172.18.0.1 port 60752
dbpill-proxy  | [proxy] Received first data chunk: 0000000804d2162f
dbpill-proxy  | [proxy] Detected SSLRequest, upgrading to TLS
dbpill-proxy  | [proxy] Sent S response, creating TLS socket...
dbpill-proxy  | [proxy] TLS socket created, waiting for handshake...
dbpill-proxy  | [proxy] TLS keylog: SERVER_HANDSHAKE_TRAFFIC_SECRET def78baa3e484e8703efd045e1ea1e95ae1da940bf8cc50fc1c4555c32353190 
dbpill-proxy  |
dbpill-proxy  | [proxy] TLS keylog: CLIENT_HANDSHAKE_TRAFFIC_SECRET def78baa3e484e8703efd045e1ea1e95ae1da940bf8cc50fc1c4555c32353190 
dbpill-proxy  |
dbpill-proxy  | [proxy] TLS keylog: EXPORTER_SECRET def78baa3e484e8703efd045e1ea1e95ae1da940bf8cc50fc1c4555c32353190 
dbpill-proxy  |
dbpill-proxy  | [proxy] TLS keylog: SERVER_TRAFFIC_SECRET_0 def78baa3e484e8703efd045e1ea1e95ae1da940bf8cc50fc1c4555c32353190 
dbpill-proxy  |
dbpill-proxy  | [proxy] TLS keylog: CLIENT_TRAFFIC_SECRET_0 def78baa3e484e8703efd045e1ea1e95ae1da940bf8cc50fc1c4555c32353190 
dbpill-proxy  |
dbpill-proxy  | [proxy] Received first Postgres bytes after TLS handshake: 00000054000300007573657
dbpill-proxy  | [proxy] startPgProxy called. Pending buffer length: 84, socket is TLS: true
dbpill-proxy  | [proxy] Emitting 84 pending bytes to pg-server internal processing.
dbpill-proxy  | [proxy] bindSocket callback triggered for client command: Unknown
dbpill-proxy  | [proxy] bindSocket callback triggered for client command: 112

Any advice?

[fridlundisme]

Also I can access the web GUI, but not the database itself

[mayfer]

what version postgres server are you running?

i always suspected the proxy may not be universal

try matching the pgwire lib version to something that better matches your postgres version

[bodonisystems]

I have a similar problem where the proxy stops at the same place, with the same log entry at the end . I'm using PostgreSQL 16.3. I've tried SSL verify-full and disable and psql for testing. The connection string works perfectly to my real database. Once I try and connect, the web page does not load any more. The sql command never finishes and no error is shown.

[bodonisystems]

I've tried the PostgreSQL 18 app and everything is working ok

[mayfer]

that's good to know!

also i just realized i was wrong to say pgwire, looks like current proxy is using pg-server npm library instead even though both are installed. we are most likely dealing with pg-server's version incompatibilities. a different proxy may need to be used to support a wider range of versions.

[debjan]

same here:

❯ psql --version
psql (PostgreSQL) 18.0 (Ubuntu 18.0-1.pgdg22.04+3)

that's for cli while the db server is 17:

 PostgreSQL 17.6 (Ubuntu 17.6-2.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0, 64-bit

[NickLin910221]

@mayfer Same problem here, whether have Postgresql version limit?