mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #22490] issue: TOOL_SERVER_CONNECTIONS list index out of range
#35251
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @erhhung on GitHub (Mar 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22490
Check Existing Issues
Installation Method
Other
Open WebUI Version
v0.8.10
Ollama Version (if applicable)
v0.17.6
Operating System
Ubuntu 24.04
Browser (if applicable)
Arc/Chrome
Confirmation
README.md.Expected Behavior
After upgrading Open WebUI to a new version (by installing Helm chart with new Open WebUI image), I don't expect to see errors with huge exception stack traces in the output when the container starts.
This particular issue concerns tool servers, and the result is that all previously configured tool servers are gone (or no longer accessible) from the UI——tools previously shown under
Admin Settings>Settings>Integrations>Generalare no longer there, and models that included those tools stop working.Actual Behavior
Container output shows a stack trace for error:
This issue has been happening for many versions (0.8.4 => 0.8.5 => 0.8.6 => 0.8.7 => 0.8.8 => 0.8.10), and likely even earlier, as I've only started adding tool servers around 0.8.4).
It occurs only, but always, after an upgrade/migration. Since a very similar issue had been reported earlier, but without the full log output, I'm including the full container log output below.
My scenario involves a slightly different configuration:
POST /api/v1/configs/tool_servers).TOOL_SERVER_CONNECTIONSenvironment variable is ever defined in the container.Steps to Reproduce
Run an older version of Open WebUI (I'm running on a Kubernetes cluster, but Docker Compose should be equally valid).
Configure some tool servers against a running MCPO instance, but not using the
TOOL_SERVER_CONNECTIONSenvironment variable nor through the UI——configure only via REST API:For example:
POST /api/v1/configs/tool_servers:Confirm that the tools appear in the UI under
Admin Settings>Settings>Integrations>Generaland work as expected.Now upgrade/migrate to a new version of Open WebUI, say, the latest. When the new container starts, after some initial output and the banner, a REST API call to
GET /api/v1/tools/fails with error 500, followed by cascading exception stack traces.Logs & Screenshots
Full output is too large to be included inline: owui-tool-servers-exception.log
The full log output shows several
POST /api/v1/configs/tool_serversAPI calls after the exceptions. Those are from my automation script that recreates the tool servers.Additional Information
See previous discussion: https://github.com/open-webui/open-webui/discussions/21629
Request to maintainers: please don't close this issue so soon just because you can't reproduce it on your first try.
@tjbck commented on GitHub (Mar 11, 2026):
8da29566a1@erhhung commented on GitHub (Mar 13, 2026):
@tjbck It looks like your refactoring, while checking for index bounds and bailing gracefully, doesn't really address why the server connection index would be out-of-bounds in the first place whenever an upgrade is performed. Would I still lose all my previously added tools whenver I do an upgrade?