Disabling websocket in values yaml does not actually disable it #80

New Issue

2026-02-15T19:16:04-05:00

yindo commented

2026-02-15 19:16:04 -05:00

Originally created by @lorelei-rupp-imprivata on GitHub (Apr 4, 2025).

we were trying to set in the values.yaml for version 5.20.0

websocket:
   enabled: false

But this does not actually disable websockets
I needed to actually set this in the

  extraEnvVars:
    # -- Default API key value for Pipelines. Should be updated in a production deployment, or be changed to the required API key if not using Pipelines
    - name: OPENAI_API_KEY
      value: "0p3n-w3bu!"
    - name: ENABLE_WEBSOCKET_SUPPORT
      value: "False"

I would have expected enabled: false to properly disable it, but it does not and there are lots of websocket errors

Originally created by @lorelei-rupp-imprivata on GitHub (Apr 4, 2025). we were trying to set in the values.yaml for version 5.20.0 ``` websocket: enabled: false ``` But this does not actually disable websockets I needed to actually set this in the ``` extraEnvVars: # -- Default API key value for Pipelines. Should be updated in a production deployment, or be changed to the required API key if not using Pipelines - name: OPENAI_API_KEY value: "0p3n-w3bu!" - name: ENABLE_WEBSOCKET_SUPPORT value: "False" ``` I would have expected enabled: false to properly disable it, but it does not and there are lots of websocket errors

yindo added the bug label 2026-02-15 19:16:04 -05:00

yindo commented

2026-02-15 19:16:04 -05:00

@jyje commented on GitHub (Apr 4, 2025):

Hello @lorelei-rupp-imprivata, your point makes sense. Thanks for reporting this. According to this documentation, the default value of ENABLE_WEBSOCKET_SUPPORT is False.

I’ll check if the WebSocket is not working as expected. You can submit a PR for this, or please wait while I investigate your point.

Have a good day!

@jyje commented on GitHub (Apr 4, 2025): Hello @lorelei-rupp-imprivata, your point makes sense. Thanks for reporting this. According to [this documentation](https://docs.openwebui.com/getting-started/env-configuration#enable_websocket_support), the default value of ENABLE_WEBSOCKET_SUPPORT is False. I’ll check if the WebSocket is not working as expected. You can submit a PR for this, or please wait while I investigate your point. Have a good day!

yindo commented

2026-02-15 19:16:04 -05:00

@lorelei-rupp-imprivata commented on GitHub (Apr 4, 2025):

Hello @lorelei-rupp-imprivata, your point makes sense. Thanks for reporting this. According to this documentation, the default value of ENABLE_WEBSOCKET_SUPPORT is False.

I’ll check if the WebSocket is not working as expected. You can submit a PR for this, or please wait while I investigate your point.

Have a good day!

Thanks -- yeah that default def does not get set on the container and is def not set for some reason. When this is specifically put in, then all the errors go away and things work

@lorelei-rupp-imprivata commented on GitHub (Apr 4, 2025): > Hello [@lorelei-rupp-imprivata](https://github.com/lorelei-rupp-imprivata), your point makes sense. Thanks for reporting this. According to [this documentation](https://docs.openwebui.com/getting-started/env-configuration#enable_websocket_support), the default value of ENABLE_WEBSOCKET_SUPPORT is False. > > I’ll check if the WebSocket is not working as expected. You can submit a PR for this, or please wait while I investigate your point. > > Have a good day! Thanks -- yeah that default def does not get set on the container and is def not set for some reason. When this is specifically put in, then all the errors go away and things work

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: open-webui/helm-charts#80