Originally created by @bgeneto on GitHub (Oct 16, 2024).
Bug Report
Important: Before submitting a bug report, please check whether a similar issue or feature request has already been posted in the Issues or Discussions section. It's likely we're already tracking it. In case of uncertainty, initiate a discussion post first. This helps us all to efficiently focus on improving the project.
Let's collaborate respectfully. If you bring negativity, please understand our capacity to engage may be limited. If you're open to learning and communicating constructively, we're more than happy to assist you. Remember, Open WebUI is a volunteer-driven project maintained by a single maintainer, supported by our amazing contributors who also manage full-time jobs. We respect your time; please respect ours. If you have an issue, We highly encourage you to submit a pull request or to fork the project. We actively work to prevent contributor burnout to preserve the quality and continuity of Open WebUI.
Installation Method
[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]
Environment
**Open WebUI Version:**v0.3.32
Ollama (if applicable): n/a
Operating System: Debian 12
Browser (if applicable): Chrome, Edge, Firefox
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 included the browser console logs.
I have included the Docker container logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
Assistant response should appear (word-by-word with Stream Chat Response is On).
Actual Behavior:
No response.
Description
Bug Summary:
Responses are not streamed (char by char or word-by-word) unless Fluidly stream large external response chunks is turned On. Also if you assistant response is large, DeepSeek (and other providers) does not return a response.
Reproduction Details
Steps to Reproduce:
Ask something non-trivial and wait (forever) for a response.
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
Originally created by @bgeneto on GitHub (Oct 16, 2024).
# Bug Report
**Important: Before submitting a bug report, please check whether a similar issue or feature request has already been posted in the Issues or Discussions section. It's likely we're already tracking it. In case of uncertainty, initiate a discussion post first. This helps us all to efficiently focus on improving the project.**
**Let's collaborate respectfully. If you bring negativity, please understand our capacity to engage may be limited. If you're open to learning and communicating constructively, we're more than happy to assist you. Remember, Open WebUI is a volunteer-driven project maintained by a single maintainer, supported by our amazing contributors who also manage full-time jobs. We respect your time; please respect ours. If you have an issue, We highly encourage you to submit a pull request or to fork the project. We actively work to prevent contributor burnout to preserve the quality and continuity of Open WebUI.**
## Installation Method
[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]
## Environment
- **Open WebUI Version:**v0.3.32
- **Ollama (if applicable):** n/a
- **Operating System:** Debian 12
- **Browser (if applicable):** Chrome, Edge, Firefox
**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 included the browser console logs.
- [ ] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
Assistant response should appear (word-by-word with Stream Chat Response is On).
## Actual Behavior:
No response.

## Description
**Bug Summary:**
Responses are not streamed (char by char or word-by-word) unless Fluidly stream large external response chunks is turned On. Also if you assistant response is large, DeepSeek (and other providers) does not return a response.
## Reproduction Details
**Steps to Reproduce:**
Ask something non-trivial and wait (forever) for a response.
## Logs and Screenshots
https://github.com/user-attachments/assets/292a57f9-23eb-4274-8fa5-ff1f76e5e72a
**Browser Console Logs:**
see attached video.
**Docker Container Logs:**
n/a
**Screenshots/Screen Recordings (if applicable):**
[Attach any relevant screenshots to help illustrate the issue]
## Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
## Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
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 @bgeneto on GitHub (Oct 16, 2024).
Bug Report
Important: Before submitting a bug report, please check whether a similar issue or feature request has already been posted in the Issues or Discussions section. It's likely we're already tracking it. In case of uncertainty, initiate a discussion post first. This helps us all to efficiently focus on improving the project.
Let's collaborate respectfully. If you bring negativity, please understand our capacity to engage may be limited. If you're open to learning and communicating constructively, we're more than happy to assist you. Remember, Open WebUI is a volunteer-driven project maintained by a single maintainer, supported by our amazing contributors who also manage full-time jobs. We respect your time; please respect ours. If you have an issue, We highly encourage you to submit a pull request or to fork the project. We actively work to prevent contributor burnout to preserve the quality and continuity of Open WebUI.
Installation Method
[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]
Environment
**Open WebUI Version:**v0.3.32
Ollama (if applicable): n/a
Operating System: Debian 12
Browser (if applicable): Chrome, Edge, Firefox
Confirmation:
Expected Behavior:
Assistant response should appear (word-by-word with Stream Chat Response is On).
Actual Behavior:
No response.

Description
Bug Summary:
Responses are not streamed (char by char or word-by-word) unless Fluidly stream large external response chunks is turned On. Also if you assistant response is large, DeepSeek (and other providers) does not return a response.
Reproduction Details
Steps to Reproduce:
Ask something non-trivial and wait (forever) for a response.
Logs and Screenshots
https://github.com/user-attachments/assets/292a57f9-23eb-4274-8fa5-ff1f76e5e72a
Browser Console Logs:
see attached video.
Docker Container Logs:
n/a
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!