[GH-ISSUE #179] Make WebSocket notification server port configurable #86

Closed
opened 2026-03-03 01:24:43 +03:00 by kerem · 2 comments
Owner

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

The WebSocket notification server does not work on a system where port 3012 is already in use.
Making the WebSocket server port configurable similar to the ROCKET_PORT option would help in such cases.

Originally created by @mengelbrecht on GitHub (Sep 13, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/179 The WebSocket notification server does not work on a system where port 3012 is already in use. Making the WebSocket server port configurable similar to the `ROCKET_PORT` option would help in such cases.
kerem 2026-03-03 01:24:43 +03:00
Author
Owner

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

This should be solved now, with commit 948554a

<!-- gh-comment-id:421116126 --> @dani-garcia commented on GitHub (Sep 13, 2018): This should be solved now, with commit 948554a
Author
Owner

@mengelbrecht commented on GitHub (Sep 13, 2018):

Thanks!

<!-- gh-comment-id:421133214 --> @mengelbrecht commented on GitHub (Sep 13, 2018): Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#86
No description provided.