[GH-ISSUE #559] Vault empty; No longer Part of Organisations #362

New issue

Closed

opened 2026-03-03 01:28:23 +03:00 by kerem · 7 comments

kerem commented 2026-03-03 01:28:23 +03:00

Owner

Copy link

Originally created by @davidh2k on GitHub (Aug 7, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/559

I have an issue, when I log into the webinterface (or any new remote client) I have an empty Vault, it even states that I'm no longer part of any of my two organisations.

However, if i look at the admin panel, it still shows my belonging to the two organisations:

I already did a backup of my still synched desktop client that had the passwords still. Any ideas how my vault can be empty? Could that hapenned on a container update?

Originally created by @davidh2k on GitHub (Aug 7, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/559 I have an issue, when I log into the webinterface (or any new remote client) I have an empty Vault, it even states that I'm no longer part of any of my two organisations.  However, if i look at the admin panel, it still shows my belonging to the two organisations:  I already did a backup of my still synched desktop client that had the passwords still. Any ideas how my vault can be empty? Could that hapenned on a container update?

kerem closed this issue 2026-03-03 01:28:23 +03:00

kerem commented 2026-03-03 01:28:24 +03:00

Author

Owner

Copy link

@davidh2k commented on GitHub (Aug 7, 2019):

For Sanity checking I just added one dummy password and both restarted and --force-recreate'd the container via docker-compose - dummy password still there.

<!-- gh-comment-id:519014722 --> @davidh2k commented on GitHub (Aug 7, 2019): For Sanity checking I just added one dummy password and both restarted and --force-recreate'd the container via docker-compose - dummy password still there.

kerem commented 2026-03-03 01:28:24 +03:00

Author

Owner

Copy link

@davidh2k commented on GitHub (Aug 7, 2019):

[2019-08-07 10:56:11][rocket::rocket][INFO] GET / text/html:
[2019-08-07 10:56:11][][INFO] Matched: GET / (web_index)
[2019-08-07 10:56:11][][INFO] Outcome: Success
[2019-08-07 10:56:11][][INFO] Response succeeded.
[2019-08-07 10:56:19][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8:
[2019-08-07 10:56:19][][INFO] Matched: POST /api/accounts/prelogin (prelogin)
[2019-08-07 10:56:19][][INFO] Outcome: Success
[2019-08-07 10:56:19][][INFO] Response succeeded.
[2019-08-07 10:56:19][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-08-07 10:56:19][][INFO] Matched: POST /identity/connect/token (login)
[2019-08-07 10:56:19][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[0],"TwoFactorProviders2":{"0":null},"error":"invalid_grant","error_description":"Two factor required."}
[2019-08-07 10:56:19][][INFO] Outcome: Success
[2019-08-07 10:56:19][][INFO] Response succeeded.
[2019-08-07 10:56:33][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-08-07 10:56:33][][INFO] Matched: POST /identity/connect/token (login)
[2019-08-07 10:56:33][bitwarden_rs::api::identity][INFO] User user@mail.domain logged in successfully. IP: 62.176.232.167
[2019-08-07 10:56:33][][INFO] Outcome: Success
[2019-08-07 10:56:33][][INFO] Response succeeded.
[2019-08-07 10:56:33][rocket::rocket][INFO] POST /notifications/hub/negotiate text/plain; charset=UTF-8:
[2019-08-07 10:56:33][][INFO] Matched: POST /notifications/hub/negotiate (negotiate)
[2019-08-07 10:56:33][][INFO] Outcome: Success
[2019-08-07 10:56:33][][INFO] Response succeeded.
[2019-08-07 10:56:33][rocket::rocket][INFO] GET /api/sync?excludeDomains=true application/json:
[2019-08-07 10:56:33][][INFO] Matched: GET /api/sync?<data..> (sync)
thread '' panicked at 'called Result::unwrap() on an Err value: Error("EOF while parsing a value", line: 1, column: 0)', src/libcore/result.rs:997:5
[2019-08-07 10:56:33][ws::io][INFO] Accepted a new tcp connection from 172.19.0.4:48452.
[2019-08-07 10:56:33][bitwarden_rs::api::notifications][INFO] Server got message '{"protocol":"messagepack","version":1}'.

Maybe this is in any way related to https://github.com/dani-garcia/bitwarden_rs/issues/494 ?

<!-- gh-comment-id:519048112 --> @davidh2k commented on GitHub (Aug 7, 2019): > [2019-08-07 10:56:11][rocket::rocket][INFO] GET / text/html: > [2019-08-07 10:56:11][_][INFO] Matched: GET / (web_index) > [2019-08-07 10:56:11][_][INFO] Outcome: Success > [2019-08-07 10:56:11][_][INFO] Response succeeded. > [2019-08-07 10:56:19][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8: > [2019-08-07 10:56:19][_][INFO] Matched: POST /api/accounts/prelogin (prelogin) > [2019-08-07 10:56:19][_][INFO] Outcome: Success > [2019-08-07 10:56:19][_][INFO] Response succeeded. > [2019-08-07 10:56:19][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: > [2019-08-07 10:56:19][_][INFO] Matched: POST /identity/connect/token (login) > [2019-08-07 10:56:19][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[0],"TwoFactorProviders2":{"0":null},"error":"invalid_grant","error_description":"Two factor required."} > [2019-08-07 10:56:19][_][INFO] Outcome: Success > [2019-08-07 10:56:19][_][INFO] Response succeeded. > [2019-08-07 10:56:33][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: > [2019-08-07 10:56:33][_][INFO] Matched: POST /identity/connect/token (login) > [2019-08-07 10:56:33][bitwarden_rs::api::identity][INFO] User user@mail.domain logged in successfully. IP: 62.176.232.167 > [2019-08-07 10:56:33][_][INFO] Outcome: Success > [2019-08-07 10:56:33][_][INFO] Response succeeded. > [2019-08-07 10:56:33][rocket::rocket][INFO] POST /notifications/hub/negotiate text/plain; charset=UTF-8: > [2019-08-07 10:56:33][_][INFO] Matched: POST /notifications/hub/negotiate (negotiate) > [2019-08-07 10:56:33][_][INFO] Outcome: Success > [2019-08-07 10:56:33][_][INFO] Response succeeded. > [2019-08-07 10:56:33][rocket::rocket][INFO] GET /api/sync?excludeDomains=true application/json: > [2019-08-07 10:56:33][_][INFO] Matched: GET /api/sync?<data..> (sync) > thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Error("EOF while parsing a value", line: 1, column: 0)', src/libcore/result.rs:997:5 > [2019-08-07 10:56:33][ws::io][INFO] Accepted a new tcp connection from 172.19.0.4:48452. > [2019-08-07 10:56:33][bitwarden_rs::api::notifications][INFO] Server got message '{"protocol":"messagepack","version":1}'. Maybe this is in any way related to https://github.com/dani-garcia/bitwarden_rs/issues/494 ?

kerem commented 2026-03-03 01:28:24 +03:00

Author

Owner

Copy link

@davidh2k commented on GitHub (Aug 7, 2019):

I just kinda solved it by pulling the current image and switching from version:

/--------------------------------------------------------------------
| Starting Bitwarden_RS |

Version 1.8.0-f25ab42e

to:

/--------------------------------------------------------------------
| Starting Bitwarden_RS |

Version 1.9.1-8be2ed62

Log now shows:

[2019-08-07 11:05:09][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8:
[2019-08-07 11:05:09][][INFO] Matched: POST /api/accounts/prelogin (prelogin)
[2019-08-07 11:05:09][][INFO] Outcome: Success
[2019-08-07 11:05:09][][INFO] Response succeeded.
[2019-08-07 11:05:09][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-08-07 11:05:09][][INFO] Matched: POST /identity/connect/token (login)
[2019-08-07 11:05:09][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[0],"TwoFactorProviders2":{"0":null},"error":"invalid_grant","error_description":"Two factor required."}
[2019-08-07 11:05:09][][INFO] Outcome: Success
[2019-08-07 11:05:09][][INFO] Response succeeded.
[2019-08-07 11:05:16][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-08-07 11:05:16][][INFO] Matched: POST /identity/connect/token (login)
[2019-08-07 11:05:16][bitwarden_rs::api::identity][INFO] User mail@domain.tld logged in successfully. IP: 62.176.232.167
[2019-08-07 11:05:16][][INFO] Outcome: Success
[2019-08-07 11:05:16][][INFO] Response succeeded.
[2019-08-07 11:05:16][rocket::rocket][INFO] POST /notifications/hub/negotiate text/plain; charset=UTF-8:
[2019-08-07 11:05:16][][INFO] Matched: POST /notifications/hub/negotiate (negotiate)
[2019-08-07 11:05:16][][INFO] Outcome: Success
[2019-08-07 11:05:16][][INFO] Response succeeded.
[2019-08-07 11:05:16][rocket::rocket][INFO] GET /api/sync?excludeDomains=true application/json:
[2019-08-07 11:05:16][][INFO] Matched: GET /api/sync?<data..> (sync)
[2019-08-07 11:05:16][][INFO] Outcome: Success
[2019-08-07 11:05:16][_][INFO] Response succeeded.
[2019-08-07 11:05:16][ws::io][INFO] Accepted a new tcp connection from 172.19.0.4:48578.
[2019-08-07 11:05:16][bitwarden_rs::api::notifications][INFO] Server got message '{"protocol":"messagepack","version":1}'.

And Webinterface shows all passwords and organisations again. So in fact maybe really related to #494 ?

Solved for the moment, but worth investigating more?

<!-- gh-comment-id:519051303 --> @davidh2k commented on GitHub (Aug 7, 2019): I just _kinda_ solved it by pulling the current image and switching from version: > /--------------------------------------------------------------------\ > | Starting Bitwarden_RS | > | Version 1.8.0-f25ab42e | > |--------------------------------------------------------------------| to: > /--------------------------------------------------------------------\ > | Starting Bitwarden_RS | > | Version 1.9.1-8be2ed62 | > |--------------------------------------------------------------------| Log now shows: > [2019-08-07 11:05:09][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8: > [2019-08-07 11:05:09][_][INFO] Matched: POST /api/accounts/prelogin (prelogin) > [2019-08-07 11:05:09][_][INFO] Outcome: Success > [2019-08-07 11:05:09][_][INFO] Response succeeded. > [2019-08-07 11:05:09][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: > [2019-08-07 11:05:09][_][INFO] Matched: POST /identity/connect/token (login) > [2019-08-07 11:05:09][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[0],"TwoFactorProviders2":{"0":null},"error":"invalid_grant","error_description":"Two factor required."} > [2019-08-07 11:05:09][_][INFO] Outcome: Success > [2019-08-07 11:05:09][_][INFO] Response succeeded. > [2019-08-07 11:05:16][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: > [2019-08-07 11:05:16][_][INFO] Matched: POST /identity/connect/token (login) > [2019-08-07 11:05:16][bitwarden_rs::api::identity][INFO] User mail@domain.tld logged in successfully. IP: 62.176.232.167 > [2019-08-07 11:05:16][_][INFO] Outcome: Success > [2019-08-07 11:05:16][_][INFO] Response succeeded. > [2019-08-07 11:05:16][rocket::rocket][INFO] POST /notifications/hub/negotiate text/plain; charset=UTF-8: > [2019-08-07 11:05:16][_][INFO] Matched: POST /notifications/hub/negotiate (negotiate) > [2019-08-07 11:05:16][_][INFO] Outcome: Success > [2019-08-07 11:05:16][_][INFO] Response succeeded. > [2019-08-07 11:05:16][rocket::rocket][INFO] GET /api/sync?excludeDomains=true application/json: > [2019-08-07 11:05:16][_][INFO] Matched: GET /api/sync?<data..> (sync) > [2019-08-07 11:05:16][_][INFO] Outcome: Success > [2019-08-07 11:05:16][_][INFO] Response succeeded. > [2019-08-07 11:05:16][ws::io][INFO] Accepted a new tcp connection from 172.19.0.4:48578. > [2019-08-07 11:05:16][bitwarden_rs::api::notifications][INFO] Server got message '{"protocol":"messagepack","version":1}'. And Webinterface shows all passwords and organisations again. So in fact maybe really related to #494 ? Solved for the moment, but worth investigating more?

kerem commented 2026-03-03 01:28:24 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Aug 10, 2019):

The previous version you used was quite old. It's still strange that it was failing this way, but not sure how we can troubleshoot further unless you have some way to reproduce it again.

If it ever happens again, one thing worth trying is to log out the user, force-reload the interface (ctrl-shift-r) and log in again.

<!-- gh-comment-id:520178614 --> @mprasil commented on GitHub (Aug 10, 2019): The previous version you used was quite old. It's still strange that it was failing this way, but not sure how we can troubleshoot further unless you have some way to reproduce it again. If it ever happens again, one thing worth trying is to log out the user, force-reload the interface (ctrl-shift-r) and log in again.

kerem commented 2026-03-03 01:28:24 +03:00

Author

Owner

Copy link

@jamestutton commented on GitHub (Sep 5, 2019):

Can confirm I am experiencing a similar issue. In my case I created a new org owner and the downgraded the original owner to a "User" permissons didnt seem to update correctly so remove the user and readded and now they cant see the org at all. Will see if i can replicate in a test env and update.

<!-- gh-comment-id:528249927 --> @jamestutton commented on GitHub (Sep 5, 2019): Can confirm I am experiencing a similar issue. In my case I created a new org owner and the downgraded the original owner to a "User" permissons didnt seem to update correctly so remove the user and readded and now they cant see the org at all. Will see if i can replicate in a test env and update.

kerem commented 2026-03-03 01:28:24 +03:00

Author

Owner

Copy link

@jamestutton commented on GitHub (Sep 5, 2019):

Sorry not sure where this issue was coming from. Not able to recreate with current version. And when pointed the latest docker image at my original data the issue went away. So can only assume what ever was the cause has been fixed.

<!-- gh-comment-id:528271745 --> @jamestutton commented on GitHub (Sep 5, 2019): Sorry not sure where this issue was coming from. Not able to recreate with current version. And when pointed the latest docker image at my original data the issue went away. So can only assume what ever was the cause has been fixed.

kerem commented 2026-03-03 01:28:24 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Oct 11, 2019):

Closing this now, but feel free to reopen if you can find some way to reproduce the problem.

<!-- gh-comment-id:541003871 --> @mprasil commented on GitHub (Oct 11, 2019): Closing this now, but feel free to reopen if you can find some way to reproduce the problem.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels   

SSO

  

Third party

  

better for forum

  

bug

  

bug

  

documentation

  

duplicate

  

enhancement

  

future Vault

  

future Vault

  

future Vault

  

good first issue

  

help wanted

  

low priority

  

notes

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

troubleshooting

  

wontfix

No labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

question

troubleshooting

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vaultwarden#362

No description provided.