github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22581] issue: WebSocket uses ws:// instead of wss:// when Open WebUI is served over HTTPS (Open Terminal Container) #35286

New Issue
Closed
opened 2026-04-25 09:31:17 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 09:31:17 -05:00
Owner
Copy Link

Originally created by @ieQ-strecker on GitHub (Mar 11, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22581

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

No response

Operating System

Debian 12

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

Expected behavior
When Open WebUI is accessed over HTTPS, the terminal should use a secure WebSocket connection (wss://) automatically.

Actual Behavior

Observed behavior

  • Access via IP address (HTTP) works without any issues.
  • Access via HTTPS domain fails in the interactive terminal with the following error:

Steps to Reproduce

We’re using the Open Terminal Container and it connects without issues when using direct connect (not admin connect) to Open WebUI.

Our Open WebUI instance is available via HTTPS, but the terminal WebSocket is attempting to connect via ws:// instead of wss://. This causes the connection to fail when accessing Open WebUI through our HTTPS domain.

Logs & Screenshots

[Error: SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.]

Additional Information

No response

Originally created by @ieQ-strecker on GitHub (Mar 11, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22581 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 ### 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 **Expected behavior** When Open WebUI is accessed over HTTPS, the terminal should use a secure WebSocket connection (`wss://`) automatically. ### Actual Behavior **Observed behavior** - Access via **IP address (HTTP)** works without any issues. - Access via **HTTPS domain** fails in the interactive terminal with the following error: ### Steps to Reproduce We’re using the Open Terminal Container and it connects without issues when using *direct connect* (not *admin connect*) to Open WebUI. Our Open WebUI instance is available via **HTTPS**, but the terminal WebSocket is attempting to connect via **`ws://`** instead of **`wss://`**. This causes the connection to fail when accessing Open WebUI through our HTTPS domain. ### Logs & Screenshots ```text [Error: SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.] ``` ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-25 09:31:17 -05:00
GiteaMirror commented 2026-04-25 09:31:19 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 11, 2026):

https://github.com/open-webui/open-terminal/issues/42

<!-- gh-comment-id:4041607464 --> @tjbck commented on GitHub (Mar 11, 2026): https://github.com/open-webui/open-terminal/issues/42
GiteaMirror commented 2026-04-25 09:31:20 -05:00
Author
Owner
Copy Link

@ieQ-strecker commented on GitHub (Mar 12, 2026):

@tjbck NIK-TIGER-BILL attempted to address this with the pull request he posted here, but it was closed without being merged. Could you explain why? From my perspective, that pull request seems to contain the exact fix for my issue.

<!-- gh-comment-id:4044505787 --> @ieQ-strecker commented on GitHub (Mar 12, 2026): @tjbck NIK-TIGER-BILL attempted to address this with the pull request he posted here, but it was closed without being merged. Could you explain why? From my perspective, that pull request seems to contain the exact fix for my issue.
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#35286
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?