github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-17 01:12:27 -05:00
Code Issues 481 Packages Projects Releases 83 Wiki Activity

Websocket error log cannot be disabled #4845

New Issue
Closed
opened 2026-03-07 20:03:07 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-07 20:03:07 -06:00
Owner
Copy Link

Originally created by @pichouk on GitHub (Jan 24, 2022).

Websocket error log cannot be disabled

When I set the variable LOG_LEVEL = "off" I still have log messages because of websocket malformed requests.

Encountered an error: WebSocket Protocol Error: Unable to parse WebSocket key.                                                                                                                                                                             Enable a logger to see more information.

Deployment environment

I deployed Vaultwarden using Kubernetes, on AWS. I use the container image vaultwarden/server:1.23.1.
I expose Vaultwarden using a AWS Application Load Balancer, which regularly send healtchecks to the container. Those healthchecks does not support Websocket, and I can't disable them. So I have malformed requests on the Websocket port.

I just want to hide the error message generated by the container when receiving a bad request on Websocket port.

Steps to reproduce

Start a Vaultwarden server with LOG_LEVEL="off" and send an HTTP request (using curl) to the websocket port.

Expected behaviour

I think those error logs should not be present when using the LOG_LEVEL="off" configuration.

Actual behaviour

I still have this messages

Encountered an error: WebSocket Protocol Error: Unable to parse WebSocket key.                                                                                                                                                                             Enable a logger to see more information.
Originally created by @pichouk on GitHub (Jan 24, 2022). ### Websocket error log cannot be disabled When I set the variable `LOG_LEVEL = "off"` I still have log messages because of websocket malformed requests. ``` Encountered an error: WebSocket Protocol Error: Unable to parse WebSocket key. Enable a logger to see more information. ``` ### Deployment environment I deployed Vaultwarden using Kubernetes, on AWS. I use the container image `vaultwarden/server:1.23.1`. I expose Vaultwarden using a AWS Application Load Balancer, which regularly send healtchecks to the container. Those healthchecks does not support Websocket, and I can't disable them. So I have malformed requests on the Websocket port. I just want to hide the error message generated by the container when receiving a bad request on Websocket port. ### Steps to reproduce Start a Vaultwarden server with `LOG_LEVEL="off"` and send an HTTP request (using curl) to the websocket port. ### Expected behaviour I think those error logs should not be present when using the `LOG_LEVEL="off"` configuration. ### Actual behaviour I still have this messages ``` Encountered an error: WebSocket Protocol Error: Unable to parse WebSocket key. Enable a logger to see more information. ```
GiteaMirror added the wontfix label 2026-03-07 20:03:07 -06:00
GiteaMirror commented 2026-03-07 20:03:08 -06:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Jan 24, 2022):

This is not something we can fix, since this is build-in into the library used for the websockets.
24511a9d4b/src/handler.rs (L63-L70)

Also, if you see this error, then you probably have configured your reverse proxy incorrect, or, if not using a reverse proxy you need to disable websockets at all via WEBSOCKET_ENABLED=FALSE.

Also see: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-WebSocket-notifications
And https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples

@BlackDex commented on GitHub (Jan 24, 2022): This is not something we can fix, since this is build-in into the library used for the websockets. https://github.com/paritytech/ws-rs/blob/24511a9d4ba5e485f625b9c90d0e4d5b2ec01243/src/handler.rs#L63-L70 Also, if you see this error, then you probably have configured your reverse proxy incorrect, or, if not using a reverse proxy you need to disable websockets at all via `WEBSOCKET_ENABLED=FALSE`. Also see: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-WebSocket-notifications And https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label wontfix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#4845
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?