Disabled models appear in the chat interface. #3381

Closed
opened 2025-11-11 15:30:37 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @FischLu on GitHub (Jan 23, 2025).

Bug Report

Installation Method

docker via openai usage only

docker run -d -p 3000:8080 -e OPENAI_API_KEY=your_secret_key -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main

Environment

  • Open WebUI Version: v0.5.6

  • Operating System: debian 12

  • Browser (if applicable): firefox 134

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

If a model is disabled in the configuration interface, it should not appear in the list of selectable models.

Actual Behavior:

I still can see some disabled models

Description

Bug Summary:
I imported OpenRouter's models through their API and then closed the ones I didn't need. However, I found that some models still appears in the chat interface's model selection list even after being disabled in the configuration interface. I've tried many times, even resetting all models, restart container, rerun container, but it doesn't help. Moreover, the problematic model is different each time. For example, this time Llama3.3 can't be removed, and after resetting, Gemma 2 can't be removed. In the screenshot below, I provided two examples: Google's Gemma 2 9B and Microsoft's Phi-3 Medium 128K Instruct, both of which were disabled in the configuration interface but still appear in the chat interface. In fact, there are many more models that cannot be closed.

Reproduction Details

Steps to Reproduce:

Add the OpenRouter API, and the system will automatically import their models. Then, try to disable most of the models, leaving only a few models, which will reproduce the problem. Additionally, in the connection configuration interface, I can input the model ID, and according to the system description, this should only import the model I entered. However, the system actually imported all of OpenRouter's models, so I had to disable them manually.

Logs and Screenshots

Image Image Image
Originally created by @FischLu on GitHub (Jan 23, 2025). # Bug Report ## Installation Method docker via openai usage only ``` docker run -d -p 3000:8080 -e OPENAI_API_KEY=your_secret_key -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main ``` ## Environment - **Open WebUI Version:** v0.5.6 - **Operating System:** debian 12 - **Browser (if applicable):** firefox 134 **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. - [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: If a model is disabled in the configuration interface, it should not appear in the list of selectable models. ## Actual Behavior: I still can see some disabled models ## Description **Bug Summary:** I imported OpenRouter's models through their API and then closed the ones I didn't need. However, I found that some models still appears in the chat interface's model selection list even after being disabled in the configuration interface. I've tried many times, even resetting all models, restart container, rerun container, but it doesn't help. Moreover, the problematic model is different each time. For example, this time Llama3.3 can't be removed, and after resetting, Gemma 2 can't be removed. In the screenshot below, I provided two examples: Google's Gemma 2 9B and Microsoft's Phi-3 Medium 128K Instruct, both of which were disabled in the configuration interface but still appear in the chat interface. In fact, there are many more models that cannot be closed. ## Reproduction Details **Steps to Reproduce:** Add the OpenRouter API, and the system will automatically import their models. Then, try to disable most of the models, leaving only a few models, which will reproduce the problem. Additionally, in the connection configuration interface, I can input the model ID, and according to the system description, this should only import the model I entered. However, the system actually imported all of OpenRouter's models, so I had to disable them manually. ## Logs and Screenshots <img width="1119" alt="Image" src="https://github.com/user-attachments/assets/6a2b7c18-6cc8-44a8-88b4-3f5211102f0b" /> <img width="1133" alt="Image" src="https://github.com/user-attachments/assets/1fe96445-063f-4b08-8c35-81e09dfe1474" /> <img width="515" alt="Image" src="https://github.com/user-attachments/assets/2b0b9ebc-569d-4567-889c-2ce62aa77551" />
Author
Owner

@gaoxiaobei commented on GitHub (Jan 23, 2025):

I've also encountered it. This is a new issue. It's coming with v0.5.6. I recently requested for a feature here and maybe it's linked with that?

@gaoxiaobei commented on GitHub (Jan 23, 2025): I've also encountered it. This is a new issue. It's coming with v0.5.6. I recently requested for a feature [here](https://github.com/open-webui/open-webui/issues/8662) and maybe it's linked with that?
Author
Owner

@FischLu commented on GitHub (Jan 23, 2025):

I've also encountered it. This is a new issue. It's coming with v0.5.6. I recently requested for a feature here and maybe it's linked with that?

not sure. I checked the webui.db from my container, which is a SQLite database used by the app. In fact, I used the “is_active” field in the model table to filter the list of models, and only the models I enabled appeared here. So, the models that shouldn't appear on the webpage interface are coming from somewhere else.

@FischLu commented on GitHub (Jan 23, 2025): > I've also encountered it. This is a new issue. It's coming with v0.5.6. I recently requested for a feature [here](https://github.com/open-webui/open-webui/issues/8662) and maybe it's linked with that? not sure. I checked the webui.db from my container, which is a SQLite database used by the app. In fact, I used the “is_active” field in the model table to filter the list of models, and only the models I enabled appeared here. So, the models that shouldn't appear on the webpage interface are coming from somewhere else.
Author
Owner

@FischLu commented on GitHub (Jan 23, 2025):

I manually deleted some models from the SQLite database that I couldn't disable, and then imported the database into my container. I expected these models to completely disappear, but they still appeared in the chat interface. However, when I went to check the configuration interface again, I found that these models were recovered from somewhere but shown as enabled this time. So, after I manually disabled them, they disappeared from the chat interface. I suspect that there might be some caching mechanism that didn't synchronize with the SQLite database configuration?

@FischLu commented on GitHub (Jan 23, 2025): I manually deleted some models from the SQLite database that I couldn't disable, and then imported the database into my container. I expected these models to completely disappear, but they still appeared in the chat interface. However, when I went to check the configuration interface again, I found that these models were recovered from somewhere but shown as enabled this time. So, after I manually disabled them, they disappeared from the chat interface. I suspect that there might be some caching mechanism that didn't synchronize with the SQLite database configuration?
Author
Owner

@silentoplayz commented on GitHub (Jan 23, 2025):

Related issue - https://github.com/open-webui/open-webui/issues/8807

@silentoplayz commented on GitHub (Jan 23, 2025): Related issue - https://github.com/open-webui/open-webui/issues/8807
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#3381