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

Infinite loading screen #137

New Issue
Closed
opened 2026-02-04 17:26:59 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-04 17:26:59 +03:00
Owner
Copy Link

Originally created by @mfnalex on GitHub (Oct 7, 2021).

After installing via docker-compose, I cannot login using the demo credentials - the loading animation just keeps repeating forever and ever. The logs are showing nothing.

Originally created by @mfnalex on GitHub (Oct 7, 2021). After installing via docker-compose, I cannot login using the demo credentials - the loading animation just keeps repeating forever and ever. The logs are showing nothing.
OVERLORD commented 2026-02-04 17:27:13 +03:00
Author
Owner
Copy Link

@Syndamia commented on GitHub (Oct 7, 2021):

Could be a duplicate of #135 and #111. Are you sure that the BASE_URL inside docker-compose.yml is the same as the address you're trying to host it at (better explained in https://github.com/plankanban/planka/issues/158#issuecomment-933566242)?

@Syndamia commented on GitHub (Oct 7, 2021): Could be a duplicate of #135 and #111. Are you sure that the `BASE_URL` inside `docker-compose.yml` is the same as the address you're trying to host it at (better explained in https://github.com/plankanban/planka/issues/158#issuecomment-933566242)?
OVERLORD commented 2026-02-04 17:27:18 +03:00
Author
Owner
Copy Link

@mfnalex commented on GitHub (Oct 8, 2021):

the BASE_URL is set correctly to the public domain name, however I'm using a reverse proxy to localhost. It works fine without the proxy, but... that's not a vialable solution. Are there any headers the proxy must keep to make it work?

@mfnalex commented on GitHub (Oct 8, 2021): the BASE_URL is set correctly to the public domain name, however I'm using a reverse proxy to localhost. It works fine without the proxy, but... that's not a vialable solution. Are there any headers the proxy must keep to make it work?
OVERLORD commented 2026-02-04 17:27:21 +03:00
Author
Owner
Copy Link

@loranger commented on GitHub (Oct 11, 2021):

I had difficulties to make planka work using docker behind my traefik reverse-proxy, but now everything works flawlessly.

I did a quick summary here. I hope it would help

@loranger commented on GitHub (Oct 11, 2021): I had difficulties to make planka work using docker behind my traefik reverse-proxy, but now everything works flawlessly. I did a [quick summary here](https://github.com/plankanban/planka/issues/157#issuecomment-920649307). I hope it would help
OVERLORD commented 2026-02-04 17:27:29 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 21, 2021):

Having the correct value for the BASE_URL is very important. Most likely as in the other issues linked by @Syndamia your browser can't connect to the websocket. You can verify this by checking your browser's console logs.

If you're using a reverse proxy and it handles terminating TLS, then you should have the BASE_URL environment variable as https://domain.tld.

What do you have it set to currently @mfnalex?

In my case, I had to alter the trustProxy value. Please see PR #164 which is now merged 🥳 and #163.

@dbrennand commented on GitHub (Oct 21, 2021): Having the correct value for the `BASE_URL` is very important. Most likely as in the other issues linked by @Syndamia your browser can't connect to the websocket. You can verify this by checking your browser's console logs. If you're using a reverse proxy and it handles terminating TLS, then you should have the `BASE_URL` environment variable as `https://domain.tld`. What do you have it set to currently @mfnalex? In my case, I had to alter the `trustProxy` value. Please see PR #164 which is now merged 🥳 and #163.
OVERLORD commented 2026-02-04 17:27:32 +03:00
Author
Owner
Copy Link

@mfnalex commented on GitHub (Oct 21, 2021):

Sorry, I currently don't have planka installed anymore. I'll try again on my testing server when I have time and will report back then. Feel free to close this issue for now.

@mfnalex commented on GitHub (Oct 21, 2021): Sorry, I currently don't have planka installed anymore. I'll try again on my testing server when I have time and will report back then. Feel free to close this issue for now.
OVERLORD commented 2026-02-04 17:27:42 +03:00
Author
Owner
Copy Link

@raimundomartins commented on GitHub (Jan 29, 2022):

I have the same issue, BASE_URL=https://planka.foo.tld is copy-pasted into browser, and TRUST_PROXY=1. I'm using caddy as a reverse proxy (not docker) with a config of the sorts

planka.foo.tld {
        reverse_proxy localhost:8004
}

where 8004 is the port I set in the docker-compose.yml.

EDIT: So, I have another server that is exposed to the internet and I don't have this issue. I guess I can't run planka if I'm behind NAT?

