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.0
Ollama Version (if applicable)
No response
Operating System
Vanilla OS 2
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 listed steps to reproduce the bug in detail.
Expected Behavior
When making requests to external tool servers, the request should be successfully authenticated.
Actual Behavior
The configured API key is not being included in the request headers, leading to a 401 Unauthorized error.
Steps to Reproduce
Run mcpo with --api-key MY_API_KEY.
Add MY_API_KEY to the tools settings in Open WebUI.
Send a chat message that triggers a request to the tool servers.
Logs & Screenshots
"POST /mcp/xxx HTTP/1.1" 401 Unauthorized
Additional Information
No response
Originally created by @NN708 on GitHub (Apr 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12379
### 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.0
### Ollama Version (if applicable)
_No response_
### Operating System
Vanilla OS 2
### 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 listed steps to reproduce the bug in detail.
### Expected Behavior
When making requests to external tool servers, the request should be successfully authenticated.
### Actual Behavior
The configured API key is not being included in the request headers, leading to a 401 Unauthorized error.
### Steps to Reproduce
1. Run `mcpo` with `--api-key MY_API_KEY`.
2. Add `MY_API_KEY` to the tools settings in Open WebUI.
3. Send a chat message that triggers a request to the tool servers.
### Logs & Screenshots
```
"POST /mcp/xxx HTTP/1.1" 401 Unauthorized
```
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-19 22:28:10 -05:00
Addressed with 2277566ce1, 0.6.1 will be released soon.
<!-- gh-comment-id:2774254041 -->
@tjbck commented on GitHub (Apr 3, 2025):
Addressed with 2277566ce1b7bf24e227be8a0091011cb13a1122, 0.6.1 will be released soon.
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 @NN708 on GitHub (Apr 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12379
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.0
Ollama Version (if applicable)
No response
Operating System
Vanilla OS 2
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When making requests to external tool servers, the request should be successfully authenticated.
Actual Behavior
The configured API key is not being included in the request headers, leading to a 401 Unauthorized error.
Steps to Reproduce
mcpowith--api-key MY_API_KEY.MY_API_KEYto the tools settings in Open WebUI.Logs & Screenshots
Additional Information
No response
@tjbck commented on GitHub (Apr 3, 2025):
Addressed with
2277566ce1, 0.6.1 will be released soon.@NN708 commented on GitHub (Apr 3, 2025):
Thanks for the quick fix!
@phamkhactu commented on GitHub (Apr 22, 2025):
Hi @tjbck, @NN708
I have the same problem with v0.6.5