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.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #24168] issue: #58884

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

Originally created by @aprudnev on GitHub (Apr 27, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24168

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

Pip Install

Open WebUI Version

v0.9.2

Ollama Version (if applicable)

No response

Operating System

Ubuntu 24 LTS

Browser (if applicable)

Chrome

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

We used to have all models PRIVATE and then create PUBLIC ones from them in WORKSPACE. It allows to provide access to the models coupled with workspace and prompts without exposing original models.

This broke once we updated open-webui to the version v0.9 - now, if I use PRIVATE model as a BASE model and mark result (in workspace) as PUBLIC, when user (who is not admin) try to start chat, he receive error 'model not found'. As I can not downgrade system, and as it was POC and we could not backup VM due to PCI pass thru (which do not allow veeam backups) we was forced to make base models public and so users see both, base model and workspace model.

In addition, it looks as pdf download is broken in the chats, and when we try to share chat as PUBLIC, it jump back to private. I can not confirm it (but can test on other instance), but the very first thing (that v0.8 allowed to user PRIVATE model when create model for workspace, and claim new model PUBLIC and it worked - and it broke in v0.9) is a very serious limitation and looks as a bug.

Actual Behavior

Before upgrade, v0.8, I could create model B in workspace using model A imported from connections, set up A as PRIVATE and B as PUBLIC, and it worked. After upgrade, all these models return error 'model not found' when user starts chat.

Steps to Reproduce

Connect open-webui to OpenAI model (for example vLLM). Select some model, keep it PRIVATE.

Open WORKSPACE, create new model using model above as a BASE. Change access to it as PUBLIC.

Login by USER (not administrator), create new chat. You will see model from workspace. Ask it. Response will be 'model not found' in v0.9.2 . v0.8 - workspace model worked well (and user saw only this model).

Change base model to PUBLIC. Now user will see both, original model and one created with it as a BASE. Now both works.

Logs & Screenshots

No logs, it is all gui behavior.

Additional Information

I do not think that it is intended behavior as if so, system should show error during setup or did not snow model at all.

Originally created by @aprudnev on GitHub (Apr 27, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24168 ### 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 Pip Install ### Open WebUI Version v0.9.2 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 24 LTS ### Browser (if applicable) Chrome ### 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 We used to have all models PRIVATE and then create PUBLIC ones from them in WORKSPACE. It allows to provide access to the models coupled with workspace and prompts without exposing original models. This broke once we updated open-webui to the version v0.9 - now, if I use PRIVATE model as a BASE model and mark result (in workspace) as PUBLIC, when user (who is not admin) try to start chat, he receive error 'model not found'. As I can not downgrade system, and as it was POC and we could not backup VM due to PCI pass thru (which do not allow veeam backups) we was forced to make base models public and so users see both, base model and workspace model. In addition, it looks as pdf download is broken in the chats, and when we try to share chat as PUBLIC, it jump back to private. I can not confirm it (but can test on other instance), but the very first thing (that v0.8 allowed to user PRIVATE model when create model for workspace, and claim new model PUBLIC and it worked - and it broke in v0.9) is a very serious limitation and looks as a bug. ### Actual Behavior Before upgrade, v0.8, I could create model B in workspace using model A imported from connections, set up A as PRIVATE and B as PUBLIC, and it worked. After upgrade, all these models return error 'model not found' when user starts chat. ### Steps to Reproduce Connect open-webui to OpenAI model (for example vLLM). Select some model, keep it PRIVATE. Open WORKSPACE, create new model using model above as a BASE. Change access to it as PUBLIC. Login by USER (not administrator), create new chat. You will see model from workspace. Ask it. Response will be 'model not found' in v0.9.2 . v0.8 - workspace model worked well (and user saw only this model). Change base model to PUBLIC. Now user will see both, original model and one created with it as a BASE. Now both works. ### Logs & Screenshots No logs, it is all gui behavior. ### Additional Information I do not think that it is intended behavior as if so, system should show error during setup or did not snow model at all.
GiteaMirror added the bug label 2026-05-06 00:20:29 -05:00
GiteaMirror commented 2026-05-06 00:20:35 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Apr 27, 2026):

⚠️ Invalid Issue Title

Hey @aprudnev, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.

Please update the title to reflect the content of your issue.

⚠️ Missing Issue Title Prefix

@aprudnev, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:4324523835 --> @pr-validator-bot commented on GitHub (Apr 27, 2026): # ⚠️ Invalid Issue Title Hey @aprudnev, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues. Please update the title to reflect the content of your issue. --- # ⚠️ Missing Issue Title Prefix @aprudnev, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-05-06 00:20:36 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Apr 27, 2026):

Use the search this was reported 3 more times. It's a security bug that was fixed. If you don't have access to the base model you shouldn't have access to it though the workspace model either

Just turn the base models to public but hide them (three dots > hide model)

<!-- gh-comment-id:4324958380 --> @Classic298 commented on GitHub (Apr 27, 2026): Use the search this was reported 3 more times. It's a security bug that was fixed. If you don't have access to the base model you shouldn't have access to it though the workspace model either Just turn the base models to public but hide them (three dots > hide model)
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#58884
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?