starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 09:46:00 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #407] Unable to login after one week #234

New issue
Closed
opened 2026-03-03 01:27:03 +03:00 by kerem · 5 comments
kerem commented 2026-03-03 01:27:03 +03:00
Owner
Copy link

Originally created by @Gilneus on GitHub (Feb 21, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/407

Hello,

I deployed bitwarden on AWS ECS about two weeks ago. First everything ran fine, I could use bitwarden without any problems. Since yesterday I have the problem that I can't log in anymore. Unfortunately I don't get a clear error message via the browser console. The error is "Error saving device". The whole call stack looks like this:

POST https://MYURL/identity/connect/token 400
(anonymous) @ polyfills.c8f35891102feaad9f9e.js:16
n.fetch @ main.c8f35891102feaad9f9e.js:1
(anonymous) @ main.c8f35891102feaad9f9e.js:1
(anonymous) @ main.c8f35891102feaad9f9e.js:1
(anonymous) @ main.c8f35891102feaad9f9e.js:1
(anonymous) @ main.c8f35891102feaad9f9e.js:1
t @ polyfills.c8f35891102feaad9f9e.js:16
t @ main.c8f35891102feaad9f9e.js:1
n.postIdentityToken @ main.c8f35891102feaad9f9e.js:1
(anonymous) @ main.c8f35891102feaad9f9e.js:1
(anonymous) @ main.c8f35891102feaad9f9e.js:1
(anonymous) @ main.c8f35891102feaad9f9e.js:1
r @ main.c8f35891102feaad9f9e.js:1
t.invoke @ polyfills.c8f35891102feaad9f9e.js:16
onInvoke @ vendor.c8f35891102feaad9f9e.js:200
t.invoke @ polyfills.c8f35891102feaad9f9e.js:16
e.run @ polyfills.c8f35891102feaad9f9e.js:16
(anonymous) @ polyfills.c8f35891102feaad9f9e.js:16
t.invokeTask @ polyfills.c8f35891102feaad9f9e.js:16
onInvokeTask @ vendor.c8f35891102feaad9f9e.js:200
t.invokeTask @ polyfills.c8f35891102feaad9f9e.js:16
e.runTask @ polyfills.c8f35891102feaad9f9e.js:16
d @ polyfills.c8f35891102feaad9f9e.js:16
e.invokeTask @ polyfills.c8f35891102feaad9f9e.js:16
m @ polyfills.c8f35891102feaad9f9e.js:39
b @ polyfills.c8f35891102feaad9f9e.js:39

Do any of you have any idea how I can fix this?

Originally created by @Gilneus on GitHub (Feb 21, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/407 Hello, I deployed bitwarden on AWS ECS about two weeks ago. First everything ran fine, I could use bitwarden without any problems. Since yesterday I have the problem that I can't log in anymore. Unfortunately I don't get a clear error message via the browser console. The error is "Error saving device". The whole call stack looks like this: ``` POST https://MYURL/identity/connect/token 400 (anonymous) @ polyfills.c8f35891102feaad9f9e.js:16 n.fetch @ main.c8f35891102feaad9f9e.js:1 (anonymous) @ main.c8f35891102feaad9f9e.js:1 (anonymous) @ main.c8f35891102feaad9f9e.js:1 (anonymous) @ main.c8f35891102feaad9f9e.js:1 (anonymous) @ main.c8f35891102feaad9f9e.js:1 t @ polyfills.c8f35891102feaad9f9e.js:16 t @ main.c8f35891102feaad9f9e.js:1 n.postIdentityToken @ main.c8f35891102feaad9f9e.js:1 (anonymous) @ main.c8f35891102feaad9f9e.js:1 (anonymous) @ main.c8f35891102feaad9f9e.js:1 (anonymous) @ main.c8f35891102feaad9f9e.js:1 r @ main.c8f35891102feaad9f9e.js:1 t.invoke @ polyfills.c8f35891102feaad9f9e.js:16 onInvoke @ vendor.c8f35891102feaad9f9e.js:200 t.invoke @ polyfills.c8f35891102feaad9f9e.js:16 e.run @ polyfills.c8f35891102feaad9f9e.js:16 (anonymous) @ polyfills.c8f35891102feaad9f9e.js:16 t.invokeTask @ polyfills.c8f35891102feaad9f9e.js:16 onInvokeTask @ vendor.c8f35891102feaad9f9e.js:200 t.invokeTask @ polyfills.c8f35891102feaad9f9e.js:16 e.runTask @ polyfills.c8f35891102feaad9f9e.js:16 d @ polyfills.c8f35891102feaad9f9e.js:16 e.invokeTask @ polyfills.c8f35891102feaad9f9e.js:16 m @ polyfills.c8f35891102feaad9f9e.js:39 b @ polyfills.c8f35891102feaad9f9e.js:39 ``` Do any of you have any idea how I can fix this?
kerem closed this issue 2026-03-03 01:27:03 +03:00
kerem commented 2026-03-03 01:27:04 +03:00
Author
Owner
Copy link

@Gilneus commented on GitHub (Feb 21, 2019):

I took a short view in the docker logs and found this:

[2019-02-21 08:40:54][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8:
[2019-02-21 08:40:54][_][INFO] Matched: POST /api/accounts/prelogin (prelogin)
[2019-02-21 08:40:54][_][INFO] Outcome: Success
[2019-02-21 08:40:54][_][INFO] Response succeeded.
[2019-02-21 08:40:54][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-02-21 08:40:54][_][INFO] Matched: POST /identity/connect/token (login)
[2019-02-21 08:40:55][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[0],"TwoFactorProviders2":{"0":null},"error":"invalid_grant","error_description":"Two factor required."}
[2019-02-21 08:40:55][_][INFO] Outcome: Success
[2019-02-21 08:40:55][_][INFO] Response succeeded.
[2019-02-21 08:41:03][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-02-21 08:41:03][_][INFO] Matched: POST /identity/connect/token (login)
[2019-02-21 08:41:08][bitwarden_rs::error][ERROR] Error saving device.
[CAUSE] DatabaseError(
    __Unknown,
    "database disk image is malformed"
)
<!-- gh-comment-id:465913278 --> @Gilneus commented on GitHub (Feb 21, 2019): I took a short view in the docker logs and found this: ``` [2019-02-21 08:40:54][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8: [2019-02-21 08:40:54][_][INFO] Matched: POST /api/accounts/prelogin (prelogin) [2019-02-21 08:40:54][_][INFO] Outcome: Success [2019-02-21 08:40:54][_][INFO] Response succeeded. [2019-02-21 08:40:54][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: [2019-02-21 08:40:54][_][INFO] Matched: POST /identity/connect/token (login) [2019-02-21 08:40:55][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[0],"TwoFactorProviders2":{"0":null},"error":"invalid_grant","error_description":"Two factor required."} [2019-02-21 08:40:55][_][INFO] Outcome: Success [2019-02-21 08:40:55][_][INFO] Response succeeded. [2019-02-21 08:41:03][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: [2019-02-21 08:41:03][_][INFO] Matched: POST /identity/connect/token (login) [2019-02-21 08:41:08][bitwarden_rs::error][ERROR] Error saving device. [CAUSE] DatabaseError( __Unknown, "database disk image is malformed" ) ```
kerem commented 2026-03-03 01:27:04 +03:00
Author
Owner
Copy link

@mprasil commented on GitHub (Feb 21, 2019):

That sounds as if the db file got corrupted. This is quite weird as sqlite tends to be quite resilient. Do you have any filesystem issues?

<!-- gh-comment-id:465917426 --> @mprasil commented on GitHub (Feb 21, 2019): That sounds as if the db file got corrupted. This is quite weird as sqlite tends to be quite resilient. Do you have any filesystem issues?
kerem commented 2026-03-03 01:27:04 +03:00
Author
Owner
Copy link

@Gilneus commented on GitHub (Feb 21, 2019):

I use an efs (nfs) under AWS to persit the file. I can imagine that access by two servers (autoscaling 2 instances of bitwarden) damaged the database file. Is there a way to recover the sqlite database

<!-- gh-comment-id:465919948 --> @Gilneus commented on GitHub (Feb 21, 2019): I use an efs (nfs) under AWS to persit the file. I can imagine that access by two servers (autoscaling 2 instances of bitwarden) damaged the database file. Is there a way to recover the sqlite database
kerem commented 2026-03-03 01:27:04 +03:00
Author
Owner
Copy link

@mprasil commented on GitHub (Feb 21, 2019):

Ah, yes, this was probably it. We use WAL, which does not work with networked filesystem. We have some info in the wiki regarding this. Generally speaking sqlite doesn't work well on NFS, I've seen multiple projects completely breaking with sqlite DB on NFS.

As for restoring the corrupted DB I personally think that you should just restore a backup if you have it. If not, try googling something about restoring corrupted sqlite DB. From my quick search it seems like the common approach is to dump the DB:

mv db.sqlite3 corrupted_db.sqlite3
echo ".dump" | sqlite corrupted_db.sqlite3 | sqlite db.sqlite3

Make sure to create backup of the corrupted DB before trying to fix it.

As for running on NFS in the future, I wouldn't recommend it, but if you do want that consider disabling WAL or make sure it never scales to more than one instance running. (the whole thing is going to be bottlenecked by the DB operations anyway, so there's no benefit in running more instances)

<!-- gh-comment-id:465947043 --> @mprasil commented on GitHub (Feb 21, 2019): Ah, yes, this was probably it. We use WAL, which does not work with networked filesystem. We have [some info in the wiki](https://github.com/dani-garcia/bitwarden_rs/wiki/Running-without-WAL-enabled) regarding this. Generally speaking sqlite doesn't work well on NFS, I've seen multiple projects completely breaking with sqlite DB on NFS. As for restoring the corrupted DB I personally think that you should just [restore a backup](https://github.com/dani-garcia/bitwarden_rs/wiki/Backing-up-your-vault) if you have it. If not, try googling something about restoring corrupted sqlite DB. From my quick search it seems like the common approach is to dump the DB: ```bash mv db.sqlite3 corrupted_db.sqlite3 echo ".dump" | sqlite corrupted_db.sqlite3 | sqlite db.sqlite3 ``` Make sure to create backup of the corrupted DB before trying to fix it. As for running on NFS in the future, I wouldn't recommend it, but if you do want that consider disabling WAL or make sure it never scales to more than one instance running. (the whole thing is going to be bottlenecked by the DB operations anyway, so there's no benefit in running more instances)
kerem commented 2026-03-03 01:27:04 +03:00
Author
Owner
Copy link

@mprasil commented on GitHub (Feb 22, 2019):

Hi @Gilneus, I'm going to close this as I don't think there's much we can do here. If you think we could improve something or add some documentation to avoid this, feel free to reopen.

<!-- gh-comment-id:466337060 --> @mprasil commented on GitHub (Feb 22, 2019): Hi @Gilneus, I'm going to close this as I don't think there's much we can do here. If you think we could improve something or add some documentation to avoid this, feel free to reopen.
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
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#234
No description provided.