starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Unable to login after restore DB on another docker host #348

New Issue
Closed
opened 2026-02-04 19:49:13 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 19:49:13 +03:00
Owner
Copy Link

Originally created by @evolsano on GitHub (Jul 19, 2019).

Hi,

I am trying to restore the bitwarden by replace existing db.sqlite3 with the backup.sqlite3 I have. But somehow it do not work and I cannot login to bitwarden after rename it.

Here are the scenarios,

  1. Create a new bitwarden container in host 2. Bitwarden is running behind traefik docker for reverse proxy.
  2. Copy backup.sqlite3 from host 1 to host 2 and renamed it to db.sqlite3.
  3. Host 1 domain is bitwarden.domain1.local, and host 2 is bitwarden.domain2.local. (These are example domains).
  4. Both docker host running on Ubuntu 18.04, docker-compose 1.23.1, and same docker-compose environment variables.
  5. Access to web vault, and login, but it prompt me incorrect username or password.
[2019-07-19 14:47:19][_][INFO] Matched: POST /identity/connect/token (login)
[2019-07-19 14:47:19][bitwarden_rs::error][ERROR] Username or password is incorrect. Try again. IP: x.x.x.y. Username: xxx@example.com.
[2019-07-19 14:47:19][_][INFO] Outcome: Success
[2019-07-19 14:47:19][_][INFO] Response succeeded.

Failed to add new user.

[2019-07-19 14:47:19][_][INFO] Response succeeded.
[2019-07-19 14:53:30][rocket::rocket][INFO] POST /api/accounts/register application/json; charset=utf-8:
[2019-07-19 14:53:30][_][INFO] Matched: POST /api/accounts/register (register)
[2019-07-19 14:53:30][bitwarden_rs::error][ERROR] Error saving user.
[CAUSE] DatabaseError(
    __Unknown,
    "table users has no column named key",

If I restore create a new container in host 1, and restore the DB, everything works well. The backup.sqlite3 copied to host 2 should not corrupt and it has the same md5 hash to the source.

Can someone enlighten me how can I restore it on another docker host?

Originally created by @evolsano on GitHub (Jul 19, 2019). Hi, I am trying to restore the bitwarden by replace existing db.sqlite3 with the backup.sqlite3 I have. But somehow it do not work and I cannot login to bitwarden after rename it. Here are the scenarios, 1. Create a new bitwarden container in host 2. Bitwarden is running behind traefik docker for reverse proxy. 2. Copy backup.sqlite3 from host 1 to host 2 and renamed it to db.sqlite3. 3. Host 1 domain is bitwarden.domain1.local, and host 2 is bitwarden.domain2.local. (These are example domains). 4. Both docker host running on Ubuntu 18.04, docker-compose 1.23.1, and same docker-compose environment variables. 5. Access to web vault, and login, but it prompt me incorrect username or password. ``` [2019-07-19 14:47:19][_][INFO] Matched: POST /identity/connect/token (login) [2019-07-19 14:47:19][bitwarden_rs::error][ERROR] Username or password is incorrect. Try again. IP: x.x.x.y. Username: xxx@example.com. [2019-07-19 14:47:19][_][INFO] Outcome: Success [2019-07-19 14:47:19][_][INFO] Response succeeded. ``` Failed to add new user. ``` [2019-07-19 14:47:19][_][INFO] Response succeeded. [2019-07-19 14:53:30][rocket::rocket][INFO] POST /api/accounts/register application/json; charset=utf-8: [2019-07-19 14:53:30][_][INFO] Matched: POST /api/accounts/register (register) [2019-07-19 14:53:30][bitwarden_rs::error][ERROR] Error saving user. [CAUSE] DatabaseError( __Unknown, "table users has no column named key", ``` If I restore create a new container in host 1, and restore the DB, everything works well. The backup.sqlite3 copied to host 2 should not corrupt and it has the same md5 hash to the source. Can someone enlighten me how can I restore it on another docker host?
OVERLORD commented 2026-02-04 19:49:42 +03:00
Author
Owner
Copy Link

@evolsano commented on GitHub (Jul 19, 2019):

Issue resolved after update to latest docker image.
Please ignore my stupidity and I wasted half day to troubleshoot it.

@evolsano commented on GitHub (Jul 19, 2019): Issue resolved after update to latest docker image. Please ignore my stupidity and I wasted half day to troubleshoot it.
OVERLORD commented 2026-02-04 19:49:50 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Jul 19, 2019):

Well you figured it out and now you know better, so no stupidity as far as I can see. You used older image with newer DB, if it was the other way around, it would work because bitwarden_rs would automatically upgrade the DB. I wonder if we could detect your case and refuse to start with clear message indicating the DB is ahead of program version.

@mprasil commented on GitHub (Jul 19, 2019): Well you figured it out and now you know better, so no stupidity as far as I can see. You used older image with newer DB, if it was the other way around, it would work because bitwarden_rs would automatically upgrade the DB. I wonder if we could detect your case and refuse to start with clear message indicating the DB is ahead of program version.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#348
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?