Nginx Proxy Manager doesn't work with planka 2.0.0-rc.3 #752

Closed
opened 2026-02-04 21:12:42 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @velizarofff on GitHub (Jul 8, 2025).

Hello

I installed planka 2.0.0-rc.3 via a docker image. It is available locally: 192.168.4.108:3000. Edited docker-compose and enabled the option:

  • TRUST_PROXY=true, configured reverse_proxy for the domain planka.example.com in nginx proxy manager (enabled the web_socket setting), but when trying to log in, planka does not load, and the error in the console is:
    index-Crmnsq57.js:464 WebSocket connection to 'wss://planka.example.com/socket.io/?__sails_io_sdk_version=1.2.1&__sails_io_sdk_platform=node&__sails_io_sdk_language=javascript&EIO=3&transport=websocket' failed:

At the same time, with docker inspect planka-planka-1I don't see the - TRUST_PROXY option.

Originally created by @velizarofff on GitHub (Jul 8, 2025). Hello I installed planka 2.0.0-rc.3 via a docker image. It is available locally: 192.168.4.108:3000. Edited docker-compose and enabled the option: - TRUST_PROXY=true, configured reverse_proxy for the domain planka.example.com in nginx proxy manager (enabled the web_socket setting), but when trying to log in, planka does not load, and the error in the console is: index-Crmnsq57.js:464 WebSocket connection to 'wss://planka.example.com/socket.io/?__sails_io_sdk_version=1.2.1&__sails_io_sdk_platform=node&__sails_io_sdk_language=javascript&EIO=3&transport=websocket' failed: At the same time, with docker inspect planka-planka-1I don't see the - TRUST_PROXY option.
Author
Owner

@velizarofff commented on GitHub (Jul 8, 2025):

I did: docker compose up -d. I'm sorry I'm new to the docker thing, the TRUE_PROXY option is now true. But it still doesn't work. I tried on different browser versions: chrome, firefox the effect is the same. After login there is no loading and the error described above.

@velizarofff commented on GitHub (Jul 8, 2025): I did: docker compose up -d. I'm sorry I'm new to the docker thing, the TRUE_PROXY option is now true. But it still doesn't work. I tried on different browser versions: chrome, firefox the effect is the same. After login there is no loading and the error described above.
Author
Owner

@meltyshev commented on GitHub (Jul 8, 2025):

Hi! It's hard to say exactly what might be wrong without seeing all the configuration files and environment variables.

A common issue is an incorrectly set BASE_URL, which can cause the connection origin check to fail. In your case, it should be BASE_URL=https://planka.example.com.

Also, make sure the socket connection is properly forwarded at the Nginx level. You can refer to the official documentation here: https://docs.planka.cloud/docs/configuration/reverse-proxy/nginx/.

@meltyshev commented on GitHub (Jul 8, 2025): Hi! It's hard to say exactly what might be wrong without seeing all the configuration files and environment variables. A common issue is an incorrectly set `BASE_URL`, which can cause the connection origin check to fail. In your case, it should be `BASE_URL=https://planka.example.com`. Also, make sure the socket connection is properly forwarded at the Nginx level. You can refer to the official documentation here: https://docs.planka.cloud/docs/configuration/reverse-proxy/nginx/.
Author
Owner

@velizarofff commented on GitHub (Jul 8, 2025):

Hello!

Indeed, setting the BASE_URL helped, I thought it should be the local address and not the one that NPM proxies.

@velizarofff commented on GitHub (Jul 8, 2025): Hello! Indeed, setting the BASE_URL helped, I thought it should be the local address and not the one that NPM proxies.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#752