[GH-ISSUE #9664] Deleting Ollama API entry causes model IDs to shift to the next entry #15604

New Issue

GiteaMirror · 2026-04-19T21:46:10-05:00

GiteaMirror commented

2026-04-19 21:46:10 -05:00

Originally created by @bannert1337 on GitHub (Feb 8, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9664

Environment

Open WebUI Version: v0.5.10
Ollama (if applicable): 0.5.7
Operating System: Linux
Browser (if applicable): Firefox 135.0.0

Confirmation:

I have read and followed all the instructions provided in the README.md.
I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

If multiple connections are configured and one connection is removed, the remaining connections move up one position. All details belonging to the deleted connection should be removed and subsequent connections should correctly maintain their associated data.

Actual Behavior:

When deleting an entry under Ollama API, the Key, Prefix, and Model IDs from the deleted entry override the entries of the connection that moves up to replace it. This results in incorrect model ID associations for the remaining connections.

Steps to Reproduce

Configure multiple connections to the Ollama API in Open WebUI.
Ensure at least one of the connections (not the first) has specified model IDs.
Delete the connection immediately above the connection with the specified model IDs.
Observe that the Key, Prefix, and Model IDs previously associated with the deleted connection are now associated with the connection that moved up.

Additional Information

This issue is similar to a previously reported bug where model IDs were not being correctly updated after deleting a connection (#8818). This can lead to security and functionality problems, as connections may be granted access to models they were not intended to use.

Originally created by @bannert1337 on GitHub (Feb 8, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/9664 ## Environment - **Open WebUI Version:** v0.5.10 - **Ollama (if applicable):** 0.5.7 - **Operating System:** Linux - **Browser (if applicable):** Firefox 135.0.0 **Confirmation:** - [X] I have read and followed all the instructions provided in the README.md. - [X] I am on the latest version of both Open WebUI and Ollama. - [ ] I have included the browser console logs. - [ ] I have included the Docker container logs. - [X] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: If multiple connections are configured and one connection is removed, the remaining connections move up one position. All details belonging to the deleted connection should be removed and subsequent connections should correctly maintain their associated data. ## Actual Behavior: When deleting an entry under Ollama API, the `Key`, `Prefix`, and `Model IDs` from the deleted entry override the entries of the connection that moves up to replace it. This results in incorrect model ID associations for the remaining connections. ## Steps to Reproduce 1. Configure multiple connections to the Ollama API in Open WebUI. 2. Ensure at least one of the connections (not the first) has specified model IDs. 3. Delete the connection immediately above the connection with the specified model IDs. 4. Observe that the `Key`, `Prefix`, and `Model IDs` previously associated with the deleted connection are now associated with the connection that moved up. ## Additional Information This issue is similar to a previously reported bug where model IDs were not being correctly updated after deleting a connection (#8818). This can lead to security and functionality problems, as connections may be granted access to models they were not intended to use.

GiteaMirror closed this issue

2026-04-19 21:46:10 -05:00

GiteaMirror commented

2026-04-19 21:46:11 -05:00

@tjbck commented on GitHub (Feb 8, 2025):

Good catch, fixed with 425a8a91788e40d766f16cc9c85b43330e061a49!

@tjbck commented on GitHub (Feb 8, 2025): Good catch, fixed with 425a8a91788e40d766f16cc9c85b43330e061a49!

GiteaMirror referenced this issue

2026-04-20 05:06:12 -05:00

[PR #15604] [MERGED] fix: tool results #23888

GiteaMirror referenced this issue

2026-04-25 12:05:22 -05:00