mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #11508] issue: Disabled models still appear in model selection #54921
Reference in New Issue
Block a user
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?
Originally created by @jcrabapple on GitHub (Mar 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11508
Check Existing Issues
Installation Method
Docker
Open WebUI Version
5.20
Ollama Version (if applicable)
No response
Operating System
Fedora Linux 40
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Models disabled from the Settings>Models screen should not show up in the Models dropdown selection on the chat screen.
Actual Behavior
A few of the disabled models still show up in the dropdown list i.e. Microsoft: Phi-3 Mini 128K Instruct
Steps to Reproduce
Logs & Screenshots
Additional Information
No response
@Classic298 commented on GitHub (Mar 10, 2025):
Press CTRL+SHIFT+R or delete cache (or, actually, a normal refresh should suffice).
Going straight from admin panel to homepage doesn't refresh anything. You need to refresh the page then it should reload the model list
From your "steps to reproduce" I didn't see you refresh the page
@jcrabapple commented on GitHub (Mar 10, 2025):
Sorry, I did hard refresh the page. The disabled models were still there. Cleared cache and tried a different browser. Still there.
@Classic298 commented on GitHub (Mar 10, 2025):
Interesting. I regularly disable some models and enable others. After refreshing they are always gone from the model list.
Can you add additional screenshots, or better a screen recording of disabling a model, going to home screen, refreshing and then showing it's still there? I really cannot reproduce this on my end. Never had such an issue.
@jcrabapple commented on GitHub (Mar 10, 2025):
I did some more extensive searching and found other bug reports the same as or similar to mine:
https://github.com/open-webui/open-webui/discussions/7912
https://github.com/open-webui/open-webui/issues/9577
@thejudge22 commented on GitHub (Mar 10, 2025):
Can confirm I'm experiencing the same issues as reported by OP. I've recorded a video showing this behavior. Recorded in a Chrome Incognito window.
https://filedn.com/lKyCkKH4dQqVFkh4zuHDVqY/Screen%20Recording%202025-03-10%20at%2011.44.29%E2%80%AFAM.mov
@frenzybiscuit commented on GitHub (Mar 10, 2025):
Models set to private do not show up under regular (non-admin) accounts.
I'd just do that and then disable the models at the same time.
@bjj commented on GitHub (Mar 16, 2025):
Not sure if there is any plan to fix this, but it would be nice if the model dropdown updated automatically with model availability changes. It's clear in many cases that the backend knows about model availability (whether due to server availability or other reasons) but the only way to refresh the dropdown is to reload.
@bannert1337 commented on GitHub (Mar 19, 2025):
Also reported this, same problem:
https://github.com/open-webui/open-webui/issues/11669
https://github.com/open-webui/open-webui/discussions/11689
@bannert1337 commented on GitHub (Mar 19, 2025):
It seems like this might be related in a way to other bugs I reported a while back, which also affected persistence of changes:
https://github.com/open-webui/open-webui/issues/9664
https://github.com/open-webui/open-webui/issues/9578
https://github.com/open-webui/open-webui/issues/8818
@bannert1337 commented on GitHub (Mar 20, 2025):
Just tried this out on a completely fresh installation on a new system.
Issue happens again.
Used the OpenRouter function and disabled the majority of models.
@bannert1337 commented on GitHub (Mar 20, 2025):
The issue is caused by these checks:
https://github.com/open-webui/open-webui/discussions/10883#discussioncomment-12361214
@bannert1337 commented on GitHub (Mar 21, 2025):
Affected are models of OpenRouter that contain no colon (
:), which causes the split on colon (:) to fail.@hojin-koh commented on GitHub (Apr 12, 2025):
I had the same issue when connecting to OpenRouter's (supposedly) OpenAI-compatible endpoint in the current v0.6.2 release. Of course also tried force-refresh. That's quite annoying since OpenRouter has a LOT of models that would show up in this way...
Can confirm applying a quick dirty patch to comment out the split-on-colon condition against v0.6.2 (installed through pip) make these disabled model disappear in model selection:
But I'm not sure about the side effects.
@tjbck commented on GitHub (Apr 13, 2025):
Might be addressed with
daabc188e8