@raimundomartins commented on GitHub (Jan 29, 2022): I have the same issue, `BASE_URL=https://planka.foo.tld` is copy-pasted into browser, and `TRUST_PROXY=1`. I'm using caddy as a reverse proxy (not docker) with a config of the sorts ``` planka.foo.tld { reverse_proxy localhost:8004 } ``` where 8004 is the port I set in the docker-compose.yml. EDIT: So, I have another server that is exposed to the internet and I don't have this issue. I guess I can't run planka if I'm behind NAT?
OVERLORD commented 2026-02-04 17:27:49 +03:00
Author
Owner
Copy Link

@noriakisana commented on GitHub (Feb 28, 2022):

when you are using an proxy, please remove the port. (worked for me with traefik). if you want, i can send you my docker-compose.yml later :D

@noriakisana commented on GitHub (Feb 28, 2022): when you are using an proxy, please remove the port. (worked for me with traefik). if you want, i can send you my docker-compose.yml later :D
OVERLORD commented 2026-02-04 17:27:51 +03:00
Author
Owner
Copy Link

@Alumniminium commented on GitHub (Apr 13, 2022):

client/src/constants/Config.js has a fked if statement that makes websocket requests go to localhost:1337, fix the URL there or set it in ENV (REACT_APP_SERVER_BASE_URL)

@Alumniminium commented on GitHub (Apr 13, 2022): `client/src/constants/Config.js` has a fked if statement that makes websocket requests go to localhost:1337, fix the URL there or set it in ENV (REACT_APP_SERVER_BASE_URL)
OVERLORD commented 2026-02-04 17:27:59 +03:00
Author
Owner
Copy Link

@pointjalta commented on GitHub (Jul 13, 2022):

Has anyone discovered what issue causing the problem? I just can't find a way yet on how to fi this ...

@pointjalta commented on GitHub (Jul 13, 2022): Has anyone discovered what issue causing the problem? I just can't find a way yet on how to fi this ...
OVERLORD commented 2026-02-04 17:28:20 +03:00
Author
Owner
Copy Link

@Giorgio-Germani commented on GitHub (Aug 11, 2022):

Here is my docker config that worked in combination with portainer and nginx proxy manager:
Make sure you have the https domain set as base_url and websocket enabled in nginx proxy manager.

version: '3'

services:
planka:
image: ghcr.io/plankanban/planka:latest
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: unless-stopped
volumes:
- user-avatars:/app/public/user-avatars
- project-background-images:/app/public/project-background-images
- attachments:/app/private/attachments
ports:
- 3000:1337
environment:
- BASE_URL=https://planka.domain.com
- TRUST_PROXY=0
- DATABASE_URL=postgresql://postgres@postgres/planka
- SECRET_KEY=123randomlygenerated123
depends_on:
- postgres

postgres:
image: postgres:alpine
restart: unless-stopped
volumes:
- db-data:/var/lib/postgresql/data
environment:
- POSTGRES_DB=planka
- POSTGRES_HOST_AUTH_METHOD=trust

volumes:
user-avatars:
project-background-images:
attachments:
db-data:

@Giorgio-Germani commented on GitHub (Aug 11, 2022): Here is my docker config that worked in combination with portainer and nginx proxy manager: Make sure you have the https domain set as base_url and websocket enabled in nginx proxy manager. ---------- version: '3' services: planka: image: ghcr.io/plankanban/planka:latest 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: unless-stopped volumes: - user-avatars:/app/public/user-avatars - project-background-images:/app/public/project-background-images - attachments:/app/private/attachments ports: - 3000:1337 environment: - BASE_URL=https://planka.domain.com - TRUST_PROXY=0 - DATABASE_URL=postgresql://postgres@postgres/planka - SECRET_KEY=123randomlygenerated123 depends_on: - postgres postgres: image: postgres:alpine restart: unless-stopped volumes: - db-data:/var/lib/postgresql/data environment: - POSTGRES_DB=planka - POSTGRES_HOST_AUTH_METHOD=trust volumes: user-avatars: project-background-images: attachments: db-data:
OVERLORD commented 2026-02-04 17:28:26 +03:00
Author
Owner
Copy Link

@frogman544 commented on GitHub (Aug 30, 2022):

Here is my docker config that worked in combination with portainer and nginx proxy manager:

Make sure you have the https domain set as base_url and websocket enabled in nginx proxy manager.

version: '3'

services:

planka:

image: ghcr.io/plankanban/planka:latest

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: unless-stopped

volumes:

  - user-avatars:/app/public/user-avatars

  - project-background-images:/app/public/project-background-images

  - attachments:/app/private/attachments

