[GH-ISSUE #21600] issue: Previously Configured Tool Servers via UI Break When TOOL_SERVER_CONNECTIONS Is Introduced or Empty

Originally created by @BernhardtMilan on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21600 ### 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 Other ### Open WebUI Version v0.8.3 ### Ollama Version (if applicable) _No response_ ### Operating System Red Hat Enterprise Linux CoreOS ### 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 upgrading or migrating from an older version of Open WebUI where tool servers were configured via the UI and stored in the database, the system should continue to work after the upgrade/migration. All previously configured tool servers should remain available and function correctly, even if a new environment variable TOOL_SERVER_CONNECTIONS is available. The system should handle the presence of old tool server configuration data gracefully, and should not crash or become unusable due to configuration method changes during migration. Tool servers previously managed through the UI should be available in chats and the application UI without requiring manual intervention or data cleanup. ### Actual Behavior After migrating from an older version where tool servers were configured via the UI and stored in the database, the application fails to load these tool servers correctly with the new environment variable TOOL_SERVER_CONNECTIONS bot configured with a placeholder. This results in errors such as IndexError when attempting to access the tools, leading to the complete unavailability of previously configured tools in both the application UI and in new chats. As a result, users are unable to access or use any of the existing tools within new or ongoing chats, effectively breaking key functionality after the upgrade. ### Steps to Reproduce 1. Start with an older version of Open WebUI (pre-v0.8.3) and configure one or more tool servers via the UI. 2. Upgrade to the latest version of Open WebUI (e.g., v0.8.3). 3. Start the application without setting or properly configuring the new TOOL_SERVER_CONNECTIONS environment variable. 4. Attempt to access previously configured tools in the application UI or within a new ch ### Logs & Screenshots File "/app/backend/open_webui/routers/tools.py", line 81, in get_tools connection = request.app.state.config.TOOL_SERVER_CONNECTIONS[ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ IndexError: list index out of range ### Additional Information _No response_

GiteaMirror commented

2026-04-25 09:16:00 -05:00

Owner

Originally created by @BernhardtMilan on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21600

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

Other

Open WebUI Version

v0.8.3

Ollama Version (if applicable)

No response

Operating System

Red Hat Enterprise Linux CoreOS

Browser (if applicable)

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 upgrading or migrating from an older version of Open WebUI where tool servers were configured via the UI and stored in the database, the system should continue to work after the upgrade/migration. All previously configured tool servers should remain available and function correctly, even if a new environment variable TOOL_SERVER_CONNECTIONS is available. The system should handle the presence of old tool server configuration data gracefully, and should not crash or become unusable due to configuration method changes during migration. Tool servers previously managed through the UI should be available in chats and the application UI without requiring manual intervention or data cleanup.

Actual Behavior

After migrating from an older version where tool servers were configured via the UI and stored in the database, the application fails to load these tool servers correctly with the new environment variable TOOL_SERVER_CONNECTIONS bot configured with a placeholder. This results in errors such as IndexError when attempting to access the tools, leading to the complete unavailability of previously configured tools in both the application UI and in new chats. As a result, users are unable to access or use any of the existing tools within new or ongoing chats, effectively breaking key functionality after the upgrade.

Steps to Reproduce

Start with an older version of Open WebUI (pre-v0.8.3) and configure one or more tool servers via the UI.
Upgrade to the latest version of Open WebUI (e.g., v0.8.3).
Start the application without setting or properly configuring the new TOOL_SERVER_CONNECTIONS environment variable.
Attempt to access previously configured tools in the application UI or within a new ch

Logs & Screenshots

File "/app/backend/open_webui/routers/tools.py", line 81, in get_tools
connection = request.app.state.config.TOOL_SERVER_CONNECTIONS[
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
IndexError: list index out of range

Additional Information

GiteaMirror added the bug label 2026-04-25 09:16:00 -05:00

GiteaMirror closed this issue

2026-04-25 09:16:01 -05:00

2026-04-25 09:16:02 -05:00

Author

@tjbck commented on GitHub (Feb 19, 2026):

@Classic298 are you able to reproduce? Unable to reproduce from our end, and working as intended.

@tjbck commented on GitHub (Feb 19, 2026): @Classic298 are you able to reproduce? Unable to reproduce from our end, and working as intended.

[GH-ISSUE #21600] issue: Previously Configured Tool Servers via UI Break When TOOL_SERVER_CONNECTIONS Is Introduced or Empty #35059