I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
v0.7.2
Ollama Version (if applicable)
No response
Operating System
Kubernetes / Linux
Browser (if applicable)
Chrome
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
HTTP requests to external services (TTS, Images, Pipelines, Ollama, etc.) should fail gracefully with a timeout error when the configured service is unreachable, allowing the UI to remain responsive.
Actual Behavior
When external services are unreachable (e.g., misconfigured URL, service down, network issues), the HTTP requests hang indefinitely because they
have no timeout parameter set. This causes:
The entire UI to hang/freeze
Admin settings pages to become unresponsive
No feedback to the user about what's happening
Server threads/connections to be held open indefinitely
Steps to Reproduce
Open Admin Settings and navigate to the relevant section (e.g. Audio under TTS)
Configure an external (OpenAI) service URL to an unreachable address (e.g., http://10.255.255.1:9999)
Go to the main chat interface and go back to the audio settings.
Try to change it to WebAPI
Result: The page hangs indefinitely with no response
Originally created by @jannikstdl on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21054
### 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 have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
v0.7.2
### Ollama Version (if applicable)
_No response_
### Operating System
Kubernetes / Linux
### Browser (if applicable)
Chrome
### 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
HTTP requests to external services (TTS, Images, Pipelines, Ollama, etc.) should fail gracefully with a timeout error when the configured service is unreachable, allowing the UI to remain responsive.
### Actual Behavior
When external services are unreachable (e.g., misconfigured URL, service down, network issues), the HTTP requests hang indefinitely because they
have no timeout parameter set. This causes:
- The entire UI to hang/freeze
- Admin settings pages to become unresponsive
- No feedback to the user about what's happening
- Server threads/connections to be held open indefinitely
### Steps to Reproduce
1. Open Admin Settings and navigate to the relevant section (e.g. Audio under TTS)
3. Configure an external (OpenAI) service URL to an unreachable address (e.g., http://10.255.255.1:9999)
4. Go to the main chat interface and go back to the audio settings.
5. Try to change it to WebAPI
6. Result: The page hangs indefinitely with no response
### Logs & Screenshots
```bash
2026-01-29 17:32:53.947 | DEBUG | urllib3.connectionpool:_new_conn:241 - Starting new HTTP connection (1): 100.127.170.82:80
```
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-18 04:40:05 -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 @jannikstdl on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21054
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.7.2
Ollama Version (if applicable)
No response
Operating System
Kubernetes / Linux
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
HTTP requests to external services (TTS, Images, Pipelines, Ollama, etc.) should fail gracefully with a timeout error when the configured service is unreachable, allowing the UI to remain responsive.
Actual Behavior
When external services are unreachable (e.g., misconfigured URL, service down, network issues), the HTTP requests hang indefinitely because they
have no timeout parameter set. This causes:
Steps to Reproduce
Logs & Screenshots
Additional Information
No response