[GH-ISSUE #16689] issue: Providers setting the "name" attribute of of models to null breaks things #56676

Closed
opened 2026-05-05 19:55:00 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @nkukard on GitHub (Aug 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16689

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.22

Ollama Version (if applicable)

No response

Operating System

Linux

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

[I read through the confirmations but a lot of this is not relevant]

This issue pertains to Mistral.ai and them setting one of the model names to null. This breaks the OpenWebUI interface. See https://github.com/open-webui/open-webui/discussions/4150

I'd expect Open WebUI not to backtrace and lock one out of the interface when this happens.

Actual Behavior

Web interface is locked up, backend backtraces endlessly.

Steps to Reproduce

  1. Sign up on Mistral.ai
  2. Create an API key in the default namespace
  3. Add a connection in OpenWebUI
  4. Refresh page and get an endless loading symbol and backtraces on the server console

Absolutely no other configuration, as easy as that.

Logs & Screenshots

Line 45 of models output: https://github.com/user-attachments/files/21823517/example_models.json

Backtrace: https://github.com/user-attachments/files/21823518/backtrace.txt

Models dump in Python...

Image

Additional Information

I'll be submitting a patch shortly which works around this edge case.

Originally created by @nkukard on GitHub (Aug 17, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16689 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.22 ### Ollama Version (if applicable) _No response_ ### Operating System Linux ### 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 [I read through the confirmations but a lot of this is not relevant] This issue pertains to Mistral.ai and them setting one of the model names to null. This breaks the OpenWebUI interface. See https://github.com/open-webui/open-webui/discussions/4150 I'd expect Open WebUI not to backtrace and lock one out of the interface when this happens. ### Actual Behavior Web interface is locked up, backend backtraces endlessly. ### Steps to Reproduce 1. Sign up on Mistral.ai 2. Create an API key in the default namespace 3. Add a connection in OpenWebUI 4. Refresh page and get an endless loading symbol and backtraces on the server console Absolutely no other configuration, as easy as that. ### Logs & Screenshots Line 45 of models output: https://github.com/user-attachments/files/21823517/example_models.json Backtrace: https://github.com/user-attachments/files/21823518/backtrace.txt Models dump in Python... <img width="720" height="534" alt="Image" src="https://github.com/user-attachments/assets/cae45479-37ef-47a4-9a95-f9718be5a224" /> ### Additional Information I'll be submitting a patch shortly which works around this edge case.
GiteaMirror added the bug label 2026-05-05 19:55:00 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#56676