mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
[GH-ISSUE #8518] blank page after logging #15153
Reference in New Issue
Block a user
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?
Originally created by @Sturmkater on GitHub (Jan 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8518
Bug Report
Important Notes
Installation Method
Docker on Synology NAS, ollama on proxmox
Environment
Open WebUI Version: [e.g., v0.3.11]
? popably latest, gets updated with Ouroboros
Ollama (if applicable): [e.g., v0.2.0, v0.1.32-rc1]
0.5.1 << works well in Terminal
Operating System: [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04]
Docker
Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]
Brave, Safari
Confirmation:
Expected Behavior:
First it got slower und buggier, second question mad it hang. Now after logging there is a blank page. If I compose a new docker open webui container the ui is entirely unreachable.
Actual Behavior:
[Describe what actually happened.]
Description
Bug Summary:
[Provide a brief but clear summary of the bug]
Reproduction Details
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
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!