Make WebSocket notification server port configurable #85

Closed
opened 2026-02-04 16:50:31 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @mengelbrecht on GitHub (Sep 13, 2018).

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). 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.
OVERLORD added the enhancement label 2026-02-04 16:50:31 +03:00
Author
Owner

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

This should be solved now, with commit 948554a

@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!

@mengelbrecht commented on GitHub (Sep 13, 2018): Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#85