[GH-ISSUE #22543] issue: Frontend fetch of openapi.json from external tool server has no timeout, causing infinite UI hang on page load

GiteaMirror commented

2026-04-20 02:15:01 -05:00

Owner

Originally created by @jprovolone on GitHub (Mar 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22543

Check Existing Issues

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

Docker

Open WebUI Version

0.8.10

Ollama Version (if applicable)

No response

Operating System

Kubernetes

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

When a configured external OpenAPI tool server is unreachable, the frontend should time out, skip the unavailable server, and continue loading. The user should see a non-blocking warning rather than an indefinite spinner.

Actual Behavior

The UI hangs indefinitely with a spinning wheel whenever an enabled external tool server is unreachable. The page never loads and no error is shown to the user.

Steps to Reproduce

Add an external OpenAPI tool server under Settings → Integrations (e.g. http://localhost:2022)
Enable the connection (toggle on) and save
Stop or make the tool server unreachable
Clear all browser cache and login to Open WebUI
UI spins indefinitely — openapi.json shows as Pending in DevTools Network tab with no resolution

Logs & Screenshots

Additional Information

The backend already handles this correctly with AIOHTTP_CLIENT_TIMEOUT_TOOL_SERVER_DATA. This appears to be a frontend-only gap
Workaround: Blocking the unreachable tool server URL at the browser/network level (blocking trackers & ads) allows the fetch() to fail fast with a connection refused error rather than hanging, which unblocks the UI and allows Open WebUI to load normally

Originally created by @jprovolone on GitHub (Mar 10, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22543 ### 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 Docker ### Open WebUI Version 0.8.10 ### Ollama Version (if applicable) _No response_ ### Operating System Kubernetes ### 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 When a configured external OpenAPI tool server is unreachable, the frontend should time out, skip the unavailable server, and continue loading. The user should see a non-blocking warning rather than an indefinite spinner. ### Actual Behavior The UI hangs indefinitely with a spinning wheel whenever an enabled external tool server is unreachable. The page never loads and no error is shown to the user. ### Steps to Reproduce 1. Add an external OpenAPI tool server under Settings → Integrations (e.g. http://localhost:2022) 2. Enable the connection (toggle on) and save 3. Stop or make the tool server unreachable 4. Clear all browser cache and login to Open WebUI UI spins indefinitely — openapi.json shows as Pending in DevTools Network tab with no resolution ### Logs & Screenshots <img width="1887" height="974" alt="Image" src="https://github.com/user-attachments/assets/b2c58c5f-1df6-434a-994e-ac297e41b7c6" /> <img width="2560" height="1359" alt="Image" src="https://github.com/user-attachments/assets/ba59a78d-5d4e-4f12-8063-0f20e6763a82" /> ### Additional Information The backend already handles this correctly with AIOHTTP_CLIENT_TIMEOUT_TOOL_SERVER_DATA. This appears to be a frontend-only gap Workaround: Blocking the unreachable tool server URL at the browser/network level (blocking trackers & ads) allows the fetch() to fail fast with a connection refused error rather than hanging, which unblocks the UI and allows Open WebUI to load normally