I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Pip Install
Open WebUI Version
0.6.15
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22.04
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
Open WebUI to keep functioning and throw an error
Actual Behavior
Open WebUI fully hangs for an extended period of time (minutes/longer)
Steps to Reproduce
Some projects that provide openAI compatible API endpoints do not support all the endpoints that openAI does. While it could be argued that the projects should add the endpoints, I don't think open webui should become fully unresponsive after saving settings pointing it at one of these endpoints.
As is, using such a project and setting it up in open webUI causes the application to fully hang, and log nothing but what can be seen below which also makes it impossible to change the settings again until the application starts responding again, which takes a couple of minutes
Jun 17 14:02:52 open-webui[278]: 2025-06-17 14:02:52.893 | ERROR | open_webui.routers.audio:get_available_voices:1042 - Error fetching voices from custom endpoint: HTTPConnectionPool(host='192.168.1.100', port=8003): Max retries exceeded with url: /v1/audio/voices (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7e0b33826d50>, 'Connection to 192.168.1.100 timed out. (connect timeout=None)')) - {}
Jun 17 14:05:08 open-webui[278]: 2025-06-17 14:05:08.061 | ERROR | open_webui.routers.audio:get_available_models:995 - Error fetching models from custom endpoint: HTTPConnectionPool(host='192.168.1.100', port=8003): Max retries exceeded with url: /v1/audio/models (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7e0b338a9b90>, 'Connection to 192.168.1.100 timed out. (connect timeout=None)')) - {}
Additional Information
No response
Originally created by @abcd678 on GitHub (Jun 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15079
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Pip Install
### Open WebUI Version
0.6.15
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu 22.04
### 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
Open WebUI to keep functioning and throw an error
### Actual Behavior
Open WebUI fully hangs for an extended period of time (minutes/longer)
### Steps to Reproduce
Some projects that provide openAI compatible API endpoints do not support all the endpoints that openAI does. While it could be argued that the projects should add the endpoints, I don't think open webui should become fully unresponsive after saving settings pointing it at one of these endpoints.
As is, using such a project and setting it up in open webUI causes the application to fully hang, and log nothing but what can be seen below which also makes it impossible to change the settings again until the application starts responding again, which takes a couple of minutes
Examples of some projects that will trigger this issue:
https://github.com/devnen/Dia-TTS-Server
https://github.com/devnen/Chatterbox-TTS-Server
### Logs & Screenshots
```
Jun 17 14:02:52 open-webui[278]: 2025-06-17 14:02:52.893 | ERROR | open_webui.routers.audio:get_available_voices:1042 - Error fetching voices from custom endpoint: HTTPConnectionPool(host='192.168.1.100', port=8003): Max retries exceeded with url: /v1/audio/voices (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7e0b33826d50>, 'Connection to 192.168.1.100 timed out. (connect timeout=None)')) - {}
Jun 17 14:05:08 open-webui[278]: 2025-06-17 14:05:08.061 | ERROR | open_webui.routers.audio:get_available_models:995 - Error fetching models from custom endpoint: HTTPConnectionPool(host='192.168.1.100', port=8003): Max retries exceeded with url: /v1/audio/models (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7e0b338a9b90>, 'Connection to 192.168.1.100 timed out. (connect timeout=None)')) - {}
```
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-20 22:28:59 -05:00
Unable to reproduce, you should be able to configure AIOHTTP_CLIENT_TIMEOUT.
<!-- gh-comment-id:2982914737 -->
@tjbck commented on GitHub (Jun 18, 2025):
Unable to reproduce, you should be able to configure `AIOHTTP_CLIENT_TIMEOUT`.
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 @abcd678 on GitHub (Jun 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15079
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
0.6.15
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22.04
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Open WebUI to keep functioning and throw an error
Actual Behavior
Open WebUI fully hangs for an extended period of time (minutes/longer)
Steps to Reproduce
Some projects that provide openAI compatible API endpoints do not support all the endpoints that openAI does. While it could be argued that the projects should add the endpoints, I don't think open webui should become fully unresponsive after saving settings pointing it at one of these endpoints.
As is, using such a project and setting it up in open webUI causes the application to fully hang, and log nothing but what can be seen below which also makes it impossible to change the settings again until the application starts responding again, which takes a couple of minutes
Examples of some projects that will trigger this issue:
https://github.com/devnen/Dia-TTS-Server
https://github.com/devnen/Chatterbox-TTS-Server
Logs & Screenshots
Additional Information
No response
@tjbck commented on GitHub (Jun 18, 2025):
Unable to reproduce, you should be able to configure
AIOHTTP_CLIENT_TIMEOUT.