[GH-ISSUE #934] WebSocket notifications problems #663

New issue

Closed

opened 2026-03-03 02:01:55 +03:00 by kerem · 3 comments

kerem commented

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

Owner

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

I have Bitwarden_RS running on my Synology - Docker.
Creating users, webpage etc is working great. Except (auto) syncing the desktop app and browser extension through webSocket notifications.
WEBSOCKET_ENABLED=true has been set.

Auto syncing is not working and I'm seeing the following error in the logs:
[ws::handler][ERROR] WS Error <Io(Kind(InvalidData))>: Missing id or access token

Any one have a clue what's going on?

I have created a bitwarden.conf file in /etc/nginx/sites-enabled with the following config:

    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    server_name bitwarden.mydomain.com;

    ssl_certificate /usr/syno/etc/certificate/ReverseProxy/fghrthtrh/fullchain.pem;

    ssl_certificate_key /usr/syno/etc/certificate/ReverseProxy/fghrthtrh/privkey.pem;

    location / {

        proxy_connect_timeout 60;

        proxy_read_timeout 60;

        proxy_send_timeout 60;

        proxy_intercept_errors off;

        proxy_http_version 1.1;

        proxy_set_header        Host            $http_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://localhost:8080;

    }

    location /notifications/hub {
        proxy_pass http://localhost:3012;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    location /notifications/hub/negotiate {
        proxy_pass http://localhost:8080;
    }

    error_page 403 404 500 502 503 504 @error_page;

    location @error_page {
        root /usr/syno/share/nginx;
        rewrite (.*) /error.html break;
        allow all;
    }

}

Originally created by @Panja0 on GitHub (Mar 27, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/934 I have Bitwarden_RS running on my Synology - Docker. Creating users, webpage etc is working great. Except (auto) syncing the desktop app and browser extension through webSocket notifications. WEBSOCKET_ENABLED=true has been set. Auto syncing is not working and I'm seeing the following error in the logs: _[ws::handler][ERROR] WS Error <Io(Kind(InvalidData))>: Missing id or access token_ Any one have a clue what's going on? I have created a bitwarden.conf file in /etc/nginx/sites-enabled with the following config: ```server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name bitwarden.mydomain.com; ssl_certificate /usr/syno/etc/certificate/ReverseProxy/fghrthtrh/fullchain.pem; ssl_certificate_key /usr/syno/etc/certificate/ReverseProxy/fghrthtrh/privkey.pem; location / { proxy_connect_timeout 60; proxy_read_timeout 60; proxy_send_timeout 60; proxy_intercept_errors off; proxy_http_version 1.1; proxy_set_header Host $http_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://localhost:8080; } location /notifications/hub { proxy_pass http://localhost:3012; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://localhost:8080; } error_page 403 404 500 502 503 504 @error_page; location @error_page { root /usr/syno/share/nginx; rewrite (.*) /error.html break; allow all; } }

kerem

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

closed this issue
added the
better for forum
label

kerem commented

2026-03-03 02:01:56 +03:00

Author

Owner

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

may be fixed now: https://github.com/dani-garcia/bitwarden_rs/pull/932

@sentriz commented on GitHub (Mar 27, 2020): may be fixed now: https://github.com/dani-garcia/bitwarden_rs/pull/932

kerem commented

2026-03-03 02:01:56 +03:00

Author

Owner

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

Sounds good!
Will have a look later on this weekend and report back.
Thx!

@Panja0 commented on GitHub (Mar 27, 2020): Sounds good! Will have a look later on this weekend and report back. Thx!

kerem commented

2026-03-03 02:01:56 +03:00

Author

Owner

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

It's indeed fixed with the latest version. Many thanks!

@Panja0 commented on GitHub (Mar 27, 2020): It's indeed fixed with the latest version. Many thanks!

kerem referenced this issue

2026-03-03 08:53:01 +03:00

[PR #664] [MERGED] Fixed issue #663. #2773