[GH-ISSUE #199] Make websocket port configurable #100

New issue

Closed

opened 2026-03-03 01:24:54 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:24:54 +03:00

Owner

Originally created by @aminehmida on GitHub (Sep 26, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/199

I want to expose birwarden on a specific interface only. I can't do that because the WebSocket server it is currently hard coded to 0.0.0.0

Similar to #179

Thanks in advance!

Originally created by @aminehmida on GitHub (Sep 26, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/199 I want to expose birwarden on a specific interface only. I can't do that because the WebSocket server it is currently hard [coded to `0.0.0.0`](https://github.com/dani-garcia/bitwarden_rs/blob/948554a20fd46acc7155303985b9517607b246b9/src/api/notifications.rs#L361) Similar to #179 Thanks in advance!

kerem

2026-03-03 01:24:54 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-03 01:24:55 +03:00

Author

Owner

@dani-garcia commented on GitHub (Sep 28, 2018):

This should be fixed now, you can use WEBSOCKET_ADDRESS to change it.

@dani-garcia commented on GitHub (Sep 28, 2018): This should be fixed now, you can use `WEBSOCKET_ADDRESS` to change it.

kerem referenced this issue

2026-03-03 02:20:00 +03:00

[PR #106] [MERGED] Use stable release of v2.0.0 #2609

kerem referenced this issue

2026-03-03 02:20:02 +03:00

[PR #116] [MERGED] Implemented bulk cipher share (share selected) #100 #2615

kerem referenced this issue

2026-03-03 02:20:04 +03:00

[PR #129] [MERGED] Implemented PUT for /two-factor/authenticator and /two-factor/disable #124 #2620