mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
[GH-ISSUE #2337] bug: hanging connection causing blank screen #28373
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 @Zambito1 on GitHub (May 17, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/2337
Bug Report
Description
Bug Summary:
If the Open WebUI backend hangs indefinitely, the UI will show a blank screen with just the keybinding help button in the bottom right.
Steps to Reproduce:
I noticed this because I run Open WebUI on my desktop, and Ollama on another machine. If I connected to a VPN on my desktop, LAN connections from my desktop would hang indefinitely. When I tried to boot up Open WebUI, I would just see the screen above.
The easiest way to reproduce this is to run
nc -lp 11434and try to use that as the Ollama server. You will see something like:As the Open WebUI backend tries to connect to Ollama, but
ncwill never respond to the request, nor will it close the connection. You will see the above screen when you open the web interface.I was able to work around my VPN issue by splitting my connection to only route traffic that I want to access over the VPN with the virtual interface.
Expected Behavior:
You can see the web interface, and ideally there will be some sort of timeout to show a connection error.
Actual Behavior:
You are hit with a wall of nothing.
Environment
Open WebUI Version: v0.1.124
Ollama (if applicable): NA
Operating System: NA
Browser (if applicable): NA
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
NA, the connection issue is on the backend. There is nothing that fails in the UI logs.
Docker Container Logs:
This is what happens when you load the index page:
If you kill
nc, the UI will actually show up:Screenshots (if applicable):
See above.
Installation Method
Docker, but probably does not matter.
@tjbck commented on GitHub (May 17, 2024):
PR welcome!
@tjbck commented on GitHub (May 17, 2024):
Updated some code on our dev branch, let us know if that did anything for you.
@Zambito1 commented on GitHub (May 21, 2024):
Hey @tjbck, I got around to testing the dev branch today. The problem still seems to happen. I should have said to use
nc -lk 11434orncat -lk 11434, that will continue to listen to connections after the first one. If you do not use-k, refreshing the page will kill netcat, and the UI will appear.@Hiradpi commented on GitHub (May 22, 2024):
having the same exact issue here but Im not using docker
and I also have these vars set
export OLLAMA_MODELS=/run/media/hirad/HSSD/AII ran ollama with
ollama servecommand (no docker again)I have llama3 and codellama
( ollama is running on gpu mode )
and the os is arch linux with lts kernel
@justinh-rahb commented on GitHub (May 22, 2024):
@Hiradpi I'm going to guess this is on Windows. You'll need to set
ENABLE_LITELLM=Falseas an environment variable since it's not supported running directly on Windows with the method we're using, and will soon be deprecated and removed from the project anyway.@Hiradpi commented on GitHub (May 22, 2024):
this worked thanks a lot I added ENABLE_LITELLM=False to the .env file and it solved the problem thanks a lot <3
@Zambito1 commented on GitHub (May 23, 2024):
For clarity this is unrelated to the issue originally described. I just tested it again on the latest dev branch, and the UI is still blank when the Ollama service is reachable but unresponsive (such as when using netcat instead of ollama to listen to the port).
@tjbck commented on GitHub (May 26, 2024):
Just pushed a massive refac/update to our dev branch, please try again and let us know how it went! Much thanks!
@Zambito1 commented on GitHub (May 26, 2024):
Now the UI will be blank for 5 seconds, and then it will appear after the backend connection to Ollama times out.
The UI appears after the models connection finishes. It is definitely much better than indefinitely showing a blank screen (enough that I would consider the original issue resolved), but I do think the UI should be able to show before that request completes. Feel free to close this issue, or use it to continue tracking the UI not appearing until this request finishes at your discretion.
@tjbck commented on GitHub (May 26, 2024):
@Zambito1 could you try disabling Ollama connection from settings > connections?
@Zambito1 commented on GitHub (May 26, 2024):
Hm, that menu actually has some weird behavior when I try to do that. When I navigate there while listening with netcat instead of Ollama, the UI will show Ollama and Open AI as disabled.
When the connection attempt to Ollama times out, the UI will change automatically, switching both to be enabled.
I did not interact with anything manually between the above screenshots.
If I have nothing listening on the port that Open WebUI expects Ollama to be on (neither netcat nor Ollama), these are both immediately populated and on when I navigate to the menu.
Note that I did not manually enter the URL between the above two screenshots. I just closed netcat, and then reopened the settings window.
@tjbck commented on GitHub (May 26, 2024):
Just added a fix to include a loading screen, let me know if you encounter the same set of issues!
@Zambito1 commented on GitHub (May 26, 2024):
On commit
b7fc37d9the settings will load for 12 seconds before timing out (2 sequential 6 second time outs).After the connection times out, the settings will show with the URLs populated and the connections enabled.
If I disable the Ollama connection now, I am able to refresh the page without waiting on a blank screen like my earlier tests today.
@sebdanielsson commented on GitHub (Jun 4, 2024):
Loading times are greatly improved since I followed this issue but I'm still getting 6 seconds of loading time. Is this intended?
@eagerto-learn commented on GitHub (Feb 4, 2025):
I am still experiencing this issue. I use multiple ollama instances and when any one of the instances are unreachable, the whole openwebui is unusable.
I am getting prompted to login but after successfully logging in I get the same blank screen.
@GeorgiaM-honestly commented on GitHub (Feb 7, 2025):
I am also experiencing this issue. This is preventing me from using a new Open-WebUI install.
New install. Setting the environment variable OLLAMA_API_TIMEOUT to 0.1 didn't change anything. ( docker run [...] -e OLLAMA_API_TIMEOUT=0.1
@flennic commented on GitHub (Feb 10, 2025):
Encountering the same issue. ollama hosted on another machine. When the machine is not reachable, I get a blank screen. It starts working again as soon the the machine hosting ollama is reachable via the network again. It is the only available ollama model instance (so if this one is down, there is none available at all).
@blyedev commented on GitHub (Feb 16, 2025):
Same issue here, except my ollama instance is behind a ssh tunnel
@frugbug commented on GitHub (Feb 19, 2025):
I'm also experiencing this issue, but it only occurs for me when a remote instance is down. With an inaccessible instance on the same host as open-webui, the UI does still load fine
@intelligo1466 commented on GitHub (Feb 22, 2025):
Same here. Fresh install on Windows 11 of Open WebUI container with Podman. Installation was without error, but when I connect to localhost:3000 the Open WebUI logo flashes for a second, disappears, then I'm left with a black screen. No response when left- and right-Clicking around the screen.
@mcpeixoto commented on GitHub (Mar 14, 2025):
Same here. Did a fresh installed -> Configured OLLAMA but after some time (??) the page broke and after login I only get a blank page.
Using docker latest version
@intelligo1466 commented on GitHub (Mar 22, 2025):
Follow-up: By exercising some patience, I discovered that this apparent disappearance of Open WebUI is only because of the unexpectedly long lag between starting the Open WebUI container and the appearance of Open WebUI on localhost, especially if it's your first time running the container. After a minute, Open WebUI appears and functions as expected.