github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-11 08:22:09 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #14794] issue: Conversations are lost, requests never submitted despite UI showing them being worked upon, general disharmony #17363

New Issue
Closed
opened 2026-04-19 23:05:46 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-19 23:05:46 -05:00
Owner
Copy Link

Originally created by @sempervictus on GitHub (Jun 9, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14794

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

latest

Ollama Version (if applicable)

No response

Operating System

Linux

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

State presented in current UI is consistent in back-end and upon page refresh

Actual Behavior

Complex conversation trees (more than one model, forking, changing model counts, setting parameters for the models) show "everyting working" on the front-end but models never receive requests and refreshing the window "destroys" entire branches of conversation.

Steps to Reproduce

  1. Start with OpenWebUI ~ 0.6 when it was the latest docker image
  2. Upgrade iteratively while building up conversations to present
  3. Observe conversations and communication with models disconnect from what is represented in UI

Logs & Screenshots

This is the fun part: nothing is logged when i attempt to send a request to a model but the UI pretends like its waiting for the request.

Additional Information

No response

Originally created by @sempervictus on GitHub (Jun 9, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14794 ### 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 latest ### Ollama Version (if applicable) _No response_ ### Operating System Linux ### 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 State presented in current UI is consistent in back-end and upon page refresh ### Actual Behavior Complex conversation trees (more than one model, forking, changing model counts, setting parameters for the models) show "everyting working" on the front-end but models never receive requests and refreshing the window "destroys" entire branches of conversation. ### Steps to Reproduce 1. Start with OpenWebUI ~ 0.6 when it was the latest docker image 2. Upgrade iteratively while building up conversations to present 3. Observe conversations and communication with models disconnect from what is represented in UI ### Logs & Screenshots This is the fun part: _nothing is logged_ when i attempt to send a request to a model but the UI pretends like its waiting for the request. ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-19 23:05:46 -05:00
GiteaMirror commented 2026-04-19 23:05:47 -05:00
Author
Owner
Copy Link

@JoeChen2me commented on GitHub (Jun 9, 2025):

Maybe you can check the container logs of Docker, I'm also experiencing this issue. When I initiate a request, the UI interface shows it is in progress, but my API server does not receive the request. Usually, it takes 1-2 minutes before the API request is made. According to the review of the logs, I found that during this period, the app's version was being requested, which consumed a lot of time.

Here is the log from my test. From receiving the request from the frontend to actually sending the completion request to the API, there was a 2-minute interval.

Task IDs for chat 153a9e2e-eeb2-4abf-abae-f54b90c1a4cb: []
2025-06-09 10:53:52.409 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /api/tasks/chat/153a9e2e-eeb2-4abf-abae-f54b90c1a4cb HTTP/1.1" 200 - {}
2025-06-09 10:53:52.845 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /ollama/api/version HTTP/1.1" 200 - {}
2025-06-09 10:53:53.263 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:53:55.746 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 216.247.110.21:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:54:04.955 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /manifest.json HTTP/1.1" 200 - {}
2025-06-09 10:54:04.958 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/immutable/assets/26.wEbTgpRj.css HTTP/1.1" 200 - {}
2025-06-09 10:54:15.285 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "POST /api/v1/chats/153a9e2e-eeb2-4abf-abae-f54b90c1a4cb HTTP/1.1" 200 - {}
2025-06-09 10:54:15.696 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /api/v1/chats/?page=1 HTTP/1.1" 200 - {}
2025-06-09 10:54:19.420 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:54:53.285 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:55:19.699 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:55:53.288 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:55:55.573 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 216.247.110.21:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:56:19.743 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:56:53.297 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:56:55.472 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 216.247.110.21:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:57:20.895 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {}
2025-06-09 10:57:25.852 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 205.198.68.146:0 - "GET /_app/version.json HTTP/1.1" 304 - {}
<!-- gh-comment-id:2954528465 --> @JoeChen2me commented on GitHub (Jun 9, 2025): Maybe you can check the container logs of Docker, I'm also experiencing this issue. When I initiate a request, the UI interface shows it is in progress, but my API server does not receive the request. Usually, it takes 1-2 minutes before the API request is made. According to the review of the logs, I found that during this period, the app's version was being requested, which consumed a lot of time. Here is the log from my test. From receiving the request from the frontend to actually sending the completion request to the API, there was a 2-minute interval. ```sh Task IDs for chat 153a9e2e-eeb2-4abf-abae-f54b90c1a4cb: [] 2025-06-09 10:53:52.409 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /api/tasks/chat/153a9e2e-eeb2-4abf-abae-f54b90c1a4cb HTTP/1.1" 200 - {} 2025-06-09 10:53:52.845 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /ollama/api/version HTTP/1.1" 200 - {} 2025-06-09 10:53:53.263 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:53:55.746 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 216.247.110.21:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:54:04.955 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /manifest.json HTTP/1.1" 200 - {} 2025-06-09 10:54:04.958 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/immutable/assets/26.wEbTgpRj.css HTTP/1.1" 200 - {} 2025-06-09 10:54:15.285 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "POST /api/v1/chats/153a9e2e-eeb2-4abf-abae-f54b90c1a4cb HTTP/1.1" 200 - {} 2025-06-09 10:54:15.696 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /api/v1/chats/?page=1 HTTP/1.1" 200 - {} 2025-06-09 10:54:19.420 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:54:53.285 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:55:19.699 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:55:53.288 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:55:55.573 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 216.247.110.21:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:56:19.743 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:56:53.297 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 110.65.147.203:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:56:55.472 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 216.247.110.21:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:57:20.895 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 139.162.17.136:0 - "GET /_app/version.json HTTP/1.1" 200 - {} 2025-06-09 10:57:25.852 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 205.198.68.146:0 - "GET /_app/version.json HTTP/1.1" 304 - {} ```
GiteaMirror commented 2026-04-19 23:05:48 -05:00
Author
Owner
Copy Link

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

unable to reproduce

<!-- gh-comment-id:2954753593 --> @tjbck commented on GitHub (Jun 9, 2025): unable to reproduce
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 Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#17363
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?