starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-07-16 05:53:57 +03:00
Code Issues 396 Packages Projects Releases 21 Wiki Activity

[Bug]: No connection to server #539

New Issue
Open
opened 2026-02-04 20:17:21 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-04 20:17:21 +03:00
Owner
Copy Link

Originally created by @ryshi on GitHub (Jun 28, 2024).

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
Screenshot 2024-06-28 at 16 04 43

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.

Originally created by @ryshi on GitHub (Jun 28, 2024). ### 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 <img width="440" alt="Screenshot 2024-06-28 at 16 04 43" src="https://github.com/plankanban/planka/assets/1818419/4710b6f2-113c-42ce-b5bb-95de303101ce"> ### 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.
OVERLORD commented 2026-02-04 20:17:26 +03:00
Author
Owner
Copy Link

@daniel-hiller commented on GitHub (Jul 14, 2024):

Is the container crashing?
check with docker compose logs

Whats about the proxy logs?

@daniel-hiller commented on GitHub (Jul 14, 2024): Is the container crashing? check with `docker compose logs` Whats about the proxy logs?
OVERLORD commented 2026-02-04 20:17:29 +03:00
Author
Owner
Copy Link

@ryshi commented on GitHub (Jul 15, 2024):

it works fine on web except the warning

there's no error in proxy logs

/app/node_modules/.pnpm/pg@8.11.0/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/pg@8.11.0/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/pg@8.11.0/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
@ryshi commented on GitHub (Jul 15, 2024): it works fine on web except the warning there's no error in proxy logs ``` /app/node_modules/.pnpm/pg@8.11.0/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/pg@8.11.0/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/pg@8.11.0/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 ```
OVERLORD commented 2026-02-04 20:17:33 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Jul 15, 2024):

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.

@meltyshev commented on GitHub (Jul 15, 2024): 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.
OVERLORD commented 2026-02-04 20:17:48 +03:00
Author
Owner
Copy Link

@ryshi commented on GitHub (Jul 17, 2024):

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.

@ryshi commented on GitHub (Jul 17, 2024): 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.
OVERLORD commented 2026-02-04 20:17:57 +03:00
Author
Owner
Copy Link

@JoeKer1 commented on GitHub (Jul 22, 2024):

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.

@JoeKer1 commented on GitHub (Jul 22, 2024): 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](https://medium.com/johnjjung/how-to-use-gcp-loadbalancer-with-websockets-on-kubernetes-using-services-ingresses-and-backend-16a5565e4702) for the websocket connections with the GCP Ingress class.
OVERLORD commented 2026-02-04 20:18:01 +03:00
Author
Owner
Copy Link

@ryshi commented on GitHub (Aug 23, 2024):

websocket throws timeout continuously
image

@ryshi commented on GitHub (Aug 23, 2024): websocket throws timeout continuously <img width="967" alt="image" src="https://github.com/user-attachments/assets/b76b7d51-0f53-4cdf-b9f0-d49f349dc0a9">
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#539
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?