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 am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
v0.6.34
Ollama Version (if applicable)
No response
Operating System
rhel9
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
Hello, I am using open-webui as a front end connected to my llm provider.
The provider sends the Open-Webui errors to show the client in certain scenarios in the chat ui, and this worked fine in version v0.6.10.
Actual Behavior
We now upgraded to v0.6.34, and instead of showcasing the errors to the client, the chat just start loading endlessly.
Any idea what can cause this?
Steps to Reproduce
Use open-webui v0.6.34
Write an llm provider that sends errors to return to the client if they have insufficient tokens etc.
Replicate the client error scenario and see if the webui shows the error to the client
Logs & Screenshots
I don't see any error logs in the open-webui pod
Additional Information
No response
Originally created by @TamKej on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19085
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] 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!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
v0.6.34
### Ollama Version (if applicable)
_No response_
### Operating System
rhel9
### 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
Hello, I am using open-webui as a front end connected to my llm provider.
The provider sends the Open-Webui errors to show the client in certain scenarios in the chat ui, and this worked fine in version v0.6.10.
### Actual Behavior
We now upgraded to v0.6.34, and instead of showcasing the errors to the client, the chat just start loading endlessly.
Any idea what can cause this?
### Steps to Reproduce
1. Use open-webui v0.6.34
2. Write an llm provider that sends errors to return to the client if they have insufficient tokens etc.
3. Replicate the client error scenario and see if the webui shows the error to the client
### Logs & Screenshots
I don't see any error logs in the open-webui pod
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-15 14:24:31 -05:00
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 @TamKej on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19085
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.34
Ollama Version (if applicable)
No response
Operating System
rhel9
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Hello, I am using open-webui as a front end connected to my llm provider.
The provider sends the Open-Webui errors to show the client in certain scenarios in the chat ui, and this worked fine in version v0.6.10.
Actual Behavior
We now upgraded to v0.6.34, and instead of showcasing the errors to the client, the chat just start loading endlessly.
Any idea what can cause this?
Steps to Reproduce
Logs & Screenshots
I don't see any error logs in the open-webui pod
Additional Information
No response
@tjbck commented on GitHub (Nov 11, 2025):
Unable to reproduce, keep us updated.