FS#76133 - Incompatibility issue: vaultwarden v1.25.2 and vaultwarden-web v2022.9.0 - error creating new org
Attached to Project:
Community Packages
Opened by Bouke J. Henstra (bouke) - Friday, 07 October 2022, 09:37 GMT
Last edited by George Rawlinson (rawlinsong) - Wednesday, 12 October 2022, 00:20 GMT
Opened by Bouke J. Henstra (bouke) - Friday, 07 October 2022, 09:37 GMT
Last edited by George Rawlinson (rawlinsong) - Wednesday, 12 October 2022, 00:20 GMT
|
Details
Description:
Vaultwarden 1.25.2-1 is not compatible with 2022.9.0 web-vault version. When I click the button "+ New organisation" in the web-vault, then the "New organisation" text is visible with a animated gif / loading indicator - and the process will stall. In the log file there's the following eror: [2022-10-06 22:32:48.043][request][INFO] GET /api/plans/ [2022-10-06 22:32:48.043][auth][ERROR] Unauthorized Error: No access token provided [2022-10-06 22:32:48.043][_][WARN] Request guard `Headers` failed: "No access token provided". [2022-10-06 22:32:48.043][_][WARN] No 401 catcher registered. Using Rocket default. [2022-10-06 22:32:48.043][response][INFO] (get_plans) GET /api/plans => 401 Unauthorized Additional info: * package version(s): 1.25.2-1 (vaultwarden), 2022.9.0-1 (vaultwarden-web) * config and/or log files: please see "upstream bug report" * link to upstream bug report: https://github.com/dani-garcia/vaultwarden/discussions/2802 Steps to reproduce: When there is a working installation, then I recommend not to upgrade at the moment. I did however upgrade my vault at home - and I can't add organisations at the moment. The problem isn't reproducible on the previous version (as it did work) but I can confirm it is reproducible when 1.25.2-1 (vaultwarden) + 2022.9.0-1 (vaultwarden-web) are installed. |
This task depends upon
Closed by George Rawlinson (rawlinsong)
Wednesday, 12 October 2022, 00:20 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 1.25.2-2
Wednesday, 12 October 2022, 00:20 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 1.25.2-2
I was able to workaround the problem by installing version 2022.8.1 of the web-vault.
I copied /usr/share/webapps/vaultwarden-web to $HOME/bak/usr/share/webapps/vaultwarden-web/ (backup).
Next I issued the following commands:
```
$ cd $HOME
$ mkdir git
$ cd git
$ mkdir vaultwarden
$ cd vaultwarden
$ git clone https://github.com/bitwarden/clients.git web-vault.git && cd web-vault.git
$ git -c advice.detachedHead=false checkout web-v2022.8.1
$ wget https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/v2022.8.0.patch
$ git apply v2022.8.0.patch
$ npm ci && npm audit fix || true && pushd apps/web/ && npm run dist:oss:selfhost
```
Finally copied ~/git/vaultwarden/web-vault.git/apps/web to /usr/share/webapps/vaultwarden-web with 'mc'.
I am able to create organisations again with vaultwarden-web 2022.8.1.
I did copy the original executable to 'vaultwarden_bak'.
When I compare both files/versions, there is "382e6107" added to the version no (of the self compiled version). I think that's the commit hash of the test build.
```
[root@psw01 /]# /usr/bin/vaultwarden -v
vaultwarden 1.25.2-382e6107
[root@psw01 /]# /usr/bin/vaultwarden_bak -v
vaultwarden 1.25.2
```
The file size also differs:
```
# ls -lah /usr/bin/vaultwarden*
-rwxr-xr-x 1 root root 33M Oct 11 20:15 /usr/bin/vaultwarden
-rwxr-xr-x 1 root root 30M Oct 11 20:15 /usr/bin/vaultwarden_bak
```
The original vaultwarden v1.25.2 does work fine with vaultwarden-web v2022.8.1 (but not with 2022.9.x).
The self compiled vaultwarden 1.25.2 works fine with vaultwarden-web v2022.9.x.
Please also note the comment of BlackDex about the commit hash:
https://github.com/dani-garcia/vaultwarden/discussions/2802#discussioncomment-3821194