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
v0.9.2
Ollama Version (if applicable)
v0.22.1
Operating System
Ubuntu 24.04.4
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
After upgrade from v0.8.12 to v0.9.2 should modell which is running with vllm be usable for others, which has access to the Open WebUI.
Actual Behavior
After upgrade to v0.9.2 the vllm modell is only usable for admin user. All other users get
when they try to use this modell in Open WebUI or with the Open WebUI API.
The users can see and choose the model. Strange.
But they can't use it.
The MiniMax M2.5 (runs with vllm) base model ist private. Than I configured a new MiniMax M2.5 modell
which is accessible only for Agents and Development user groups.
And this is not working. This works only, when the MiniMax M2.5 base model ist set to public. This was warking with v0.8.12 fine.
All other modells runs with Ollama and here is same configuration (base model is private and the new model is private too with access for some user groups) working.
Steps to Reproduce
Reproduce the setup decscribed above.
Logs & Screenshots
See above.
Additional Information
I removed the new virtual model and added ir again. Same problem.
I don't see any call in my vllm instance. Looks for me like an internal Open WebUI issue.
Originally created by @somera on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24348
### 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
v0.9.2
### Ollama Version (if applicable)
v0.22.1
### Operating System
Ubuntu 24.04.4
### 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
After upgrade from v0.8.12 to v0.9.2 should modell which is running with vllm be usable for others, which has access to the Open WebUI.
### Actual Behavior
After upgrade to v0.9.2 the vllm modell is only usable for admin user. All other users get
<img width="322" height="263" alt="Image" src="https://github.com/user-attachments/assets/806a44d2-c301-446f-9736-74735ca59f00" />
when they try to use this modell in Open WebUI or with the Open WebUI API.
The users can see and choose the model. Strange.
<img width="272" height="254" alt="Image" src="https://github.com/user-attachments/assets/5c91fb1f-523d-4a79-8840-1669e3cbbd35" />
But they can't use it.
The MiniMax M2.5 (runs with vllm) base model ist private. Than I configured a new MiniMax M2.5 modell
<img width="621" height="692" alt="Image" src="https://github.com/user-attachments/assets/402ce987-8fbf-4cce-8fd9-514b84283533" />
which is accessible only for `Agents` and `Development` user groups.
And this is not working. This works only, when the MiniMax M2.5 base model ist set to public. This was warking with v0.8.12 fine.
All other modells runs with Ollama and here is same configuration (base model is private and the new model is private too with access for some user groups) working.
### Steps to Reproduce
Reproduce the setup decscribed above.
### Logs & Screenshots
See above.
### Additional Information
I removed the new virtual model and added ir again. Same problem.
I don't see any call in my vllm instance. Looks for me like an internal Open WebUI issue.
GiteaMirror
added the bug label 2026-05-21 02:54:35 -05:00
@owui-terminator[bot] commented on GitHub (May 4, 2026):
🔍Similar Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
#24040issue: PostgreSQL TLS startup regression in v0.9 by attilaolah · bug
#23939issue: Loading and login issue after upgrading to 0.9.0 and 0.9.1 by Joly0 · bug
#23344issue: MCP-Server OAuth not working in v0.8.12 by aleex1848 · bug
#21843issue: Startup fails after upgrading from 0.7.2 to 0.8.x by Sjw22263 · bug
#21945issue: Open WebUI Backend Required after updating from 0.7.2 to 0.8.x by Oatu4396 · bug
💡 If this is a duplicate, consider closing it and adding details to the existing issue.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4371423450 -->
@owui-terminator[bot] commented on GitHub (May 4, 2026):
🔍 **Similar Issues Found**
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
1. [#24040](https://github.com/open-webui/open-webui/issues/24040) **issue: PostgreSQL TLS startup regression in v0.9**
*by attilaolah · `bug`*
2. [#23939](https://github.com/open-webui/open-webui/issues/23939) **issue: Loading and login issue after upgrading to 0.9.0 and 0.9.1**
*by Joly0 · `bug`*
3. [#23344](https://github.com/open-webui/open-webui/issues/23344) **issue: MCP-Server OAuth not working in v0.8.12**
*by aleex1848 · `bug`*
4. [#21843](https://github.com/open-webui/open-webui/issues/21843) **issue: Startup fails after upgrading from 0.7.2 to 0.8.x**
*by Sjw22263 · `bug`*
5. [#21945](https://github.com/open-webui/open-webui/issues/21945) **issue: Open WebUI Backend Required after updating from 0.7.2 to 0.8.x**
*by Oatu4396 · `bug`*
---
💡 If this is a duplicate, consider closing it and adding details to the existing issue.
*This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
The user has to have access to the workspace model and the workspace model's base model.
If the user doesn't have access to the base model they can't use the workspace model.
This was a security bug and was fixed.
<!-- gh-comment-id:4371537994 -->
@Classic298 commented on GitHub (May 4, 2026):
The user has to have access to the workspace model and the workspace model's base model.
If the user doesn't have access to the base model they can't use the workspace model.
This was a security bug and was fixed.
The user has to have access to the workspace model and the workspace model's base model.
The user has access to the workspace model:
means, I need same group access configuration for the base model too?
<!-- gh-comment-id:4371562023 -->
@somera commented on GitHub (May 4, 2026):
> The user has to have access to the workspace model and the workspace model's base model.
The user has access to the workspace model:
<img width="461" height="210" alt="Image" src="https://github.com/user-attachments/assets/23450c23-69ce-401c-9589-e5a7b11cc902" />
means, I need same group access configuration for the base model too?
@Classic298 thx. It works. But it make more complicated.
Will this be changed for Ollama API too? Cause here the "old" way is working.
<!-- gh-comment-id:4371647539 -->
@somera commented on GitHub (May 4, 2026):
@Classic298 thx. It works. But it make more complicated.
Will this be changed for Ollama API too? Cause here the "old" way is working.
Yes. All API endpoints received enforced access control security in 0.9.0
I recommend setting the base model to public and hiding the base model
<!-- gh-comment-id:4371662339 -->
@Classic298 commented on GitHub (May 4, 2026):
Yes. All API endpoints received enforced access control security in 0.9.0
I recommend setting the base model to public and hiding the base model
I recommend setting the base model to public and hiding the base model
OK, I try this.
<!-- gh-comment-id:4371704185 -->
@somera commented on GitHub (May 4, 2026):
> I recommend setting the base model to public and hiding the base model
OK, I try this.
@Classic298 I chnaged my whole model configuration.
Base model it public and hidden.
In the UI I see the models 1 time. Fine.
And my expectatios is when I use Open WebUI API as proxy same like in the UI.
When I call curl https://openwebui/api/models -H "Authorization: Bearer sk-xxxx" I see the hidden models too.
Whis it from my point of view not good.
Is this intentional?
<!-- gh-comment-id:4372477795 -->
@somera commented on GitHub (May 4, 2026):
@Classic298 I chnaged my whole model configuration.
Base model it public and hidden.
In the UI I see the models 1 time. Fine.
And my expectatios is when I use Open WebUI API as proxy same like in the UI.
When I call `curl https://openwebui/api/models -H "Authorization: Bearer sk-xxxx"` I see the hidden models too.
Whis it from my point of view not good.
Is this intentional?
yes the hidden model is only hidden from the UI. If you want to hide it from models endpoint open a feature request. Not sure if technically easy possible since other UI elements may depend on the /models endpoint
<!-- gh-comment-id:4372489844 -->
@Classic298 commented on GitHub (May 4, 2026):
yes the hidden model is only hidden from the UI. If you want to hide it from models endpoint open a feature request. Not sure if technically easy possible since other UI elements may depend on the /models endpoint
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @somera on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24348
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.9.2
Ollama Version (if applicable)
v0.22.1
Operating System
Ubuntu 24.04.4
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
After upgrade from v0.8.12 to v0.9.2 should modell which is running with vllm be usable for others, which has access to the Open WebUI.
Actual Behavior
After upgrade to v0.9.2 the vllm modell is only usable for admin user. All other users get
when they try to use this modell in Open WebUI or with the Open WebUI API.
The users can see and choose the model. Strange.
But they can't use it.
The MiniMax M2.5 (runs with vllm) base model ist private. Than I configured a new MiniMax M2.5 modell
which is accessible only for
AgentsandDevelopmentuser groups.And this is not working. This works only, when the MiniMax M2.5 base model ist set to public. This was warking with v0.8.12 fine.
All other modells runs with Ollama and here is same configuration (base model is private and the new model is private too with access for some user groups) working.
Steps to Reproduce
Reproduce the setup decscribed above.
Logs & Screenshots
See above.
Additional Information
I removed the new virtual model and added ir again. Same problem.
I don't see any call in my vllm instance. Looks for me like an internal Open WebUI issue.
@owui-terminator[bot] commented on GitHub (May 4, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
#24040 issue: PostgreSQL TLS startup regression in v0.9
by attilaolah ·
bug#23939 issue: Loading and login issue after upgrading to 0.9.0 and 0.9.1
by Joly0 ·
bug#23344 issue: MCP-Server OAuth not working in v0.8.12
by aleex1848 ·
bug#21843 issue: Startup fails after upgrading from 0.7.2 to 0.8.x
by Sjw22263 ·
bug#21945 issue: Open WebUI Backend Required after updating from 0.7.2 to 0.8.x
by Oatu4396 ·
bug💡 If this is a duplicate, consider closing it and adding details to the existing issue.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
@Classic298 commented on GitHub (May 4, 2026):
The user has to have access to the workspace model and the workspace model's base model.
If the user doesn't have access to the base model they can't use the workspace model.
This was a security bug and was fixed.
@somera commented on GitHub (May 4, 2026):
The user has access to the workspace model:
means, I need same group access configuration for the base model too?
@Classic298 commented on GitHub (May 4, 2026):
Yes exactly
@somera commented on GitHub (May 4, 2026):
@Classic298 thx. It works. But it make more complicated.
Will this be changed for Ollama API too? Cause here the "old" way is working.
@Classic298 commented on GitHub (May 4, 2026):
Yes. All API endpoints received enforced access control security in 0.9.0
I recommend setting the base model to public and hiding the base model
@somera commented on GitHub (May 4, 2026):
OK, I try this.
@somera commented on GitHub (May 4, 2026):
@Classic298 I chnaged my whole model configuration.
Base model it public and hidden.
In the UI I see the models 1 time. Fine.
And my expectatios is when I use Open WebUI API as proxy same like in the UI.
When I call
curl https://openwebui/api/models -H "Authorization: Bearer sk-xxxx"I see the hidden models too.Whis it from my point of view not good.
Is this intentional?
@Classic298 commented on GitHub (May 4, 2026):
yes the hidden model is only hidden from the UI. If you want to hide it from models endpoint open a feature request. Not sure if technically easy possible since other UI elements may depend on the /models endpoint