[GH-ISSUE #17760] issue: External Ollama API not connecting due to OpenWebUI proxy behavior

GiteaMirror commented

2026-04-20 00:36:26 -05:00

Owner

Originally created by @emash on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17760

Check Existing Issues

I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

0.6.31

Ollama Version (if applicable)

No response

Operating System

Debian Linux

Browser (if applicable)

Mozilla Firefox latest

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

WebUI should forward requests directly to the provided Ollama endpoint without expecting internal /ollama/ endpoints.

Actual Behavior

WebUI fails to connect to external Ollama APIs and returns 500 Internal Server Error for all /ollama/ API requests.

Steps to Reproduce

Set up OpenWebUI with an external Ollama API URL (reverse-proxied).
Ensure CORS and CSP headers are properly configured.
Enter the URL into WebUI and test.
WebUI attempts to call /ollama/verify and /ollama/api/tags/0 on the WebUI server, not the actual Ollama backend that was set by the user.

Logs & Screenshots

XHRGET
https://ai.mysite.xyz/ollama/api/tags/0
[HTTP/1.1 500 Internal Server Error 185ms]

Additional Information

No response

Originally created by @emash on GitHub (Sep 25, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17760 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Pip Install ### Open WebUI Version 0.6.31 ### Ollama Version (if applicable) _No response_ ### Operating System Debian Linux ### Browser (if applicable) Mozilla Firefox latest ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using 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. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior WebUI should forward requests directly to the provided Ollama endpoint without expecting internal `/ollama/` endpoints. ### Actual Behavior WebUI fails to connect to external Ollama APIs and returns `500 Internal Server Error` for all `/ollama/` API requests. ### Steps to Reproduce 1. Set up OpenWebUI with an **external Ollama API URL** (reverse-proxied). 2. Ensure **CORS and CSP headers** are properly configured. 3. Enter the URL into WebUI and test. 4. WebUI attempts to call `/ollama/verify` and `/ollama/api/tags/0` on the **WebUI server**, not the actual Ollama backend that was set by the user. ### Logs & Screenshots XHRGET https://ai.mysite.xyz/ollama/api/tags/0 [HTTP/1.1 500 Internal Server Error 185ms] ### Additional Information _No response_