starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #929] [ISSUE] Websockets Not Working #660

New issue
Closed
opened 2026-03-03 02:01:52 +03:00 by kerem · 9 comments
kerem commented 2026-03-03 02:01:52 +03:00
Owner
Copy link

Originally created by @mokshmridul on GitHub (Mar 26, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/929

Hi,

Websockets not working / syncing between Chrome Client and Web Page

I had websockets working previously, but I am not getting this error:

WebSocket Protocol Error: Unable to parse WebSocket key.

The error appears when accessing both the internal IP of 192.168.0.11:3012 and the external server through the internet https://vault.example.in/notifications/hub

My Docker Compose is as follows:

    container_name: bitwarden
    image: bitwardenrs/server
    restart: unless-stopped
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "/opt/Bitwarden:/data"
    environment:
      LOG_FILE: /data/bitwarden.log
      WEBSOCKET_ENABLED: "true"
      INVITATIONS_ALLOWED: "false"
      SIGNUPS_ALLOWED: "false"
      SHOW_PASSWORD_HINT: "false"
      DOMAIN: https://vault.example.in
      ADMIN_TOKEN: xxxxx
    ports:
      - 8008:80
      - 3012:3012

My NGINX Reverse proxy is as follows:

#Add entry in Cloudflare DNS ("CNAME vault example.in") to enable
server {
  #BlockedAgent
  if ($blockedagent) {
        return 403;
  }
  
  #Bad Bots Filtering
  if ($limit_bots = 1) {
            return 403;
  }
  
  #listen [::]:443 ssl http2;
  listen 443 ssl http2;
  server_name vault.example.in;
  include /config/nginx/conf.d/*.conf;
  add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
  
    #client_max_body_size 128M;
      
    #SSL Configuration
    include /config/nginx/ssl.conf;

    location / {
    proxy_pass http://192.168.0.11:8008;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    }
  
    location /notifications/hub {
    proxy_pass http://192.168.0.11:3012;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    }
  
    location /notifications/hub/negotiate {
    proxy_pass http://192.168.0.11:8008;
    }

    location /admin {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    proxy_pass http://192.168.0.11:8008;
  } 
}

Your environment

  • Bitwarden_rs version: Version 1.14.1
  • Install method: Docker (Docker Compose)
  • Clients used: Web Page https://vault.example.in and Chrome Addon Client
  • Reverse proxy and version: Nginx 1.16.1

Expected behaviour

Websocket Sync to happen instantly upon changes in either client

Actual behaviour

Websocket Sync is not happening upon changes in either client

Relevant logs

[2020-03-26 17:21:14][ws::handler][ERROR] WS Error <Io(Kind(InvalidData))>: Missing id or access token
[2020-03-26 17:21:19][ws][INFO] Listening for new connections on 0.0.0.0:3012.
[2020-03-26 17:21:19][start][INFO] Rocket has launched from http://0.0.0.0:80
[2020-03-26 17:21:22][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39972.
[2020-03-26 17:21:22][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:23][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39978.
[2020-03-26 17:21:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:23][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39982.
[2020-03-26 17:21:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:24][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39986.
[2020-03-26 17:21:24][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:24][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39990.
[2020-03-26 17:21:24][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:25][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39994.
[2020-03-26 17:21:25][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:31][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:40040.
[2020-03-26 17:21:31][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:31][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:40044.
[2020-03-26 17:21:31][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:21:31][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:40048.
[2020-03-26 17:21:31][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53163.
[2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53164.
[2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53165.
[2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53166.
[2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:05][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53167.
[2020-03-26 17:22:05][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:05][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53168.
[2020-03-26 17:22:05][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:41][ws::io][INFO] Accepted a new tcp connection from 192.168.0.22:42262.
[2020-03-26 17:22:41][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
[2020-03-26 17:22:41][ws::io][INFO] Accepted a new tcp connection from 192.168.0.22:42264.
[2020-03-26 17:22:41][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.
Originally created by @mokshmridul on GitHub (Mar 26, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/929 Hi, ### Websockets not working / syncing between Chrome Client and Web Page I had websockets working previously, but I am not getting this error: ```WebSocket Protocol Error: Unable to parse WebSocket key.``` The error appears when accessing both the internal IP of ``192.168.0.11:3012`` and the external server through the internet ``https://vault.example.in/notifications/hub`` My Docker Compose is as follows: ```` bitwarden: container_name: bitwarden image: bitwardenrs/server restart: unless-stopped volumes: - "/etc/localtime:/etc/localtime:ro" - "/opt/Bitwarden:/data" environment: LOG_FILE: /data/bitwarden.log WEBSOCKET_ENABLED: "true" INVITATIONS_ALLOWED: "false" SIGNUPS_ALLOWED: "false" SHOW_PASSWORD_HINT: "false" DOMAIN: https://vault.example.in ADMIN_TOKEN: xxxxx ports: - 8008:80 - 3012:3012 ```` My NGINX Reverse proxy is as follows: ````#Bitwarden Block #Add entry in Cloudflare DNS ("CNAME vault example.in") to enable server { #BlockedAgent if ($blockedagent) { return 403; } #Bad Bots Filtering if ($limit_bots = 1) { return 403; } #listen [::]:443 ssl http2; listen 443 ssl http2; server_name vault.example.in; include /config/nginx/conf.d/*.conf; add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; #client_max_body_size 128M; #SSL Configuration include /config/nginx/ssl.conf; location / { proxy_pass http://192.168.0.11:8008; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://192.168.0.11:3012; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://192.168.0.11:8008; } location /admin { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_pass http://192.168.0.11:8008; } } ```` ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: Version 1.14.1 * Install method: Docker (Docker Compose) * Clients used: Web Page ``https://vault.example.in`` and Chrome Addon Client * Reverse proxy and version: Nginx 1.16.1 ### Expected behaviour Websocket Sync to happen instantly upon changes in either client ### Actual behaviour Websocket Sync is not happening upon changes in either client ### Relevant logs ````[2020-03-26 17:21:14][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39958. [2020-03-26 17:21:14][ws::handler][ERROR] WS Error <Io(Kind(InvalidData))>: Missing id or access token [2020-03-26 17:21:19][ws][INFO] Listening for new connections on 0.0.0.0:3012. [2020-03-26 17:21:19][start][INFO] Rocket has launched from http://0.0.0.0:80 [2020-03-26 17:21:22][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39972. [2020-03-26 17:21:22][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:23][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39978. [2020-03-26 17:21:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:23][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39982. [2020-03-26 17:21:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:24][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39986. [2020-03-26 17:21:24][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:24][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39990. [2020-03-26 17:21:24][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:25][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:39994. [2020-03-26 17:21:25][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:31][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:40040. [2020-03-26 17:21:31][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:31][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:40044. [2020-03-26 17:21:31][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:21:31][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:40048. [2020-03-26 17:21:31][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53163. [2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53164. [2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53165. [2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:04][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53166. [2020-03-26 17:22:04][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:05][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53167. [2020-03-26 17:22:05][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:05][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:53168. [2020-03-26 17:22:05][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:41][ws::io][INFO] Accepted a new tcp connection from 192.168.0.22:42262. [2020-03-26 17:22:41][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-26 17:22:41][ws::io][INFO] Accepted a new tcp connection from 192.168.0.22:42264. [2020-03-26 17:22:41][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. ````
kerem closed this issue 2026-03-03 02:01:52 +03:00
kerem commented 2026-03-03 02:01:53 +03:00
Author
Owner
Copy link

@jjlin commented on GitHub (Mar 27, 2020):

I sent a PR for the Missing id or access token issue, which I'm seeing as well. I don't get the Unable to parse WebSocket key errors, though. Maybe this is caused by the first issue in your setup, we'll see.

<!-- gh-comment-id:604783179 --> @jjlin commented on GitHub (Mar 27, 2020): I sent a PR for the `Missing id or access token` issue, which I'm seeing as well. I don't get the `Unable to parse WebSocket key` errors, though. Maybe this is caused by the first issue in your setup, we'll see.
kerem commented 2026-03-03 02:01:53 +03:00
Author
Owner
Copy link

@mokshmridul commented on GitHub (Mar 27, 2020):

Maybe this is caused by the first issue in your setup, we'll see.

Hi,
What "first issue" are you referring to in my setup? Do i have something setup incorrectly?

<!-- gh-comment-id:604804953 --> @mokshmridul commented on GitHub (Mar 27, 2020): > Maybe this is caused by the first issue in your setup, we'll see. Hi, What "first issue" are you referring to in my setup? Do i have something setup incorrectly?
kerem commented 2026-03-03 02:01:54 +03:00
Author
Owner
Copy link

@jjlin commented on GitHub (Mar 27, 2020):

Maybe this is caused by the first issue in your setup, we'll see.

Hi,
What "first issue" are you referring to in my setup? Do i have something setup incorrectly?

No, I just meant maybe the Missing id or access token issue is triggering the Unable to parse WebSocket key message on your setup for some reason. I don't see the latter message on my setup.

<!-- gh-comment-id:604821911 --> @jjlin commented on GitHub (Mar 27, 2020): > > Maybe this is caused by the first issue in your setup, we'll see. > > Hi, > What "first issue" are you referring to in my setup? Do i have something setup incorrectly? No, I just meant maybe the `Missing id or access token` issue is triggering the `Unable to parse WebSocket key` message on your setup for some reason. I don't see the latter message on my setup.
kerem commented 2026-03-03 02:01:54 +03:00
Author
Owner
Copy link

@mokshmridul commented on GitHub (Mar 27, 2020):

Okay, thanks for the input.

<!-- gh-comment-id:604823706 --> @mokshmridul commented on GitHub (Mar 27, 2020): Okay, thanks for the input.
kerem commented 2026-03-03 02:01:54 +03:00
Author
Owner
Copy link

@mokshmridul commented on GitHub (Mar 27, 2020):

Im sorry to ask, but i understand that the commit was merged into the latest build (digest 0035b5d8b0a3), and i have updated to this version. however i am still getting the error.



|                       Starting Bitwarden_RS                        |


|                      Version 1.14.1-ec608390                       |


|--------------------------------------------------------------------|


| This is an *unofficial* Bitwarden implementation, DO NOT use the   |


| official channels to report bugs/features, regardless of client.   |


| Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new |


\--------------------------------------------------------------------/




[WARNING] The following environment variables are being overriden by the config file,


[WARNING] please use the admin panel to make changes to them:


[WARNING] DOMAIN, SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, SHOW_PASSWORD_HINT, ADMIN_TOKEN




[2020-03-27 18:53:51][ws][INFO] Listening for new connections on 0.0.0.0:3012.


[2020-03-27 18:53:51][start][INFO] Rocket has launched from http://0.0.0.0:80


[2020-03-27 19:03:12][request][INFO] POST /identity/connect/token


[2020-03-27 19:03:12][response][INFO] POST /identity/connect/token (login) => 200 OK


[2020-03-27 19:03:12][request][INFO] GET /api/sync


[2020-03-27 19:03:12][response][INFO] GET /api/sync?<data..> (sync) => 200 OK


[2020-03-27 19:03:14][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:53526.


[2020-03-27 19:03:23][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:62963.


[2020-03-27 19:03:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.


[2020-03-27 19:03:23][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:62969.


[2020-03-27 19:03:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.````
<!-- gh-comment-id:605008338 --> @mokshmridul commented on GitHub (Mar 27, 2020): Im sorry to ask, but i understand that the commit was merged into the latest build (digest 0035b5d8b0a3), and i have updated to this version. however i am still getting the error. ````/--------------------------------------------------------------------\ | Starting Bitwarden_RS | | Version 1.14.1-ec608390 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new | \--------------------------------------------------------------------/ [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] DOMAIN, SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, SHOW_PASSWORD_HINT, ADMIN_TOKEN [2020-03-27 18:53:51][ws][INFO] Listening for new connections on 0.0.0.0:3012. [2020-03-27 18:53:51][start][INFO] Rocket has launched from http://0.0.0.0:80 [2020-03-27 19:03:12][request][INFO] POST /identity/connect/token [2020-03-27 19:03:12][response][INFO] POST /identity/connect/token (login) => 200 OK [2020-03-27 19:03:12][request][INFO] GET /api/sync [2020-03-27 19:03:12][response][INFO] GET /api/sync?<data..> (sync) => 200 OK [2020-03-27 19:03:14][ws::io][INFO] Accepted a new tcp connection from 172.18.0.1:53526. [2020-03-27 19:03:23][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:62963. [2020-03-27 19:03:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. [2020-03-27 19:03:23][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:62969. [2020-03-27 19:03:23][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.````
kerem commented 2026-03-03 02:01:54 +03:00
Author
Owner
Copy link

@jjlin commented on GitHub (Mar 27, 2020):

Your Missing id or access token error is gone. I'm running 1.14.1-ec608390 with HAProxy, and WebSocket notifications are working fine for me.

Given that you said you had it working before, I'd suspect that you changed something in your configuration somewhere, so maybe reflect on what that could be. Based on the error message, it looks like the Sec-WebSocket-Key HTTP header isn't making it through to bitwarden_rs for some reason. If you're also proxying through Cloudflare, you might take a look at any firewall rules and such that you have there. Finally, you might try running a WebSocket test client/server and making sure that works properly (e.g., see https://www.nginx.com/blog/websocket-nginx/).

<!-- gh-comment-id:605243092 --> @jjlin commented on GitHub (Mar 27, 2020): Your `Missing id or access token` error is gone. I'm running 1.14.1-ec608390 with HAProxy, and WebSocket notifications are working fine for me. Given that you said you had it working before, I'd suspect that you changed something in your configuration somewhere, so maybe reflect on what that could be. Based on the error message, it looks like the `Sec-WebSocket-Key` HTTP header isn't making it through to bitwarden_rs for some reason. If you're also proxying through Cloudflare, you might take a look at any firewall rules and such that you have there. Finally, you might try running a WebSocket test client/server and making sure that works properly (e.g., see https://www.nginx.com/blog/websocket-nginx/).
kerem commented 2026-03-03 02:01:54 +03:00
Author
Owner
Copy link

@mokshmridul commented on GitHub (Mar 27, 2020):

I am running it through a Nginx and through Cloudflare. However as i mentioned, even when i go directly to the internal IP 192.168.0.11:3012 i get the same error, which leads me to believe that its not an error with Nginx / Cloudflare.

I tried reverting to my previous settings, but its still a no-go. Any ideas as to where i could look further? I am just going to check if maybe its something on my firewall (pfsense).

Note: It seems like the connection is going through, but something else is going wrong. Im basing this on the following lines in the log file

[2020-03-28 01:16:28][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:50418
[2020-03-28 01:16:28][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key.

Edit: Okay so the functionality is working fine as of now, but im still getting the error mentioned above. Am i doing something wrong?

<!-- gh-comment-id:605282237 --> @mokshmridul commented on GitHub (Mar 27, 2020): I am running it through a Nginx and through Cloudflare. However as i mentioned, even when i go directly to the internal IP ``192.168.0.11:3012`` i get the same error, which leads me to believe that its not an error with Nginx / Cloudflare. I tried reverting to my previous settings, but its still a no-go. Any ideas as to where i could look further? I am just going to check if maybe its something on my firewall (pfsense). Note: It seems like the connection is going through, but something else is going wrong. Im basing this on the following lines in the log file ```` [2020-03-28 01:16:28][ws::io][INFO] Accepted a new tcp connection from 192.168.0.23:50418 [2020-03-28 01:16:28][ws::handler][ERROR] WS Error <Protocol>: Unable to parse WebSocket key. ```` Edit: Okay so the functionality is working fine as of now, but im still getting the error mentioned above. Am i doing something wrong?
kerem commented 2026-03-03 02:01:54 +03:00
Author
Owner
Copy link

@jjlin commented on GitHub (Mar 27, 2020):

Do you have a regular HTTP client somewhere trying to do a GET on http://192.168.0.11:3012/notifications/hub? That's exactly the error you would get since a non-WebSocket client wouldn't know to send a Sec-WebSocket-Key header. Your test where you "go directly to the internal IP 192.168.0.11:3012" is invalid for the same reason.

<!-- gh-comment-id:605298135 --> @jjlin commented on GitHub (Mar 27, 2020): Do you have a regular HTTP client somewhere trying to do a GET on http://192.168.0.11:3012/notifications/hub? That's exactly the error you would get since a non-WebSocket client wouldn't know to send a `Sec-WebSocket-Key` header. Your test where you "go directly to the internal IP 192.168.0.11:3012" is invalid for the same reason.
kerem commented 2026-03-03 02:01:54 +03:00
Author
Owner
Copy link

@mokshmridul commented on GitHub (Mar 28, 2020):

Do you have a regular HTTP client somewhere trying to do a GET on http://192.168.0.11:3012/notifications/hub? That's exactly the error you would get since a non-WebSocket client wouldn't know to send a Sec-WebSocket-Key header. Your test where you "go directly to the internal IP 192.168.0.11:3012" is invalid for the same reason.

Okay, that makes sense now. Thank you for the quick help on this one.

<!-- gh-comment-id:605393865 --> @mokshmridul commented on GitHub (Mar 28, 2020): > Do you have a regular HTTP client somewhere trying to do a GET on http://192.168.0.11:3012/notifications/hub? That's exactly the error you would get since a non-WebSocket client wouldn't know to send a `Sec-WebSocket-Key` header. Your test where you "go directly to the internal IP 192.168.0.11:3012" is invalid for the same reason. Okay, that makes sense now. Thank you for the quick help on this one.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.8
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
1.35.2
1.35.1
1.35.0
1.34.3
1.34.2
1.34.1
1.34.0
1.33.2
1.33.1
1.33.0
1.32.7
1.32.6
1.32.5
1.32.4
1.32.3
1.32.2
1.32.1
1.32.0
1.31.0
1.30.5
1.30.4
1.30.3
1.30.2
1.30.1
1.30.0
1.29.2
1.29.1
1.29.0
1.28.1
1.28.0
1.27.0
1.26.0
1.25.2
1.25.1
1.25.0
1.24.0
1.23.1
1.23.0
1.22.2
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.0
1.17.0
1.16.3
1.16.2
1.16.1
1.16.0
1.15.1
1.15.0
1.14.2
1.14.1
1.14
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
Labels
Clear labels   
SSO

   
Third party

   
better for forum

   
bug

   
bug

   
documentation

   
duplicate

   
enhancement

   
future Vault

   
future Vault

   
future Vault

   
good first issue

   
help wanted

   
low priority

   
notes

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
troubleshooting

   
wontfix
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#660
No description provided.