# \[SOLVED\] Question about WEBSOCKET\_ENABLED and websocket now on http

**URL:** <https://vaultwarden.discourse.group/t/solved-question-about-websocket-enabled-and-websocket-now-on-http/3299>\
**Category:** Uncategorized\
**Created:** [January 28, 2024, 3:28pm UTC](https://vaultwarden.discourse.group/t/solved-question-about-websocket-enabled-and-websocket-now-on-http/3299 "2024-01-28T15:28:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![blighted\_antsy](https://avatars.discourse-cdn.com/v4/letter/b/ee7513/32.png) [@blighted\_antsy](https://vaultwarden.discourse.group/u/blighted_antsy)\
**Post date:** [January 28, 2024, 3:28pm UTC](https://vaultwarden.discourse.group/t/solved-question-about-websocket-enabled-and-websocket-now-on-http/3299/1 "2024-01-28T15:28:38Z")

</div>

I searched but since it is a new thing, I am not sure it has been asked yet.

I am trying to get the new websocket implementation working. I know it’s supposed to now be in embedded and listening on the default port (80.) My question is then- should I set WEBSOCKET\_ENABLED to false then?

I still want websocket but with the above set to true it seems to say in the logs it’s listening on 3012. Should I assume if I set it to false (or just don’t set it at all) that the websocket will still remain active but just on http?

Edit- solved it. I was only really looking at the latest release. The note here - [Release 1.29.0 · dani-garcia/vaultwarden · GitHub](https://github.com/dani-garcia/vaultwarden/releases/tag/1.29.0) - explains the env var is no longer needed.

Thanks for such a great product!