ports:

  - 3000:1337

environment:

  - BASE_URL=https://planka.domain.com

  - TRUST_PROXY=0

  - DATABASE_URL=postgresql://postgres@postgres/planka

  - SECRET_KEY=123randomlygenerated123

depends_on:

  - postgres

postgres:

image: postgres:alpine

restart: unless-stopped

volumes:

  - db-data:/var/lib/postgresql/data

environment:

  - POSTGRES_DB=planka

  - POSTGRES_HOST_AUTH_METHOD=trust

volumes:

user-avatars:

project-background-images:

attachments:

db-data:

Hey man! Can you also add the nginx part? Cheers!

@frogman544 commented on GitHub (Aug 30, 2022): > Here is my docker config that worked in combination with portainer and nginx proxy manager: > > Make sure you have the https domain set as base_url and websocket enabled in nginx proxy manager. > > ---------- > > > > > > version: '3' > > > > services: > > planka: > > image: ghcr.io/plankanban/planka:latest > > 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: unless-stopped > > volumes: > > - user-avatars:/app/public/user-avatars > > - project-background-images:/app/public/project-background-images > > - attachments:/app/private/attachments > > ports: > > - 3000:1337 > > environment: > > - BASE_URL=https://planka.domain.com > > - TRUST_PROXY=0 > > - DATABASE_URL=postgresql://postgres@postgres/planka > > - SECRET_KEY=123randomlygenerated123 > > depends_on: > > - postgres > > > > postgres: > > image: postgres:alpine > > restart: unless-stopped > > volumes: > > - db-data:/var/lib/postgresql/data > > environment: > > - POSTGRES_DB=planka > > - POSTGRES_HOST_AUTH_METHOD=trust > > > > volumes: > > user-avatars: > > project-background-images: > > attachments: > > db-data: Hey man! Can you also add the nginx part? Cheers!
OVERLORD commented 2026-02-04 17:28:37 +03:00
Author
Owner
Copy Link

@guilhermenovais commented on GitHub (May 7, 2025):

For anyone trying to run this behind Nginx Proxy Manager, make sure you have the Websockets Support option enabled on your Proxy Host

@guilhermenovais commented on GitHub (May 7, 2025): For anyone trying to run this behind Nginx Proxy Manager, make sure you have the Websockets Support option enabled on your Proxy Host
OVERLORD commented 2026-02-04 17:28:44 +03:00
Author
Owner
Copy Link

@danish-mar commented on GitHub (Jul 24, 2025):

Hey! I ran into the same WebSocket connection issue when trying to self-host Planka on my LAN using Docker. The frontend loaded perfectly, but WebSockets kept failing with:

NS_ERROR_WEBSOCKET_CONNECTION_REFUSED

After digging into it, I found that the culprit was the SOCKET_ONLY_ALLOW_ORIGINS restriction inside Sails.js. By default, it only allows localhost, which silently blocks socket connections from other origins like 192.168.x.x.

To fix it, I updated my docker-compose.yml to include this in the environment block:

- BASE_URL=http://192.168.1.72:7543
- DATABASE_URL=postgresql://postgres@postgres/planka
- SOCKET_ONLY_ALLOW_ORIGINS=http://localhost:7543,http://192.168.1.72:7543

This immediately fixed the WebSocket connection issue. It might help to add a quick note about SOCKET_ONLY_ALLOW_ORIGINS in the setup docs, especially for people deploying on home or internal networks.

Thanks for the awesome project! 💜

@danish-mar commented on GitHub (Jul 24, 2025): Hey! I ran into the same WebSocket connection issue when trying to self-host Planka on my LAN using Docker. The frontend loaded perfectly, but WebSockets kept failing with: ``` NS_ERROR_WEBSOCKET_CONNECTION_REFUSED ``` After digging into it, I found that the culprit was the `SOCKET_ONLY_ALLOW_ORIGINS` restriction inside Sails.js. By default, it only allows `localhost`, which silently blocks socket connections from other origins like `192.168.x.x`. To fix it, I updated my `docker-compose.yml` to include this in the `environment` block: ```yaml - BASE_URL=http://192.168.1.72:7543 - DATABASE_URL=postgresql://postgres@postgres/planka - SOCKET_ONLY_ALLOW_ORIGINS=http://localhost:7543,http://192.168.1.72:7543 ``` This immediately fixed the WebSocket connection issue. It might help to add a quick note about `SOCKET_ONLY_ALLOW_ORIGINS` in the setup docs, especially for people deploying on home or internal networks. Thanks for the awesome project! 💜
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#137
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?