I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.6.26
Ollama Version (if applicable)
none
Operating System
Debian 13.0
Browser (if applicable)
No response
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
It should use a server from the openapi list, not the server that provides the openapi.[json|yaml|yml...].
Actual Behavior
It uses the server from which the endpoint list is loaded
Steps to Reproduce
Add a new tool with an openapi compatible endpoint which uses different api servers (for example the German "Autobahn API" https://autobahn.api.bund.dev/
Add the tool to a model
Ask something like "Welche Autobahnen gibt es in Deutschland" (Which highways are there in Germany)
Tool call failes because the wrong api server is being used
Logs & Screenshots
As you can see it runs "list-autobahnen" on the server autobahn.api.bund.dev but that doesn't provide the API endpoints
Additional Information
I'll look into it so see if I can maybe provide some commits to get this working correctly
Originally created by @MauritzFunke on GitHub (Sep 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17105
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.26
### Ollama Version (if applicable)
none
### Operating System
Debian 13.0
### Browser (if applicable)
_No response_
### 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
It should use a server from the openapi list, not the server that provides the openapi.[json|yaml|yml...].
### Actual Behavior
It uses the server from which the endpoint list is loaded
### Steps to Reproduce
1. Add a new tool with an openapi compatible endpoint which uses different api servers (for example the German "Autobahn API" https://autobahn.api.bund.dev/
2. Add the tool to a model
3. Ask something like "Welche Autobahnen gibt es in Deutschland" (Which highways are there in Germany)
4. Tool call failes because the wrong api server is being used
### Logs & Screenshots
<img width="878" height="371" alt="Image" src="https://github.com/user-attachments/assets/62b1c05e-2e35-405d-99a8-b07d1fe2fda8" />
As you can see it runs "list-autobahnen" on the server autobahn.api.bund.dev but that doesn't provide the API endpoints
### Additional Information
I'll look into it so see if I can maybe provide some commits to get this working correctly
GiteaMirror
added the bug label 2026-05-05 20:09:10 -05:00
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 @MauritzFunke on GitHub (Sep 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17105
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.26
Ollama Version (if applicable)
none
Operating System
Debian 13.0
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
It should use a server from the openapi list, not the server that provides the openapi.[json|yaml|yml...].
Actual Behavior
It uses the server from which the endpoint list is loaded
Steps to Reproduce
Logs & Screenshots
As you can see it runs "list-autobahnen" on the server autobahn.api.bund.dev but that doesn't provide the API endpoints
Additional Information
I'll look into it so see if I can maybe provide some commits to get this working correctly
@tjbck commented on GitHub (Sep 1, 2025):
Unable to reproduce, most likely a misconfiguration.