open-webui/helm-charts
1
0
Fork 0
mirror of https://github.com/open-webui/helm-charts.git synced 2026-07-22 18:05:24 -04:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

After adding ingress, chat message doesn't work #110

New Issue
Closed
opened 2026-02-15 19:16:22 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 19:16:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @wklee610 on GitHub (Dec 12, 2025).

Before when I used with localhost, it worked but, after adding ingress, chat messages are not showing up in OpenWebUI.

  # -- Enable Ingress controller for Open WebUI
  # @section -- Ingress configuration
  enabled: true
  # -- Ingress class to use, e.g., for GKE Ingress use "gce", for NGINX Ingress use "nginx". If using an Ingress class other than the default, ensure your cluster has the corresponding Ingress controller installed and configured.
  # @section -- Ingress configuration
  class: "nginx"
  # -- Use appropriate annotations for your Ingress controller, e.g., for NGINX:
  # @section -- Ingress configuration
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
  #   # Example for GKE Ingress
    # kubernetes.io/ingress.class: "gce"
  #   kubernetes.io/ingress.global-static-ip-name: "open-webui-external-ip"   #  you need to create this address in GCP console
  #   # Force HTTP to redirect to HTTPS
  #   nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
  #   nginx.ingress.kubernetes.io/ssl-redirect: "true"
  #   nginx.ingress.kubernetes.io/permanent-redirect: "https://chat.example.com"
  #   networking.gke.io/managed-certificates: "mydomain-chat-cert"
  #   # nginx.ingress.kubernetes.io/rewrite-target: /
  # -- Host for the Ingress record
  # @section -- Ingress configuration
  host: "test.com" # update to your real domain
  # -- Additional hosts for the Ingress record
  # @section -- Ingress configuration
  additionalHosts: []
  # -- TLS configuration for the Ingress resource
  # @section -- Ingress configuration
  tls: false
  # -- TLS secret name for the Ingress record
  # @section -- Ingress configuration
  existingSecret: ""
  # -- Additional custom labels to add to the Ingress metadata
  # @section -- Ingress configuration
  extraLabels: {}
  # extraLabels:
  #   app.kubernetes.io/environment: "staging"

In console, it keep saying WebSocket connection to 'ws://test.com/ws/socket.io/?EIO=4&transport=websocket' failed:

Originally created by @wklee610 on GitHub (Dec 12, 2025). Before when I used with localhost, it worked but, after adding ingress, chat messages are not showing up in OpenWebUI. ```ingress: # -- Enable Ingress controller for Open WebUI # @section -- Ingress configuration enabled: true # -- Ingress class to use, e.g., for GKE Ingress use "gce", for NGINX Ingress use "nginx". If using an Ingress class other than the default, ensure your cluster has the corresponding Ingress controller installed and configured. # @section -- Ingress configuration class: "nginx" # -- Use appropriate annotations for your Ingress controller, e.g., for NGINX: # @section -- Ingress configuration annotations: nginx.ingress.kubernetes.io/rewrite-target: / # # Example for GKE Ingress # kubernetes.io/ingress.class: "gce" # kubernetes.io/ingress.global-static-ip-name: "open-webui-external-ip" # you need to create this address in GCP console # # Force HTTP to redirect to HTTPS # nginx.ingress.kubernetes.io/force-ssl-redirect: "true" # nginx.ingress.kubernetes.io/ssl-redirect: "true" # nginx.ingress.kubernetes.io/permanent-redirect: "https://chat.example.com" # networking.gke.io/managed-certificates: "mydomain-chat-cert" # # nginx.ingress.kubernetes.io/rewrite-target: / # -- Host for the Ingress record # @section -- Ingress configuration host: "test.com" # update to your real domain # -- Additional hosts for the Ingress record # @section -- Ingress configuration additionalHosts: [] # -- TLS configuration for the Ingress resource # @section -- Ingress configuration tls: false # -- TLS secret name for the Ingress record # @section -- Ingress configuration existingSecret: "" # -- Additional custom labels to add to the Ingress metadata # @section -- Ingress configuration extraLabels: {} # extraLabels: # app.kubernetes.io/environment: "staging" ``` In console, it keep saying `WebSocket connection to 'ws://test.com/ws/socket.io/?EIO=4&transport=websocket' failed:`
yindo closed this issue 2026-02-15 19:16:22 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
awaiting-user-feedback
awaiting-user-feedback
bug
bug
documentation
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: open-webui/helm-charts#110
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?