github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-08-30 17:25:30 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

issue: Unable to regenerate answer on provider error #6638

New Issue
Closed
opened 2025-11-11 17:01:59 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-11 17:01:59 -06:00
Owner
Copy Link
Copy Source

Originally created by @bibendi on GitHub (Oct 9, 2025).

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.33

Ollama Version (if applicable)

No response

Operating System

Ubuntu

Browser (if applicable)

Chrome

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 the provider returns an error, I can click on regenerate button

Actual Behavior

When the provider returns an error, I cannot click on regenerate button

Steps to Reproduce

  1. Get an error from a provider
  2. Cannot see the regenerate button

Logs & Screenshots

Image

Additional Information

No response

Originally created by @bibendi on GitHub (Oct 9, 2025). ### 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 am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.33 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### Browser (if applicable) Chrome ### 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 the provider returns an error, I can click on regenerate button ### Actual Behavior When the provider returns an error, I cannot click on regenerate button ### Steps to Reproduce 1. Get an error from a provider 2. Cannot see the regenerate button ### Logs & Screenshots <img width="554" height="517" alt="Image" src="https://github.com/user-attachments/assets/50f2cd13-0af2-49a8-bb77-76a0f0592074" /> ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 17:01:59 -06:00
GiteaMirror commented 2025-11-11 17:02:00 -06:00
Author
Owner
Copy Link
Copy Source

@ShirasawaSama commented on GitHub (Oct 9, 2025):

This appears to be an issue with your LLM service provider and seems unrelated to Open-WebUI. Please check the response from your service provider.

@ShirasawaSama commented on GitHub (Oct 9, 2025): This appears to be an issue with your LLM service provider and seems unrelated to Open-WebUI. Please check the response from your service provider.
GiteaMirror commented 2025-11-11 17:02:00 -06:00
Author
Owner
Copy Link
Copy Source

@bibendi commented on GitHub (Oct 9, 2025):

Just to clarify — the provider error itself isn't my main concern. It happens only 1–2 times per day and when I manage to regenerate the request the model returns a valid response. The problem is that the UI does not show the “Regenerate” button (or other retry controls) when the provider error occurs, so I can’t trigger the regeneration from the UI.

Repro steps:

Running Open WebUI v0.6.33 (Docker on Ubuntu) in Chrome.
Send a request that hits the provider error (the error occurs intermittently).
The provider returns an error, and the UI shows an error message, but the “Regenerate” button/controls are not rendered or are not clickable.
If I manually re-run the request (or retry via other means), the response is returned correctly.
Expected: when a provider error occurs there should still be visible/usable retry controls (e.g. “Regenerate”) so the user can try again.

@bibendi commented on GitHub (Oct 9, 2025): Just to clarify — the provider error itself isn't my main concern. It happens only 1–2 times per day and when I manage to regenerate the request the model returns a valid response. The problem is that the UI does not show the “Regenerate” button (or other retry controls) when the provider error occurs, so I can’t trigger the regeneration from the UI. Repro steps: Running Open WebUI v0.6.33 (Docker on Ubuntu) in Chrome. Send a request that hits the provider error (the error occurs intermittently). The provider returns an error, and the UI shows an error message, but the “Regenerate” button/controls are not rendered or are not clickable. If I manually re-run the request (or retry via other means), the response is returned correctly. Expected: when a provider error occurs there should still be visible/usable retry controls (e.g. “Regenerate”) so the user can try again.
GiteaMirror commented 2025-11-11 17:02:00 -06:00
Author
Owner
Copy Link
Copy Source

@ShirasawaSama commented on GitHub (Oct 9, 2025):

Just to clarify — the provider error itself isn't my main concern. It happens only 1–2 times per day and when I manage to regenerate the request the model returns a valid response. The problem is that the UI does not show the “Regenerate” button (or other retry controls) when the provider error occurs, so I can’t trigger the regeneration from the UI.

Repro steps:

Running Open WebUI v0.6.33 (Docker on Ubuntu) in Chrome. Send a request that hits the provider error (the error occurs intermittently). The provider returns an error, and the UI shows an error message, but the “Regenerate” button/controls are not rendered or are not clickable. If I manually re-run the request (or retry via other means), the response is returned correctly. Expected: when a provider error occurs there should still be visible/usable retry controls (e.g. “Regenerate”) so the user can try again.

This is indeed an issue. I think it's best to let the repository owner decide.

@ShirasawaSama commented on GitHub (Oct 9, 2025): > Just to clarify — the provider error itself isn't my main concern. It happens only 1–2 times per day and when I manage to regenerate the request the model returns a valid response. The problem is that the UI does not show the “Regenerate” button (or other retry controls) when the provider error occurs, so I can’t trigger the regeneration from the UI. > > Repro steps: > > Running Open WebUI v0.6.33 (Docker on Ubuntu) in Chrome. Send a request that hits the provider error (the error occurs intermittently). The provider returns an error, and the UI shows an error message, but the “Regenerate” button/controls are not rendered or are not clickable. If I manually re-run the request (or retry via other means), the response is returned correctly. Expected: when a provider error occurs there should still be visible/usable retry controls (e.g. “Regenerate”) so the user can try again. This is indeed an issue. I think it's best to let the repository owner decide.
GiteaMirror commented 2025-11-11 17:02:00 -06:00
Author
Owner
Copy Link
Copy Source

@rgaricano commented on GitHub (Oct 9, 2025):

can you provide log of the error? (for a quicker debug)

@rgaricano commented on GitHub (Oct 9, 2025): can you provide log of the error? (for a quicker debug)
GiteaMirror commented 2025-11-11 17:02:01 -06:00
Author
Owner
Copy Link
Copy Source

@tjbck commented on GitHub (Oct 9, 2025):

  • we'll need a clear instructions on how to reproduce this issue.
@tjbck commented on GitHub (Oct 9, 2025): + we'll need a clear instructions on how to reproduce this issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#6638