mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
WebVault 2.16 throws a 404 when building trying to create an organisation. #1611
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kinsago on GitHub.
Hi all,
I've built web-vault 2.16 a few times and each time I'm unable to create an organisation from within the web vault (It hangs with "/api/plans/:1 Failed to load resource: the server responded with a status of 404 ()"). Having tried to resolve this for a few days, today I deleted the web-vault folder on my server and compiled 2.15.1 (following the same steps as before) which seems to have worked first time. I'm therefore wondering if there's something in 2.16 that's broken?
Instructions I followed for compiling are on this website https://pieterhollander.nl/post/bitwarden. Server is Debian 10.
Thanks,
Phil
@kinsago commented on GitHub:
Hi all,
Apologies for the delay, I was away for a few days. I've recompiled web-vault this morning using the latest version of the vault and patch 2.16.0 and it's still showing the same problem. I've reverted back to 2.15.1 for now. I did have to manually wget the 2.16.0 so I wonder if the bitwarden webvault has been updated again?
I forgot to mention, I'm compiling on a Ubuntu 14.04 server and running on a Debian 10 server (my Debian box doesn't have enough grunt to compile). I don't think it's relevant as the previous version of webvault compiles and runs without issues and compiling 2.16.0 doesn't generate any errors.
@BlackDex commented on GitHub:
This was a bug and already fixed in the latest version.
@dinger1986 commented on GitHub:
I built a script to install https://github.com/dinger1986/bitwardenrs_install_script using 2.16 and compiling fine for me. works on ubuntu 20.04.
The issue with the organisation was fixed yesterday, if you have done all the prerequisites you could use the update script I have written and just remove the ubuntu check?
The script for downloading and compiling is:
#Download newest versions of Bitwarden RS and compile
git clone https://github.com/dani-garcia/bitwarden_rs.git
cd bitwarden_rs/
git checkout
cargo build --features sqlite --release
cd ..
#Clone and checkout repository for Bitwarden web and patch
git clone https://github.com/bitwarden/web.git
cd web
git checkout
wget https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/$(git tag --sort=v:refname | tail -n1).patch
git apply $(git tag --sort=v:refname | tail -n1).patch
#Build Web
npm run sub:init
npm install
npm audit fix
npm run dist
cd ..
@kinsago commented on GitHub:
Thanks - I'll give it a go later and report back.
Thanks for the quick response.
Phil
@dinger1986 commented on GitHub:
What command are you using to check out the code from github?
Daniel Lamb
Technical Director
[cid:logo_2094e808-adcc-455a-a5fd-54265dc137fa.jpg]http://www.flonix.co.uk/
Flonix Limited
Willowview
Redgorton
Perth
PH1 3EL
Phone: 01738 500400
http://www.flonix.co.uk
Company Reg: SC341802
[cid:fb_11c7c55d-b85e-4b3e-b8d8-daabbed1905e.png]https://www.facebook.com/Flonixltd/
From: kinsago notifications@github.com
Sent: 21 September 2020 09:33
To: dani-garcia/bitwarden_rs bitwarden_rs@noreply.github.com
Cc: Daniel Lamb | Flonix Ltd daniel.lamb@flonix.co.uk; Comment comment@noreply.github.com
Subject: Re: [dani-garcia/bitwarden_rs] WebVault 2.16 throws a 404 when building trying to create an organisation. (#1144)
Hi all,
Apologies for the delay, I was away for a few days. I've recompiled web-vault this morning using the latest version of the vault and patch 2.16.0 and it's still showing the same problem. I've reverted back to 2.15.1 for now. I did have to manually wget the 2.16.0 so I wonder if the bitwarden webvault has been updated again?
I forgot to mention, I'm compiling on a Ubuntu 14.04 server and running on a Debian 10 server (my Debian box doesn't have enough grunt to compile). I don't think it's relevant as the previous version of webvault compiles and runs without issues and compiling 2.16.0 doesn't generate any errors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dani-garcia/bitwarden_rs/issues/1144#issuecomment-695978306, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXIVH67ZRQS3LDHPNBE5KLSG4FV5ANCNFSM4RNMV53Q.
@kinsago commented on GitHub:
I'll try the precompiled web-build and confirm later.
@BlackDex commented on GitHub:
If you see a 404 error it probably is the
/api/planslink.If that is the case you probably still have an older version of bitwarden_rs since that is fixed in the latest version
@kinsago commented on GitHub:
Hi,
Looking back through the console output, this is indeed a new version "Note: switching to 'v2.16.1'."
I then use
wget https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/$(git tag --sort=v:refname | tail -n1).patchwhich returns a 404 (makes sense as I'm now on v2.16.1) so I then manually wget the 2.16.0 patch.
wget https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/v2.16.0.patchand apply it with
git apply v2.16.0.patchHope this helps.
@dinger1986 commented on GitHub:
I also tried the same but used this to check out etc:
#Compile bitwarden_rs
git clone https://github.com/dani-garcia/bitwarden_rs.git
cd bitwarden_rs/
git checkout
cargo build --features sqlite --release
cd ..
#Clone and checkout repository for Bitwarden web and patch
git clone https://github.com/bitwarden/web.git
cd web
git checkout
wget https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/$(git tag --sort=v:refname | tail -n1).patch
git apply $(git tag --sort=v:refname | tail -n1).patch
@dinger1986 commented on GitHub:
you can also download the latest precompiled web-build from here https://github.com/dani-garcia/bw_web_builds/releases
@kinsago commented on GitHub:
Thanks all, recompiling and redeploying the server and the web-vault seems to have resolved this for v2.16.0