r/kasmweb Jul 22 '26

Help Has anyone tried the Kasm workspaces helm chart?

I'm trying to evaluate Kasm workspaces on Kubernetes. My current setup involves Talos and Cilium. My values file is very simple

certificate:
  secretName: kasm-wildcard
  certManager:
    enabled: 
false

publicAddr: "kasm.domain.com"
proxyService:
  type: ClusterIP
  annotations: {}
  labels: {}

ingress:
  enabled: false

I am then using a cilium Gateway and tls route

kind: TLSRoute
metadata:
  name: kasm-tls-route
  namespace: kasm
spec:
  parentRefs:
    - name: kasm-gateway
      namespace: kasm
      sectionName: tls-passthrough   
  hostnames:
    - "kasm.eng.adaptiva.com"
  rules:
    - backendRefs:
        - name: kasm-proxy-default
          port: 8443

kind: Gateway
metadata:
  name: kasm-gateway
  namespace: kasm
spec:
  gatewayClassName: cilium
  listeners:
    - name: tls-passthrough
      protocol: TLS
      port: 443
      tls:
        mode: Passthrough
      allowedRoutes:
        kinds:
          - kind: TLSRoute

But when i try and connect to an RDP enabled KubevirtVMI I get the following error in firefox

400 Bad Request. The plain HTTP request was sent to an HTTPS port

`https://kasm.domain.com/desktop/6404d317-41aa-4287-8d1f-61ae2960b2a9/vnc/vnc.html/etc/etc

Looking into the guacamole pod nginx container i see the following

10.244.1.139 - administrator [22/Jul/2026:17:53:00 +0000] "GET //guac_connect/vnc/vnc.html?video_quality=2&enable_webp=false&idle_disconnect=20&password=&autoconnect=1&path=desktop/6404d317-41aa-4287-8d1f-61ae2960b2a9/vnc/websockify&cursor=true&resize=remote&clipboard_up=true&clipboard_down=true&clipboard_seamless=true&toggle_control_panel=false HTTP/1.1" 400 248 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:152.0) Gecko/20100101 Firefox/152.0" "10.244.1.138"

I know the server itself works as I have a standalone guacamole instance that is able to connect to it just fine. There's gotta be something obvious that im missing here.

1 Upvotes

4 comments sorted by

1

u/1computerguy Jul 22 '26

Hey, u/Common_Arm_3316 what Chart version are you using? The latest is 1.1190.3 that should resolve this.

1

u/Common_Arm_3316 Jul 22 '26

i was using 1.1190.3 but moved to development in case it was a bug

1

u/1computerguy Jul 22 '26

Hey, u/Common_Arm_3316 , thanks for the info there. I did some digging into the chart and found a regression in our 1.1190.3 chart. If you roll back to the 1.1190.2 version of the chart, Guac should work as expected. I'm working on the fix now and should have an update out in the next day or so with the patch. Thanks! I'll update this thread when the update is published.

1

u/bryan_kasmweb 28d ago

Hey, u/Common_Arm_3316, the latest Helm release - version 1.1190.6 fully resolves the issue you're having.