Originally created by @Jiayou-Chao on GitHub (Jul 11, 2024).
Bug Report
Description
Bug Summary:
Unable to connect Open WebUI to the locally running oneapi service.
Steps to Reproduce:
Deploy oneapi on localhost:3000 using Docker.
Deploy open-webui using the command docker run -d -p 3001:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main.
Attempt to connect open-webui to oneapi on localhost.
Expected Behavior:
Open WebUI should connect to the oneapi service running on localhost:3000 without any issues.
Actual Behavior:
Open WebUI fails to connect to the locally running oneapi.
Environment
Open WebUI Version: v0.3.8
Operating System: Linux 5.15.146.1-microsoft-standard-WSL2
Reproduction Details
Confirmation:
I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
Logs and Screenshots
Browser Console Logs:
+layout.svelte:88 Backend config: Object
+layout.svelte:125 user-count Object
+layout.svelte:130 usage Object
+layout.svelte:119 connected
index.ts:64 Array(0)
Chat.svelte:177 Message received from iframe:
:3001/openai/models/0:1
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Connections.svelte:156 Uncaught (in promise) OpenAI: Network Problem
:3001/openai/models/0:1
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
index.ts:64 Array(0)
+layout.svelte:69 Wake Lock released
Docker Container Logs:
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Generating WEBUI_SECRET_KEY
Loading WEBUI_SECRET_KEY from .webui_secret_key
USER_AGENT environment variable not set, consider setting it to identify your requests.
INFO: Started server process [1]
INFO: Waiting for application startup.
/app
___ __ __ _ _ _ ___
/ _ \ _ __ ___ _ __ \ \ / /__| |__ | | | |_ _|
| | | | '_ \ / _ \ '_ \ \ \ /\ / / _ \ '_ \| | | || |
| |_| | |_) | __/ | | | \ V V / __/ |_) | |_| || |
\___/| .__/ \___|_| |_| \_/\_/ \___|_.__/ \___/|___|
|_|
v0.3.8 - building the best open-source AI user interface.
https://github.com/open-webui/open-webui
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
Encountered issues related to Docker network configuration and connection errors between Open WebUI and oneapi on localhost. Followed troubleshooting steps from Troubleshooting Guide but issue persists.
Originally created by @Jiayou-Chao on GitHub (Jul 11, 2024).
# Bug Report
## Description
**Bug Summary:**
Unable to connect Open WebUI to the locally running oneapi service.
**Steps to Reproduce:**
1. Deploy oneapi on localhost:3000 using Docker.
2. Deploy open-webui using the command `docker run -d -p 3001:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main`.
3. Attempt to connect open-webui to oneapi on localhost.
**Expected Behavior:**
Open WebUI should connect to the oneapi service running on localhost:3000 without any issues.
**Actual Behavior:**
Open WebUI fails to connect to the locally running oneapi.
## Environment
- **Open WebUI Version:** v0.3.8
- **Operating System:** Linux 5.15.146.1-microsoft-standard-WSL2
## Reproduction Details
**Confirmation:**
- [X] I have read and followed all the instructions provided in the README.md.
- [X] I am on the latest version of both Open WebUI and Ollama.
- [X] I have included the browser console logs.
- [X] I have included the Docker container logs.
## Logs and Screenshots
**Browser Console Logs:**
```
+layout.svelte:88 Backend config: Object
+layout.svelte:125 user-count Object
+layout.svelte:130 usage Object
+layout.svelte:119 connected
index.ts:64 Array(0)
Chat.svelte:177 Message received from iframe:
:3001/openai/models/0:1
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Connections.svelte:156 Uncaught (in promise) OpenAI: Network Problem
:3001/openai/models/0:1
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
index.ts:64 Array(0)
+layout.svelte:69 Wake Lock released
```
**Docker Container Logs:**
```
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Generating WEBUI_SECRET_KEY
Loading WEBUI_SECRET_KEY from .webui_secret_key
USER_AGENT environment variable not set, consider setting it to identify your requests.
INFO: Started server process [1]
INFO: Waiting for application startup.
/app
___ __ __ _ _ _ ___
/ _ \ _ __ ___ _ __ \ \ / /__| |__ | | | |_ _|
| | | | '_ \ / _ \ '_ \ \ \ /\ / / _ \ '_ \| | | || |
| |_| | |_) | __/ | | | \ V V / __/ |_) | |_| || |
\___/| .__/ \___|_| |_| \_/\_/ \___|_.__/ \___/|___|
|_|
v0.3.8 - building the best open-source AI user interface.
https://github.com/open-webui/open-webui
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
```
**Screenshots (if applicable):**

## Installation Method
```
docker run -d -p 3001:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main
```
## Additional Information
Encountered issues related to Docker network configuration and connection errors between Open WebUI and oneapi on localhost. Followed troubleshooting steps from [Troubleshooting Guide](https://github.com/open-webui/open-webui/blob/main/TROUBLESHOOTING.md) but issue persists.
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 @Jiayou-Chao on GitHub (Jul 11, 2024).
Bug Report
Description
Bug Summary:
Unable to connect Open WebUI to the locally running oneapi service.
Steps to Reproduce:
docker run -d -p 3001:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main.Expected Behavior:
Open WebUI should connect to the oneapi service running on localhost:3000 without any issues.
Actual Behavior:
Open WebUI fails to connect to the locally running oneapi.
Environment
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
Docker Container Logs:
Screenshots (if applicable):

Installation Method
Additional Information
Encountered issues related to Docker network configuration and connection errors between Open WebUI and oneapi on localhost. Followed troubleshooting steps from Troubleshooting Guide but issue persists.