[GH-ISSUE #324] After adding ingress, chat message doesn't work #110

Closed
opened 2026-10-18 21:06:09 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @wklee610 on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/open-webui/helm-charts/issues/324

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). Original GitHub issue: https://github.com/open-webui/helm-charts/issues/324 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:`
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/helm-charts#110
No description provided.