[Bug]: No connection to server

[ryshi]

Where is the problem occurring?

I encountered the problem while interacting with the server (Backend)

What browsers are you seeing the problem on?

Chrome

Current behaviour

app deployed through docker-compose.yml, everything seems good but error message occurs frequently

Desired behaviour

No response

Steps to reproduce

1. edit config(base_url) & docker compose start
2. apisix gateway add service & router with websocket on
3. login

Other information

I tried to add some test data, it run as desired, but error message poped up every few seconds.

[daniel-hiller]

Is the container crashing?
check with docker compose logs

Whats about the proxy logs?

[ryshi]

it works fine on web except the warning

there's no error in proxy logs

/app/node_modules/.pnpm/[email protected]/node_modules/pg/lib/client.js:132
      const error = this._ending ? new Error('Connection terminated') : new Error('Connection terminated unexpectedly')
                                                                        ^
Error: Connection terminated unexpectedly
    at Connection.<anonymous> (/app/node_modules/.pnpm/[email protected]/node_modules/pg/lib/client.js:132:73)
    at Object.onceWrapper (node:events:631:28)
    at Connection.emit (node:events:517:28)
    at Socket.<anonymous> (/app/node_modules/.pnpm/[email protected]/node_modules/pg/lib/connection.js:63:12)
    at Socket.emit (node:events:517:28)
    at TCP.<anonymous> (node:net:350:12)

Node.js v18.20.3

(process:19): VIPS-WARNING **: 02:08:44.587: threads clipped to 1024

[meltyshev]

We had something similar with Postgres recently, it kept restarting and dropping all connections. Updating Postgres helped us. But in your case it might be something else.

[ryshi]

Thanks for your information, I did use a remote PostgreSQL 16.2. Maybe there are the same problem.

We had something similar with Postgres recently, it kept restarting and dropping all connections. Updating Postgres helped us. But in your case it might be something else.

[JoeKer1]

I'm getting this as well, but I'm running in k8s and using a postgres 15 cloudsql server.

In my case I needed to add a backend config to add some timeouts for the websocket connections with the GCP Ingress class.

[ryshi]

websocket throws timeout continuously