plankanban / planka

The realtime kanban board for workgroups built with React and Redux.
https://planka.app
GNU Affero General Public License v3.0
6.91k stars 661 forks source link

Websocket connection error #754

Open Oscar-Charlie opened 1 month ago

Oscar-Charlie commented 1 month ago

Hello together, We have setup planka in our company via docker on our synology. Configuration is as follows:


version: '3.9' services: planka: image: ghcr.io/plankanban/planka:latest container_name: Planka command: > bash -c "for i in seq 1 30; do ./start.sh && s=$$? && break || s=$$?; echo \"Tried $$i times. Waiting 5 seconds...\"; sleep 5; done; (exit $$s)" restart: on-failure:5 volumes:

Nevertheless one of our client just sees the loading screen from the startup an can't get any further. From the google debug consule they get an websocket error (sails.io) Fehler_Planka2

Do you have any advice? We are loving planka, but we need to have to make it work for all of our clients. Thank you in advance, Matthias

meltyshev commented 1 month ago

Hi! It seems that your settings look correct. Please make sure that BASE_URL is exactly the same as the address you specify in your browser and also starts with http:// or https://. It's hard for me to suggest solutions to possible server-side problems, as I'm not very familiar with it, but I'll try to find a way to display an error text in the server logs.

meltyshev commented 1 month ago

Please try to change command in docker-compose.yml from

command: >
  bash -c
    "for i in `seq 1 30`; do
      ./start.sh &&
      s=$$? && break || s=$$?;
      echo \"Tried $$i times. Waiting 5 seconds...\";
      sleep 5;
    done; (exit $$s)"

to

command: bash -c "export NODE_ENV=development && set -e && node db/init.js && node app.js"

With this you'll be able to run Planka in development mode and see all debug messages.

Then try to open Planka in a browser and get that socket connection error. Check the logs on the server, there should be something like "debug: A socket was rejected via the ...". Also, there may not be any error there, but then the problem is somewhere in the proxy server settings.