I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
0.6.25
Ollama Version (if applicable)
No response
Operating System
macOS Sequoia
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
Long running MCP tool calls do not time out.
Actual Behavior
Long running MCP tool calls time out.
Steps to Reproduce
Use mcpo with an MCP server with a tool call that takes on average 2 minutes to complete
Make OWUI call the tool in your chat
If the tool call completes in under 60 seconds, everything is fine
If the tool call takes longer than 60 seconds, OWUI will keep the tool call spinning forever, but will proceed assuming it fails
While this is happening, mcpo logs look fine, incoming call, calling endpoint, then eventually it returns an HTTP 200 (after OWUI has moved on)
I have set AIOHTTP_CLIENT_TIMEOUT to 9999
My tools are set up through User Settings -> Tools.
Logs & Screenshots
MCPO logs:
2025-08-25 14:32:04,915 - INFO - Calling endpoint: super_slow_search, with args: {'query': 'My awesome search query', 'datasources': ['my_awesome_data_sources']}
(About 80 seconds later, after OWUI has moved on) INFO: 172.30.1.1:34436 - "POST /my_awesome_mcp_server/super_slow_search HTTP/1.1" 200 OK
Additional Information
No response
Originally created by @dionny on GitHub (Aug 25, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16900
### 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
0.6.25
### Ollama Version (if applicable)
_No response_
### Operating System
macOS Sequoia
### 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
Long running MCP tool calls do not time out.
### Actual Behavior
Long running MCP tool calls time out.
### Steps to Reproduce
1. Use mcpo with an MCP server with a tool call that takes on average 2 minutes to complete
2. Make OWUI call the tool in your chat
3. If the tool call completes in under 60 seconds, everything is fine
4. If the tool call takes longer than 60 seconds, OWUI will keep the tool call spinning forever, but will proceed assuming it fails
5. While this is happening, mcpo logs look fine, incoming call, calling endpoint, then eventually it returns an HTTP 200 (after OWUI has moved on)
I have set `AIOHTTP_CLIENT_TIMEOUT` to 9999
My tools are set up through User Settings -> Tools.
### Logs & Screenshots
MCPO logs:
2025-08-25 14:32:04,915 - INFO - Calling endpoint: super_slow_search, with args: {'query': 'My awesome search query', 'datasources': ['my_awesome_data_sources']}
(About 80 seconds later, after OWUI has moved on) INFO: 172.30.1.1:34436 - "POST /my_awesome_mcp_server/super_slow_search HTTP/1.1" 200 OK
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-20 23:20:16 -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 @dionny on GitHub (Aug 25, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16900
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.25
Ollama Version (if applicable)
No response
Operating System
macOS Sequoia
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Long running MCP tool calls do not time out.
Actual Behavior
Long running MCP tool calls time out.
Steps to Reproduce
I have set
AIOHTTP_CLIENT_TIMEOUTto 9999My tools are set up through User Settings -> Tools.
Logs & Screenshots
MCPO logs:
2025-08-25 14:32:04,915 - INFO - Calling endpoint: super_slow_search, with args: {'query': 'My awesome search query', 'datasources': ['my_awesome_data_sources']}
(About 80 seconds later, after OWUI has moved on) INFO: 172.30.1.1:34436 - "POST /my_awesome_mcp_server/super_slow_search HTTP/1.1" 200 OK
Additional Information
No response
@tjbck commented on GitHub (Aug 25, 2025):
AIOHTTP_CLIENT_TIMEOUTshould be set to None, keep us updated.