[Bug]: Blank after logged-in as Admin User #878

Closed
opened 2026-02-04 21:32:15 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @dionalfa on GitHub (Dec 11, 2025).

Where is the problem occurring?

I encountered the problem while using the application (Frontend)

What browsers are you seeing the problem on?

Chrome

Current behavior

Hi, I just did a fresh install on my Ubuntu 22 following this tutorial: https://docs.planka.cloud/docs/installation/docker/production-version#docker-compose

After logging in using the admin account, there are websocket errors in the console.

Image

Desired behavior

No response

Steps to reproduce

I just followed this installation guides: https://docs.planka.cloud/docs/installation/docker/production-version#docker-compose

Other information

No response

Originally created by @dionalfa on GitHub (Dec 11, 2025). ### Where is the problem occurring? I encountered the problem while using the application (Frontend) ### What browsers are you seeing the problem on? Chrome ### Current behavior Hi, I just did a fresh install on my Ubuntu 22 following this tutorial: https://docs.planka.cloud/docs/installation/docker/production-version#docker-compose After logging in using the admin account, there are websocket errors in the console. <img width="1571" height="451" alt="Image" src="https://github.com/user-attachments/assets/562ce330-9174-47bf-bee5-a4fbdf6468a1" /> ### Desired behavior _No response_ ### Steps to reproduce I just followed this installation guides: https://docs.planka.cloud/docs/installation/docker/production-version#docker-compose ### Other information _No response_
Author
Owner

@meltyshev commented on GitHub (Dec 11, 2025):

Hey! To understand why this is happening, we need to see your Docker Compose configuration. But I can already guess that the issue might be related to one of the following:

  • The BASE_URL value - in your case, it should be set to http://192.168.110.111:3000 (the same address you enter in your browser). Otherwise, the websocket connection will fail due to an untrusted origin.

  • Incorrect proxy server configuration (if you're using a proxy) - it must handle websocket connections and pass them through to the PLANKA process.

@meltyshev commented on GitHub (Dec 11, 2025): Hey! To understand why this is happening, we need to see your Docker Compose configuration. But I can already guess that the issue might be related to one of the following: - The `BASE_URL` value - in your case, it should be set to `http://192.168.110.111:3000` (the same address you enter in your browser). Otherwise, the websocket connection will fail due to an untrusted origin. - Incorrect proxy server configuration (if you're using a proxy) - it must handle websocket connections and pass them through to the PLANKA process.
Author
Owner

@dionalfa commented on GitHub (Dec 12, 2025):

Hi @meltyshev,

My bad, I forgot to input the port in the BASE_URL. Now the issue has been resolved.

Thanks

@dionalfa commented on GitHub (Dec 12, 2025): Hi @meltyshev, My bad, I forgot to input the port in the `BASE_URL`. Now the issue has been resolved. Thanks
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#878