issue: Disabled models on 0.11.0 disappear from the list after upgrading to 0.11.1

[fnf]

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 have checked whether this issue is already fixed on the dev branch or in the latest source.
• I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

v0.11.1

Ollama Version (if applicable)

No response

Operating System

Windows 11

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 upgrading to v0.11.1 today, I encountered an issue with models not available for use. It appears to have impacted all models that were disabled before the upgrade (and only those models). The models that were enabled remain available for use.

I have not tried downgrading to 0.11.0 as I"m not sure if Open WebUI is designed to be backward-compatible, out of concerns of database schema changes.

Actual Behavior

Only models that were enabled on v.0.11.0 are available for use on v0.11.1 . Removing the connection and adding it back doesn't work.

Steps to Reproduce

I have tried the following to test:

• Removing the connection (to confirm that the still-available model is now gone), then re-adding it back does not work: only the models that were available will come back, the models that weren't available before the removal/re-add remained unavailable.
• Adding a new connection (with the same Base URL and API key, but with a different Prefix) allows the models to show up as expected.
• Adding the same connection i.e., same Base URL and API key but no prefix in another test account worked.
• Adding the same connection i.e., same Base URL and API key but no prefix to my own account (that is, essentially a duplicate connection) does not work.

Logs & Screenshots

Please refer to the attached screenshots for clarity.

These are my current connections:

On v0.11.0 I'd get over 300 models, but on v0.11.1 I only have 31 models, which are the number of models I had enabled before the upgrade.

x.AI only has a single model (grok-4.6), which is what I use:

I added another connection to x.AI with a new prefix here:

which allows them to show up:

So it looks like there's an issue with all the models that used to be disabled after the upgrade to v0.11.1 .

Additional Information

No response

[owui-terminator]

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

1. 🟣 #29036 issue: disabling a model in the admin Models list makes it disappear with no way to re-enable it
   This is the closest match: it reports that disabled models disappear from the Models list and cannot be re-enabled. The new issue also says models disabled before the v0.11.1 upgrade disappear, with only enabled models remaining visible.
   by silentoplayz · bug, confirmed issue

2. 🟣 #27702 issue: workspace models missing from Admin Settings > Models, cannot be ordered, set as default or pinned (v0.11.0 regression)
   This is a v0.11.0 regression involving models missing from the Admin Settings > Models list after an upgrade. While it focuses on workspace models rather than disabled ones, it is clearly in the same model-list regression area.
   by garypiner · bug

3. 🟣 #26788 issue: User Model Access for removed models persists
   This issue is about model access state persisting incorrectly after models are removed. It is not the same symptom, but it is related to stale model state surviving provider/model changes, which is similar to the upgraded disabled-models problem.
   by gregtakacs · bug

---

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.