[Bug]: Open white screen after docker deployment #553

New Issue

OVERLORD · 2026-02-04T20:20:17+03:00

OVERLORD commented

2026-02-04 20:20:17 +03:00

Originally created by @tl211211211 on GitHub (Aug 12, 2024).

Where is the problem occurring?

None

What browsers are you seeing the problem on?

No response

Current behaviour

After docker local intranet deployment through port forwarding mapping to the public network can not be used normally, open the white screen. The main reason is that the following two files get the address for the intranet address.
http://localhost:3000/static/js/main.780b7d6d.js
http://localhost:3000/static/css/main.af55c8d0.css

Desired behaviour

No response

Steps to reproduce

Deploying with docker in an intranet environment
Use nat port mapping to map port 3000 on the intranet server to port 63000 on the public network.
Using public address:63000 to access opens a white screen

Other information

No response

Originally created by @tl211211211 on GitHub (Aug 12, 2024). ### Where is the problem occurring? None ### What browsers are you seeing the problem on? _No response_ ### Current behaviour After docker local intranet deployment through port forwarding mapping to the public network can not be used normally, open the white screen. The main reason is that the following two files get the address for the intranet address. http://localhost:3000/static/js/main.780b7d6d.js http://localhost:3000/static/css/main.af55c8d0.css ### Desired behaviour _No response_ ### Steps to reproduce Deploying with docker in an intranet environment Use nat port mapping to map port 3000 on the intranet server to port 63000 on the public network. Using public address:63000 to access opens a white screen ### Other information _No response_

OVERLORD commented

2026-02-04 20:20:23 +03:00

@meltyshev commented on GitHub (Aug 12, 2024):

Hi! It looks like you haven't specified BASE_URL, or you've set it to BASE_URL=http://localhost:3000. The BASE_URL should match the exact address you use in your browser to connect to Planka. In your case, it should be BASE_URL=http://PUBLIC_ADDRESS:63000.

@meltyshev commented on GitHub (Aug 12, 2024): Hi! It looks like you haven't specified `BASE_URL`, or you've set it to `BASE_URL=http://localhost:3000`. The `BASE_URL` should match the exact address you use in your browser to connect to Planka. In your case, it should be `BASE_URL=http://PUBLIC_ADDRESS:63000`.

OVERLORD commented

2026-02-04 20:20:33 +03:00

@tl211211211 commented on GitHub (Aug 12, 2024):

Hi! It looks like you haven't specified BASE_URL, or you've set it to BASE_URL=http://localhost:3000. The BASE_URL should match the exact address you use in your browser to connect to Planka. In your case, it should be BASE_URL=http://PUBLIC_ADDRESS:63000.

No, I may not have made myself clear, I set BASE_URL=172.16.1.22:3000,and mapped the intranet server port to the public address 63000 via port mapping.
When I use http://172.16.1.22:3000 on the intranet it is accessed fine, but when I use public:63000 it is not accessed properly. Those two files get the address as local IP.
http://172.16.1.22:3000/static/js/main.780b7d6d.js
http://172.16.1.22:3000/static/css/main.af55c8d0.css

@tl211211211 commented on GitHub (Aug 12, 2024): > Hi! It looks like you haven't specified `BASE_URL`, or you've set it to `BASE_URL=http://localhost:3000`. The `BASE_URL` should match the exact address you use in your browser to connect to Planka. In your case, it should be `BASE_URL=http://PUBLIC_ADDRESS:63000`. No, I may not have made myself clear, I set BASE_URL=172.16.1.22:3000,and mapped the intranet server port to the public address 63000 via port mapping. When I use http://172.16.1.22:3000 on the intranet it is accessed fine, but when I use public:63000 it is not accessed properly. Those two files get the address as local IP. http://172.16.1.22:3000/static/js/main.780b7d6d.js http://172.16.1.22:3000/static/css/main.af55c8d0.css

OVERLORD commented

2026-02-04 20:20:36 +03:00

@meltyshev commented on GitHub (Aug 12, 2024):

Ah, got it. Unfortunately, we don't currently support specifying multiple addresses. However, I think this feature should be added, I'll try to come up with something.

Related: #481, #530

@meltyshev commented on GitHub (Aug 12, 2024): Ah, got it. Unfortunately, we don't currently support specifying multiple addresses. However, I think this feature should be added, I'll try to come up with something. Related: #481, #530

OVERLORD commented

2026-02-04 20:20:40 +03:00

@ashap5 commented on GitHub (Oct 7, 2024):

Looking forward to this feature. Any idea when it might be available?

@ashap5 commented on GitHub (Oct 7, 2024): Looking forward to this feature. Any idea when it might be available?

OVERLORD referenced this issue

2026-02-04 21:45:45 +03:00

[PR #553] [CLOSED] merged from master #1038

Sign in to join this conversation.