NEXT_PUBLIC_BASE_PATH not work with docker

[YealKio]

💻 Operating System

Ubuntu

📦 Environment

Docker

🌐 Browser

Chrome

🐛 Bug Description

Chat-lobe + ollama +nginx not work.
Chat-lobe can not init in the first time, like nginx SUBPATH thing, not sure, see my step please.

BTW, ollama server and Chat-lobe server are not the same device, but in LAN.
I can run OPEN-WEBUI + OLLAMA + NGINX without problem.

🚦 Expected Behavior

Even can not init.

📷 Recurrence Steps

Chat lobe run with docker:
sudo docker run -d -p 3210:3210 -e OLLAMA_PROXY_URL=http://192.168.2.202:11434 -e NEXT_PUBLIC_BASE_PATH=/chat-lobe lobehub/lobe-chat
this my nginx conf file:

upstream chat-lobe {
   server 127.0.0.1:3210;
}

    location  /chat-lobe/ {
         proxy_pass http://chat-lobe/;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
         access_log /var/log/nginx/chat-lobe.access.log;
         error_log /var/log/nginx/chat-lobe.error.log;
    }

when I open my.nas.com:port/chat-lobe, the Chrome just show:

The website console like:

Can not find any thing, and one of Request URL like: Request URL: http://my.nas.com:port/_next/static/chunks/webpack-72cd2e677540060b.js

It look like NEXT_PUBLIC_BASE_PATH not work as expected, please help!

📝 Additional Information

Ollama server and Chat-lobe server are not the same device, but in LAN.

[lobehubbot]

👀 @YealKio

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[arvinxx]

NEXT_PUBLIC_BASE_PATH is not working with docker. You need to build it with NEXT_PUBLIC_ env by yourself

[YealKio]

same as

nginx conf

upstream chat-lobe {
   server 127.0.0.1:3210;
}

    location  /chat-lobe/ {
         proxy_pass http://chat-lobe/;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
         access_log /var/log/nginx/chat-lobe.access.log;
         error_log /var/log/nginx/chat-lobe.error.log;
    }

Browser can not load noarmlly.

[arvinxx]

@YealKio do you try

upstream chat-lobe {
   server 127.0.0.1:3210;
}

    location / {
         proxy_pass http://chat-lobe/;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
         access_log /var/log/nginx/chat-lobe.access.log;
         error_log /var/log/nginx/chat-lobe.error.log;
    }

and then visit /chat-lobe ?

[YealKio]

Hi @arvinxx ! Actually it work just visit http://myweb:port/, I use offical docker image. So that's why I say NEXT_PUBLIC_BASE_PATH didn't work in above issues.#2528 (reply in thread)

[YealKio]

The question is how can I visit chat-lobe in a web sub-path. Chat-lobe is a amazing thing and the only obstacles between us is the NEXT_PUBLIC_BASE_PATH, so any other messages can I upload to help us deal with it, I am willing to do.

[arvinxx]

@YealKio After you build with docker docker build , do you just try with ip:port/basePath ? It should make sure it's not the issue with nginx

[LouisCan]

This is a bug; the parameter isn't taking effect.

[arvinxx]

it's hard to maintain this feature. I will remove it soon, please don't use this parameter