[GH-ISSUE #119] Grey screen when trying to connect to remote instance. #69

Closed
opened 2026-10-18 14:05:38 +00:00 by bsakaguchi · 8 comments
Owner

Originally created by @bmc0923 on GitHub (Apr 21, 2026).
Original GitHub issue: https://github.com/open-webui/desktop/issues/119

Just getting grey screen with no feedback on what is going wrong when trying to connect to remote instance.

I have tried connecting to deployed production openwebui older version, and also fully up to date openwebui localhost, both don't work. Am I doing something wrong, or is this a bug.

Originally created by @bmc0923 on GitHub (Apr 21, 2026). Original GitHub issue: https://github.com/open-webui/desktop/issues/119 Just getting grey screen with no feedback on what is going wrong when trying to connect to remote instance. I have tried connecting to deployed production openwebui older version, and also fully up to date openwebui localhost, both don't work. Am I doing something wrong, or is this a bug.
Author
Owner

@Analog4Lyfe commented on GitHub (Apr 22, 2026):

Same here on linux mint latest.

Server is running on docker in unraid.

But if i click on the hambuger menu and click open browser, my browser connects correctly.

<!-- gh-comment-id:4292841174 --> @Analog4Lyfe commented on GitHub (Apr 22, 2026): Same here on linux mint latest. Server is running on docker in unraid. But if i click on the hambuger menu and click open browser, my browser connects correctly.
Author
Owner

@tolukosi commented on GitHub (Apr 22, 2026):

Same issue. This happens without having to install the local version but install connecting to the remote server.

Ubuntu

<!-- gh-comment-id:4292943471 --> @tolukosi commented on GitHub (Apr 22, 2026): Same issue. This happens without having to install the local version but install connecting to the remote server. Ubuntu
Author
Owner

@Battle-Pheasant commented on GitHub (Apr 22, 2026):

Same issue here.

Running Open WebUI in docker container with caddy certs applied and it runs just fine via browser from anywhere in house and on IOS devices. I can not open the server locally with this new desktop app at all <-- Desktop app says "Could not reach this server".

When I try connecting the Desktop app to the local instance of the docker container insecurely, the desktop app says it sees it but brings nothing up on the next screen.

<!-- gh-comment-id:4296283725 --> @Battle-Pheasant commented on GitHub (Apr 22, 2026): Same issue here. Running Open WebUI in docker container with caddy certs applied and it runs just fine via browser from anywhere in house and on IOS devices. I can not open the server locally with this new desktop app at all <-- Desktop app says "Could not reach this server". When I try connecting the Desktop app to the local instance of the docker container insecurely, the desktop app says it sees it but brings nothing up on the next screen.
Author
Owner

@savantskie commented on GitHub (Apr 23, 2026):

same issue here, try to connect to my bare metal openwebui instance, desktop app is giving just a blank screen.
Linux, Ubuntu 22.04, destop app installee via .deb, serverinstance runing bare metal by systemctl

<!-- gh-comment-id:4301771709 --> @savantskie commented on GitHub (Apr 23, 2026): same issue here, try to connect to my bare metal openwebui instance, desktop app is giving just a blank screen. Linux, Ubuntu 22.04, destop app installee via .deb, serverinstance runing bare metal by systemctl
Author
Owner

@AreYouLoco commented on GitHub (Apr 24, 2026):

Same here. Desktop app from .deb. Subscribing to issue. open-webui from docker running on localhost:8080.

Tried to set-up haproxy service with snake-oil cert to use https:// but same result

<!-- gh-comment-id:4315005453 --> @AreYouLoco commented on GitHub (Apr 24, 2026): Same here. Desktop app from .deb. Subscribing to issue. open-webui from docker running on localhost:8080. Tried to set-up haproxy service with snake-oil cert to use https:// but same result
Author
Owner

@AreYouLoco commented on GitHub (Apr 28, 2026):

I just updated. I do not use Wayland nor Intel/NVIDIA GPU and cannot confirm it's fixed. Same Gray screen

<!-- gh-comment-id:4333054180 --> @AreYouLoco commented on GitHub (Apr 28, 2026): I just updated. I do not use Wayland nor Intel/NVIDIA GPU and cannot confirm it's fixed. Same Gray screen
Author
Owner

@CorentinWicht commented on GitHub (Apr 29, 2026):

Problem solved on my side (Ubuntu 24.04, flatpak package), thanks !

<!-- gh-comment-id:4340886387 --> @CorentinWicht commented on GitHub (Apr 29, 2026): Problem solved on my side (Ubuntu 24.04, flatpak package), thanks !
Author
Owner

@AreYouLoco commented on GitHub (Apr 29, 2026):

*-amd64.deb on v0.blabla.15 still broken and gray screen. Switched to flatpak version and flatpak works fine. Even more convenient for updates

<!-- gh-comment-id:4344918085 --> @AreYouLoco commented on GitHub (Apr 29, 2026): *-amd64.deb on v0.blabla.15 still broken and gray screen. Switched to flatpak version and flatpak works fine. Even more convenient for updates
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/desktop#69
No description provided.