[GH-ISSUE #155] Bitwarden_rs websockets #136

Closed
opened 2026-02-26 06:30:35 +03:00 by kerem · 1 comment
Owner

Originally created by @PartyDonut on GitHub (May 31, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/155

I have been trying to get bitwarden_rs websockets working. The website itself works with ssl and websockets also worked with traefik.

However i can't get websockets to work using proxy manager I have tried setting the custom locations and adding the following to the advanced properties.

 location /notifications/hub {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_http_version 1.1;
    proxy_pass $forward_scheme://$server:3012;
  }
  
  location /notifications/hub/negotiate {
    proxy_pass $forward_scheme://$server:$port;
  }

Bitwarden returns these errors using either the custom locations and advanced settings

#/notifications/hub/
[2019-05-31 09:06:36][ws::io][INFO] Accepted a new tcp connection from 172.26.0.1:34178.
[2019-05-31 09:06:36][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.

#/notifications/hub/negotiate
[2019-05-31 09:10:46][rocket::rocket][INFO] GET /notifications/hub/negotiate text/html:
[2019-05-31 09:10:46][_][INFO] Matched: GET /<p..> [10] (web_files)
[2019-05-31 09:10:46][_][ERROR] Response was a non-`Responder` `Err`: Os { code: 2, kind: NotFound, message: "No such file or directory" }.
[2019-05-31 09:10:46][_][INFO] Outcome: Failure
[2019-05-31 09:10:46][_][WARN] Responding with 500 Internal Server Error catcher.
[2019-05-31 09:10:46][_][INFO] Response succeeded.

Everything else works perfectly fine, just can't get the websockets to work.

Originally created by @PartyDonut on GitHub (May 31, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/155 I have been trying to get bitwarden_rs websockets working. The website itself works with ssl and websockets also worked with traefik. However i can't get websockets to work using proxy manager I have tried setting the custom locations and adding the following to the advanced properties. ``` location /notifications/hub { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass $forward_scheme://$server:3012; } location /notifications/hub/negotiate { proxy_pass $forward_scheme://$server:$port; } ``` Bitwarden returns these errors using either the custom locations and advanced settings ``` #/notifications/hub/ [2019-05-31 09:06:36][ws::io][INFO] Accepted a new tcp connection from 172.26.0.1:34178. [2019-05-31 09:06:36][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. #/notifications/hub/negotiate [2019-05-31 09:10:46][rocket::rocket][INFO] GET /notifications/hub/negotiate text/html: [2019-05-31 09:10:46][_][INFO] Matched: GET /<p..> [10] (web_files) [2019-05-31 09:10:46][_][ERROR] Response was a non-`Responder` `Err`: Os { code: 2, kind: NotFound, message: "No such file or directory" }. [2019-05-31 09:10:46][_][INFO] Outcome: Failure [2019-05-31 09:10:46][_][WARN] Responding with 500 Internal Server Error catcher. [2019-05-31 09:10:46][_][INFO] Response succeeded. ``` Everything else works perfectly fine, just can't get the websockets to work.
kerem 2026-02-26 06:30:35 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@PartyDonut commented on GitHub (Jun 3, 2019):

Updated to the latest bitwardenrs/server and websockets now seems to work with both configurations.

<!-- gh-comment-id:498212280 --> @PartyDonut commented on GitHub (Jun 3, 2019): Updated to the latest bitwardenrs/server and websockets now seems to work with both configurations.
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/nginx-proxy-manager-NginxProxyManager#136
No description provided.