github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.2k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #24260] issue: Model settings updates not persisted through admin settings interface #58912

New Issue
Closed
opened 2026-05-06 00:26:05 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-06 00:26:05 -05:00
Owner
Copy Link

Originally created by @jasper-war on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24260

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.9.2

Ollama Version (if applicable)

No response

Operating System

Ubuntu kernel 6.8.0-100

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

[Formulated by Claude after diagnostics, reviewed by myself]

Editing a custom model from Admin Panel → Settings → Models (pencil icon → change description / access list → Save & Update) should persist the changes via POST /api/v1/models/model/update and the new values should remain after reload.

Actual Behavior

[Formulated by Claude after diagnostics, reviewed by myself]

The save silently fails. The pencil-icon editor never calls /api/v1/models/model/update. Instead the frontend calls POST /api/v1/models/create, which the backend correctly rejects with 401 MODEL_ID_TAKEN because the model already exists. No error toast is shown (the catch swallows the rejection and returns null, suppressing the success toast). Reloading the page shows the model unchanged.

The companion request POST /api/v1/models/model/access/update returns 200 — so access-grant changes do hit the DB, but the rest of the model (description, name, params, meta, capabilities) snaps back, which makes the access change appear not to persist either.

Steps to Reproduce

Environment: Open WebUI v0.9.1 in Docker, PostgreSQL backend, OpenAI-compatible upstream (LiteLLM) providing the model list.

As an admin, go to Admin Panel → Settings → Models.
In the model list, click the pencil icon on any custom model whose row already exists in the model table (e.g. one with description/system prompt set, or with base_model_id set, or whose displayed id does not byte-equal the DB-stored id).
Change the description (or system prompt, or any meta/params field).
Click Save & Update.
Open DevTools → Network. Observe:
POST /api/v1/models/create → 401 Unauthorized with body {"detail": "Model ID is already in use ..."} (MODEL_ID_TAKEN).
POST /api/v1/models/model/access/update → 200 OK.
No POST /api/v1/models/model/update request.
Reload the page — the description / params change is gone.
Backend logs (docker logs amai-openwebui-1 | grep "/api/v1/models/") confirm the same pattern, with no Failed to update the model or Error binding parameter traces (so this is not the fixed #19335 bug, and not the #23960 500-on-extra-fields bug either).

Logs & Screenshots

In ~3 hours of an admin user attempting saves, the access log distribution is:

6 200 /api/v1/models/model/access/update
4 401 /api/v1/models/create
0 -- /api/v1/models/model/update ← never called

Additional Information

Probable root Cause
The bug is in src/lib/components/admin/Settings/Models.svelte — upsertModelHandler

Originally created by @jasper-war on GitHub (Apr 30, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24260 ### 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.9.2 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu kernel 6.8.0-100 ### 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 [Formulated by Claude after diagnostics, reviewed by myself] Editing a custom model from Admin Panel → Settings → Models (pencil icon → change description / access list → Save & Update) should persist the changes via POST /api/v1/models/model/update and the new values should remain after reload. ### Actual Behavior [Formulated by Claude after diagnostics, reviewed by myself] The save silently fails. The pencil-icon editor never calls /api/v1/models/model/update. Instead the frontend calls POST /api/v1/models/create, which the backend correctly rejects with 401 MODEL_ID_TAKEN because the model already exists. No error toast is shown (the catch swallows the rejection and returns null, suppressing the success toast). Reloading the page shows the model unchanged. The companion request POST /api/v1/models/model/access/update returns 200 — so access-grant changes do hit the DB, but the rest of the model (description, name, params, meta, capabilities) snaps back, which makes the access change appear not to persist either. ### Steps to Reproduce Environment: Open WebUI v0.9.1 in Docker, PostgreSQL backend, OpenAI-compatible upstream (LiteLLM) providing the model list. As an admin, go to Admin Panel → Settings → Models. In the model list, click the pencil icon on any custom model whose row already exists in the model table (e.g. one with description/system prompt set, or with base_model_id set, or whose displayed id does not byte-equal the DB-stored id). Change the description (or system prompt, or any meta/params field). Click Save & Update. Open DevTools → Network. Observe: POST /api/v1/models/create → 401 Unauthorized with body {"detail": "Model ID is already in use ..."} (MODEL_ID_TAKEN). POST /api/v1/models/model/access/update → 200 OK. No POST /api/v1/models/model/update request. Reload the page — the description / params change is gone. Backend logs (docker logs amai-openwebui-1 | grep "/api/v1/models/") confirm the same pattern, with no Failed to update the model or Error binding parameter traces (so this is not the fixed #19335 bug, and not the #23960 500-on-extra-fields bug either). ### Logs & Screenshots In ~3 hours of an admin user attempting saves, the access log distribution is: 6 200 /api/v1/models/model/access/update 4 401 /api/v1/models/create 0 -- /api/v1/models/model/update ← never called ### Additional Information Probable root Cause The bug is in [src/lib/components/admin/Settings/Models.svelte](https://github.com/open-webui/open-webui/blob/main/src/lib/components/admin/Settings/Models.svelte#L208-L237) — upsertModelHandler
GiteaMirror added the bug label 2026-05-06 00:26:05 -05:00
GiteaMirror commented 2026-05-06 00:26:16 -05:00
Author
Owner
Copy Link

@frenzybiscuit commented on GitHub (Apr 30, 2026):

I'm not sure about API access but changes do save and propagate when you edit in the admin -> models area.

You do need to hard refresh after saving to see the changes.

<!-- gh-comment-id:4351275052 --> @frenzybiscuit commented on GitHub (Apr 30, 2026): I'm not sure about API access but changes do save and propagate when you edit in the admin -> models area. You do need to hard refresh after saving to see the changes.
GiteaMirror commented 2026-05-06 00:26:21 -05:00
Author
Owner
Copy Link

@jasper-war commented on GitHub (Apr 30, 2026):

You are right! Not very intuitive from a ux stance, but it works.

<!-- gh-comment-id:4351999736 --> @jasper-war commented on GitHub (Apr 30, 2026): You are right! Not very intuitive from a ux stance, but it works.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#58912
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?