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.23, 0.6.24
Ollama Version (if applicable)
No response
Operating System
Docker Image
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
Azure AI Foundry has been functional as an added connection until 0.6.23
Actual Behavior
After upgrading to 0.6.23, all models fail with the following error on the docker console:
| ERROR | open_webui.routers.openai:generate_chat_completion:911 - 200, message='Attempt to decode JSON with unexpected mimetype: ', url='********'
Steps to Reproduce
Add a connection to an Azure AI Foundry endpoint, and then create a new chat with a model in that deployment
Logs & Screenshots
| ERROR | open_webui.routers.openai:generate_chat_completion:911 - 200, message='Attempt to decode JSON with unexpected mimetype: ', url='********'
No browser console errors
Additional Information
No response
Originally created by @decent-engineer-decent-datascientist on GitHub (Aug 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16819
### 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.23, 0.6.24
### Ollama Version (if applicable)
_No response_
### Operating System
Docker Image
### 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
Azure AI Foundry has been functional as an added connection until 0.6.23
### Actual Behavior
After upgrading to 0.6.23, all models fail with the following error on the docker console:
| ERROR | open_webui.routers.openai:generate_chat_completion:911 - 200, message='Attempt to decode JSON with unexpected mimetype: ', url='********'
### Steps to Reproduce
Add a connection to an Azure AI Foundry endpoint, and then create a new chat with a model in that deployment
### Logs & Screenshots
| ERROR | open_webui.routers.openai:generate_chat_completion:911 - 200, message='Attempt to decode JSON with unexpected mimetype: ', url='********'
No browser console errors
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-19 23:57:58 -05:00
@decent-engineer-decent-datascientist commented on GitHub (Aug 22, 2025):
There really isn't anything in there around the error; it's just that single line and no errors on the front end.
<!-- gh-comment-id:3214906999 -->
@decent-engineer-decent-datascientist commented on GitHub (Aug 22, 2025):
There really isn't anything in there around the error; it's just that single line and no errors on the front end.
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 @decent-engineer-decent-datascientist on GitHub (Aug 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16819
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.23, 0.6.24
Ollama Version (if applicable)
No response
Operating System
Docker Image
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Azure AI Foundry has been functional as an added connection until 0.6.23
Actual Behavior
After upgrading to 0.6.23, all models fail with the following error on the docker console:
| ERROR | open_webui.routers.openai:generate_chat_completion:911 - 200, message='Attempt to decode JSON with unexpected mimetype: ', url='********'
Steps to Reproduce
Add a connection to an Azure AI Foundry endpoint, and then create a new chat with a model in that deployment
Logs & Screenshots
| ERROR | open_webui.routers.openai:generate_chat_completion:911 - 200, message='Attempt to decode JSON with unexpected mimetype: ', url='********'
No browser console errors
Additional Information
No response
@tjbck commented on GitHub (Aug 22, 2025):
Can we get more backend logs?
@decent-engineer-decent-datascientist commented on GitHub (Aug 22, 2025):
There really isn't anything in there around the error; it's just that single line and no errors on the front end.