iOS works but Browsers/Websockets throw an "Unexpected Error" #2049

Closed
opened 2025-10-09 17:43:12 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @MaestroJAL on GitHub.

First off, excellent work on bitwarden_rs! Thank you for this. If I can fix this, my whole family will be set. I cannot seem to login via any browser but the iOS app allows account creation and syncs very well. I'm using Nginx as a reverse proxy. I've tried a lot of different configurations. Here's a snippet of my my current conf:

upstream bitwarden_rs {
        server 127.0.0.1:8082;
        keepalive 64;
}

location /bw/ {
                proxy_pass              http://bitwarden_rs/;
                proxy_redirect          off;
                proxy_set_header        Upgrade                 $http_upgrade;
                proxy_set_header        Connection              "upgrade";
                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-Host        $server_name;
                proxy_set_header        X-Forwarded-Proto       $scheme;
                proxy_set_header        X-Forwarded-Protocol    $scheme;
                proxy_set_header        X-Url-Scheme            $scheme;
        }

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

        location /bw/notifications/hub/negotiate {
                proxy_pass              http://bitwarden_rs/;
        }
Originally created by @MaestroJAL on GitHub. First off, excellent work on bitwarden_rs! Thank you for this. If I can fix this, my whole family will be set. I cannot seem to login via any browser but the iOS app allows account creation and syncs very well. I'm using Nginx as a reverse proxy. I've tried a lot of different configurations. Here's a snippet of my my current conf: ``` upstream bitwarden_rs { server 127.0.0.1:8082; keepalive 64; } location /bw/ { proxy_pass http://bitwarden_rs/; proxy_redirect off; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; 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-Host $server_name; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Protocol $scheme; proxy_set_header X-Url-Scheme $scheme; } location /bw/notifications/hub { proxy_pass http://127.0.0.1:3012; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /bw/notifications/hub/negotiate { proxy_pass http://bitwarden_rs/; } ```
Author
Owner

@dani-garcia commented on GitHub:

Using bitwarden_rs in a subfolder is not recommended and requires some patches to the web vault to make it work. If you can, I'd recommend to use the root directory, maybe in a subdomain.

@dani-garcia commented on GitHub: Using bitwarden_rs in a subfolder is not recommended and requires some patches to the web vault to make it work. If you can, I'd recommend to use the root directory, maybe in a subdomain.
Author
Owner

@MaestroJAL commented on GitHub:

Thanks for the response! I’ll work to get that done.

@MaestroJAL commented on GitHub: Thanks for the response! I’ll work to get that done.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#2049