[GH-ISSUE #15375] issue: When my Open-WebUI generation exits directly without interruption midway, re-entering the dialog box will result in a loop on the loading screen. #17548

New Issue

GiteaMirror · 2026-04-19T23:19:54-05:00

GiteaMirror commented

2026-04-19 23:19:54 -05:00

Originally created by @Frost2002 on GitHub (Jun 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15375

Originally assigned to: @tjbck on GitHub.

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

v0.6.15

Ollama Version (if applicable)

latest

Operating System

Windows Server 2025 DataCenter

Browser (if applicable)

Edge Stable:latest

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

When an exception occurs while Open-WebUI calls the DeepSeek API, the automatic interruption does not affect viewing the conversation history next time.

Actual Behavior

After a series of dialogues, if DeepSeek encounters an exception and exits without manual intervention, it will cause the historical records of that conversation to fail to load properly.

Steps to Reproduce

Open Open-WebUI
Enable the local deployment of Searxng for online searching, and ask questions to DeepSeek-Reasoner (official API)
After asking 3 to 5 questions, it will prompt that the model cannot be found, or cannot generate a search
At this moment, there is still a stop button in the lower right corner, but clicking it has no effect
After refreshing the page, it is impossible to view the conversation history in the current dialogue box, and the top keeps displaying 'Loading'.

Logs & Screenshots

Additional Information

No response

Originally created by @Frost2002 on GitHub (Jun 28, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/15375 Originally assigned to: @tjbck on GitHub. ### 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 v0.6.15 ### Ollama Version (if applicable) latest ### Operating System Windows Server 2025 DataCenter ### Browser (if applicable) Edge Stable:latest ### 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 When an exception occurs while Open-WebUI calls the DeepSeek API, the automatic interruption does not affect viewing the conversation history next time. ### Actual Behavior After a series of dialogues, if DeepSeek encounters an exception and exits without manual intervention, it will cause the historical records of that conversation to fail to load properly. ### Steps to Reproduce 1. Open Open-WebUI 2. Enable the local deployment of Searxng for online searching, and ask questions to DeepSeek-Reasoner (official API) 3. After asking 3 to 5 questions, it will prompt that the model cannot be found, or cannot generate a search 4. At this moment, there is still a stop button in the lower right corner, but clicking it has no effect 5. After refreshing the page, it is impossible to view the conversation history in the current dialogue box, and the top keeps displaying 'Loading'. ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/f533743d-cf5f-47b8-b29e-a0885f0d7a94) ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-19 23:19:54 -05:00

GiteaMirror closed this issue

2026-04-19 23:19:55 -05:00

GiteaMirror commented

2026-04-19 23:19:57 -05:00

@tjbck commented on GitHub (Jun 30, 2025):

Related: #13027

@tjbck commented on GitHub (Jun 30, 2025): Related: #13027

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#17548