github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 19:38:46 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #12396] issue: Blank Screen after successful login #55249

New Issue
Closed
opened 2026-05-05 17:22:09 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-05 17:22:09 -05:00
Owner
Copy Link

Originally created by @frk-ti8m on GitHub (Apr 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12396

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.0

Ollama Version (if applicable)

without ollama

Operating System

Ubuntu 22.04

Browser (if applicable)

134.0.6998.166

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 listed steps to reproduce the bug in detail.

Expected Behavior

I expected Open WebUI to consistently load after successful setup.

Actual Behavior

The login behaviour is inconsistent. Sometimes everything works as expected, other times I sucessfully log in (green pop-up appears), but then the Open WebUI does not load and I am stuck with a blank screen.

Image

Steps to Reproduce

  1. Open deployed Open WebUI application
  2. Login with valid credentials

Logs & Screenshots

Image

Additional Information

Issue is potentially related to: https://github.com/open-webui/open-webui/issues/5866

Tested with docker tags: main, v0.6.0

However I have configured the following environment variables, as suggested there:
AIOHTTP_CLIENT_TIMEOUT=60
AIOHTTP_CLIENT_TIMEOUT_MODEL_LIST=60
AIOHTTP_CLIENT_TIMEOUT_OPENAI_MODEL_LIST=60
JWT_EXPIRES_IN=-1

Originally created by @frk-ti8m on GitHub (Apr 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/12396 ### 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.0 ### Ollama Version (if applicable) without ollama ### Operating System Ubuntu 22.04 ### Browser (if applicable) 134.0.6998.166 ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior I expected Open WebUI to consistently load after successful setup. ### Actual Behavior The login behaviour is inconsistent. Sometimes everything works as expected, other times I sucessfully log in (green pop-up appears), but then the Open WebUI does not load and I am stuck with a blank screen. ![Image](https://github.com/user-attachments/assets/d3a8106c-2e1f-4c36-a083-4efb0a9163b2) ### Steps to Reproduce 1. Open deployed Open WebUI application 2. Login with valid credentials ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/d3a8106c-2e1f-4c36-a083-4efb0a9163b2) ### Additional Information Issue is potentially related to: https://github.com/open-webui/open-webui/issues/5866 Tested with docker tags: main, v0.6.0 However I have configured the following environment variables, as suggested there: AIOHTTP_CLIENT_TIMEOUT=60 AIOHTTP_CLIENT_TIMEOUT_MODEL_LIST=60 AIOHTTP_CLIENT_TIMEOUT_OPENAI_MODEL_LIST=60 JWT_EXPIRES_IN=-1
GiteaMirror added the bug label 2026-05-05 17:22:09 -05:00
GiteaMirror commented 2026-05-05 17:22:14 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Apr 3, 2025):

reload &| clean cookies

<!-- gh-comment-id:2775722001 --> @rgaricano commented on GitHub (Apr 3, 2025): reload &| clean cookies
GiteaMirror commented 2026-05-05 17:22:16 -05:00
Author
Owner
Copy Link

@frk-ti8m commented on GitHub (Apr 3, 2025):

It does not always help to reload and clean cookies.
And oddly enough, when I run into this bug repeatedly and then 1. close the browser tab, 2. wait for about 5 Minutes (I don't delete any website data), 3. open the application in a new browser tab, then the login succeeds again.

  • also reproducible for tag v0.5.20
  • seems to occurs when multiple users use the application at the same time
  • I think the bug is related to the user session handling
<!-- gh-comment-id:2775761915 --> @frk-ti8m commented on GitHub (Apr 3, 2025): It does not always help to reload and clean cookies. And oddly enough, when I run into this bug repeatedly and then 1. close the browser tab, 2. wait for about 5 Minutes (I don't delete any website data), 3. open the application in a new browser tab, then the login succeeds again. - also reproducible for tag v0.5.20 - seems to occurs when multiple users use the application at the same time - I think the bug is related to the user session handling
GiteaMirror commented 2026-05-05 17:22:18 -05:00
Author
Owner
Copy Link

@frk-ti8m commented on GitHub (Apr 3, 2025):

Here is a gif of the whole procedure if it helps:

Image

<!-- gh-comment-id:2775790381 --> @frk-ti8m commented on GitHub (Apr 3, 2025): Here is a gif of the whole procedure if it helps: ![Image](https://github.com/user-attachments/assets/fc5fd229-e3ca-44e8-b651-9a6f82a62b17)
GiteaMirror commented 2026-05-05 17:22:19 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 3, 2025):

Most likely related to /models endpoint. I'd suggest you specify the model ids directly from the connections.

<!-- gh-comment-id:2776416000 --> @tjbck commented on GitHub (Apr 3, 2025): Most likely related to `/models` endpoint. I'd suggest you specify the model ids directly from the connections.
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#55249
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?