[GH-ISSUE #8818] Allowed Model IDs are not attached to connection entry #30806

New Issue

GiteaMirror · 2026-04-25T05:00:59-05:00

GiteaMirror commented

2026-04-25 05:00:59 -05:00

Originally created by @bannert1337 on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8818

Bug Report

Installation Method

[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]

Environment

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

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 connection are correctly moved up one position with the connection.

Actual Behavior:

The connections are correctly moved up, but the specified model IDs remain at the same position, now part of the connection previously below.

Description

Bug Summary:
Baseline:

multiple connections are configured
a connection contains specified model IDs
this connection is not the first entry

If the connection above is removed, all connections move up one position.
The model IDs remain at the same position and are now part of the connection previously below.
This can lead to big issues, as now all models are allowed for the connection that was restricted to specific model IDs.
This could cause further problems, such as

if no connection is below, the model IDs would be dangling, maybe causing memory conflicts

Reproduction Details

Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:
[Include relevant Docker container logs, if applicable]

Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]

Additional Information

[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]

Note

If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Originally created by @bannert1337 on GitHub (Jan 23, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/8818 # Bug Report ## Installation Method [Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.] ## Environment - **Open WebUI Version:** v0.5.6 - **Ollama (if applicable):** 0.5.7 - **Operating System:** Linux - **Browser (if applicable):** Firefox 134.0.2 **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. - [X] I have included the browser console logs. - [X] 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 connection are correctly moved up one position with the connection. ## Actual Behavior: The connections are correctly moved up, but the specified model IDs remain at the same position, now part of the connection previously below. ## Description **Bug Summary:** Baseline: - multiple connections are configured - a connection contains specified model IDs - this connection is not the first entry If the connection above is removed, all connections move up one position. The model IDs remain at the same position and are now part of the connection previously below. This can lead to big issues, as now all models are allowed for the connection that was restricted to specific model IDs. This could cause further problems, such as - if no connection is below, the model IDs would be dangling, maybe causing memory conflicts ## Reproduction Details **Steps to Reproduce:** [Outline the steps to reproduce the bug. Be as detailed as possible.] ## Logs and Screenshots **Browser Console Logs:** [Include relevant browser console logs, if applicable] **Docker Container Logs:** [Include relevant Docker container logs, if applicable] **Screenshots/Screen Recordings (if applicable):** [Attach any relevant screenshots to help illustrate the issue] ## Additional Information [Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.] ## Note If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

GiteaMirror closed this issue

2026-04-25 05:00:59 -05:00

GiteaMirror commented

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

@tjbck commented on GitHub (Jan 23, 2025):

Fixed with the latest

@tjbck commented on GitHub (Jan 23, 2025): Fixed with the latest

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#30806