Unable to create organization

Help
1

Hello,

I installed Bitwarden RS 1.16.3 and the vault 2.16.1 but I can’t create an organization. A request is made on /api/plans/ and never succeeds.

Apparently this problem would have been fixed in a PR?

2

Indeed, that should be fixed, at least if you use the latest tag for the docker image

3

I don’t use the docker image, I compiled the binaries.

4

@aponsin, then if you use the master repo it should be fixed.
I created and tested the PR my self, and others tested this afterwards and works for them.

I Also have created a fix for some database issues which needed me to create organizations etc… which i did after the /api/plans, so i’m sure it works on the latest master branch.

5

OK so how do explain the fact that everything is up to date on my side but when I click on New Organization it never happens?

Screenshot_2020-10-02 New Organization Bitwarden Web Vault
Screenshot_2020-10-02 New Organization Bitwarden Web Vault900×278 10.4 KB

Thanks for your time.

6

The only way i can explain that, is that it isn’t up-to-date.
I just did a fresh build after a cargo clean so all was removed.

The steps i took:
web-vault:

bitwarden_rs:

  • git pull upstream master or git pull if you are using the direct repo from dani-garcia.
  • git fetch --all --tags
  • git describe --abbrev=0 --tags ; git rev-parse HEAD
    Which outputs: 1.16.3 and 37776241bead80926d35bff0cfa4577e8adefd2e
  • cargo clean
  • cargo build --features sqlite,mysql,postgresql
  • ./target/debug/bitwarden_rs - Returns: Version 1.16.3-37776241

When i want to create a new org i see the following:
image

This is a clean environment using a sqlite3 database in this case.
Running on a Ubuntu 18.04 LXD Container.

I’m also using haproxy to get websockets working.
But also without websockets it’s working.

7

About the version of Bitwarden:

$ sudo /usr/loca/bin/bitwarden --version
bitwarden_rs 1.16.3

About the version of the vault:

$ sudo grep "version" /var/www/vault.xxx.xxx/build/version.json
{"version":"2.16.1"}

As you can see, everything is up to date.

8

Then, what is your browser telling you if you have the developer console open (F12)?
And then go to the create organization page?

Browser:
image

My bitwarden-log:

[2020-10-02 12:01:03.781][request][INFO] GET /api/plans/
[2020-10-02 12:01:03.784][response][INFO] GET /api/plans (get_plans) => 200 OK
9

HTTP request (/var/log/bitwarden/access_log):

2a01:e0a:16f:xxx - - [02/Oct/2020:14:07:10 +0200] "GET /api/plans/ HTTP/2.0" 404 597 "https://vault.xxx.xxx/" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0"

Developer console:

XHR GET https://vault.xxx.xxx/api/plans/
[HTTP/2 404 Not Found 16ms]

ERROR Error: Uncaught (in promise): t: {"response":null,"statusCode":404}
    Angular 2
    s main.8bc41762fd7ae6d7d4ae.js:1
    Angular 24
    l main.8bc41762fd7ae6d7d4ae.js:1
    t Angular
    l main.8bc41762fd7ae6d7d4ae.js:1
    a main.8bc41762fd7ae6d7d4ae.js:1
    Angular 31
    B organizations.component.html:50
    Angular 9
    N organizations.component.html:48
    bo Angular
core.js:4127:18
10

You can’t access this directly, you need to be logged-in on the vault and that link needs to be requested by the javascript because it needs to send some headers and cookies etc…

11

I’m logged in, otherwise I can not click on the button New Organisation…

Screenshot_2020-10-02 My Vault Bitwarden Web Vault

12

Well that 404 is generated when the correct headers arn’t sent.
So, what is the rest of the setup?
How is everything tied together?

Proxy, ssl, os etc?
Please give as much as details on your setup as you can.

13

I wrote an article. My Bitwarden RS instance is deployed this way.

14

@aponsin, reading your article, i have to conclude that you are not on the latest version.
You use a tagged version 1.16.3 from August the 8th (a7a479623c6f23243c5d242d08a92ccf3fb5bc0c) and not the master branch as i suggested that you needed to use.

15

See the changes done since then: https://github.com/dani-garcia/bitwarden_rs/compare/1.16.3...master

16

I thought that using the latest release “guaranteed” that the application would be stable… But now I understand better, I will use the master branch.

I’ll be back later to give you an update.

17

Well, it does, but for that you also need to use the matching web-vault which is 2.15.1, and not 2.16.1.

18

Okay, but why? How do I know which version of the vault to use?

19

That is a bit difficult, but it is located in https://github.com/dani-garcia/bitwarden_rs/blob/master/docker/Dockerfile.j2#L30 where that hash points to a specific docker image.

20

It’s really not convenient… Are there many drawbacks to using version 2.16.1?