When use Nginx remote can't open URL but host does.
Description
I have:
A host with IP 192.168.255.107 which is runing Nginx server.
B host with IP 192.168.2.202 which is running ollama(not docker) and open-webui in docker container.
C host with IP 192.168.255.106 is browser host.
A can ping B for sure.
After I run cmd docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main
I can normally open URL http://192.168.2.202:3000/ in host C.
docker logs file:(forget the IP following, I just want to mean it work.)
INFO: 192.168.102.98:24443 - "GET / HTTP/1.1" 200 OK
INFO: 192.168.102.98:24443 - "GET /_app/immutable/entry/start.b68f6fa2.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24444 - "GET /_app/immutable/chunks/scheduler.7238b518.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24446 - "GET /_app/immutable/chunks/index.6bf40fed.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24445 - "GET /_app/immutable/chunks/singletons.a849dcbe.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24447 - "GET /_app/immutable/entry/app.bdf6dbc1.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24448 - "GET /_app/immutable/chunks/preload-helper.a4192956.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24443 - "GET /logo.svg HTTP/1.1" 200 OK
But I can't normally open URL http://example:port/llama/ in host C. ('example:port' is my Domain name and nginx listen port )
Like this but nothing:
and this time the docker log just but other:
INFO: 192.168.102.98:24488 - "GET /auth/ HTTP/1.1" 200 OK
and nginx call a err like:
2024/05/09 14:01:11 [error] 1545323#1545323: *8 open() "/usr/share/nginx/html/_app/immutable/chunks/index.6bf40fed.js" failed (2: No such file or directory), client: IP, server: example, request: "GET /_app/immutable/chunks/index.6bf40fed.js HTTP/1.1", host: "example:port", referrer: "http://example:port/llama/"
2024/05/09 14:01:11 [error] 1545323#1545323: *6 open() "/usr/share/nginx/html/_app/immutable/chunks/preload-helper.a4192956.js" failed (2: No such file or directory), client: IP, server: example, request: "GET /_app/immutable/chunks/preload-helper.a4192956.js HTTP/1.1", host: "example:port", referrer: "http://example:port/llama/
[yes ] I have read and followed all the instructions provided in the README.md.
[yes ] I am on the latest version of both Open WebUI and Ollama.
[yes ] I have included the browser console logs.
[yes ] I have included the Docker container logs.
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
Originally created by @YealKio on GitHub (May 9, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/2144
# Bug Report
When use Nginx remote can't open URL but host does.
## Description
I have:
A host with IP 192.168.255.107 which is runing Nginx server.
B host with IP 192.168.2.202 which is running ollama(not docker) and open-webui in docker container.
C host with IP 192.168.255.106 is browser host.
A can ping B for sure.
After I run cmd
`docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main`
I can normally open URL http://192.168.2.202:3000/ in host C.
docker logs file:(forget the IP following, I just want to mean it work.)
```
INFO: 192.168.102.98:24443 - "GET / HTTP/1.1" 200 OK
INFO: 192.168.102.98:24443 - "GET /_app/immutable/entry/start.b68f6fa2.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24444 - "GET /_app/immutable/chunks/scheduler.7238b518.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24446 - "GET /_app/immutable/chunks/index.6bf40fed.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24445 - "GET /_app/immutable/chunks/singletons.a849dcbe.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24447 - "GET /_app/immutable/entry/app.bdf6dbc1.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24448 - "GET /_app/immutable/chunks/preload-helper.a4192956.js HTTP/1.1" 200 OK
INFO: 192.168.102.98:24443 - "GET /logo.svg HTTP/1.1" 200 OK
```
But I can't normally open URL http://example:port/llama/ in host C. ('example:port' is my Domain name and nginx listen port )
Like this but nothing:
and this time the docker log just but other:
```
INFO: 192.168.102.98:24488 - "GET /auth/ HTTP/1.1" 200 OK
```
and nginx call a err like:
```
2024/05/09 14:01:11 [error] 1545323#1545323: *8 open() "/usr/share/nginx/html/_app/immutable/chunks/index.6bf40fed.js" failed (2: No such file or directory), client: IP, server: example, request: "GET /_app/immutable/chunks/index.6bf40fed.js HTTP/1.1", host: "example:port", referrer: "http://example:port/llama/"
2024/05/09 14:01:11 [error] 1545323#1545323: *6 open() "/usr/share/nginx/html/_app/immutable/chunks/preload-helper.a4192956.js" failed (2: No such file or directory), client: IP, server: example, request: "GET /_app/immutable/chunks/preload-helper.a4192956.js HTTP/1.1", host: "example:port", referrer: "http://example:port/llama/
```
A's nginx.conf like:
```
location /llama/ {
proxy_pass http://192.168.2.202:3000/;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
```
I hope guys can give me some ideas to get rid of confusion
**Bug Summary:**
[Provide a brief but clear summary of the bug]
**Steps to Reproduce:**
[Outline the steps to reproduce the bug. Be as detailed as possible.]
**Expected Behavior:**
[Describe what you expected to happen.]
**Actual Behavior:**
[Describe what actually happened.]
## Environment
- **Open WebUI Version:** [e.g., 0.1.120]
- **Ollama (if applicable):** [e.g., 0.1.30, 0.1.32-rc1]
- **Operating System:** [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04]
- **Browser (if applicable):** [e.g., Chrome 100.0, Firefox 98.0]
## Reproduction Details
**Confirmation:**
- [yes ] I have read and followed all the instructions provided in the README.md.
- [yes ] I am on the latest version of both Open WebUI and Ollama.
- [yes ] I have included the browser console logs.
- [yes ] I have included the Docker container logs.
## Logs and Screenshots
**Browser Console Logs:**
[Include relevant browser console logs, if applicable]
**Docker Container Logs:**
[Include relevant Docker container logs, if applicable]
**Screenshots (if applicable):**
[Attach any relevant screenshots to help illustrate the issue]
## Installation Method
[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]
## Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
## Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @YealKio on GitHub (May 9, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/2144
Bug Report
When use Nginx remote can't open URL but host does.
Description
I have:
A host with IP 192.168.255.107 which is runing Nginx server.
B host with IP 192.168.2.202 which is running ollama(not docker) and open-webui in docker container.
C host with IP 192.168.255.106 is browser host.
A can ping B for sure.
After I run cmd
docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:mainI can normally open URL http://192.168.2.202:3000/ in host C.
docker logs file:(forget the IP following, I just want to mean it work.)
But I can't normally open URL http://example:port/llama/ in host C. ('example:port' is my Domain name and nginx listen port )
Like this but nothing:
and this time the docker log just but other:
and nginx call a err like:
A's nginx.conf like:
I hope guys can give me some ideas to get rid of confusion
Bug Summary:
[Provide a brief but clear summary of the bug]
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Expected Behavior:
[Describe what you expected to happen.]
Actual Behavior:
[Describe what actually happened.]
Environment
Open WebUI Version: [e.g., 0.1.120]
Ollama (if applicable): [e.g., 0.1.30, 0.1.32-rc1]
Operating System: [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04]
Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!