mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Error saving device on postgresql #1273
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 @jz8132543 on GitHub (May 24, 2022).
I failed to login on all clients(web, Android, ios and etc). I'm running version 2.25.1 of Vaultwarden/server in docker, using postgresql14. I accidentally restarted postgresql and then can't log into my account. The log is as follows.
The devices table in postgresql has been emptied, but such an error still occurs. How to fix or how to migrate data to other database types like SQLite or MySQL?
@BlackDex commented on GitHub (May 24, 2022):
Could you post the generated support string please. That would be really helpful.
@BlackDex commented on GitHub (May 24, 2022):
Also, if you still see v2.25.1 as your web-vault version, you are not on the latest version.
I would make sure you are using the latest version. Since it seems to work for me just fine using Postgresql.
So, posting the Support String would be helpful.
@jz8132543 commented on GitHub (May 27, 2022):
Thanks for your reply! It works after I update my docker container. It is a weird issue but I'm so glad it was solved after update.
@Bluscream commented on GitHub (Mar 28, 2024):
I have a similar error:
@BlackDex commented on GitHub (Mar 28, 2024):
@Bluscream that looks more like a PostgreSQL issue that it isn't able to store data. Check the storage or logs of the database.
@Bluscream commented on GitHub (Mar 28, 2024):
i am using the rpi portainer install with no special database (https://github.com/pi-hosted/pi-hosted/blob/master/template/apps/vaultwarden.json)
disk space seems not critical to me:
container stats also look fine to me

@BlackDex commented on GitHub (Mar 28, 2024):
Then your issues is misplaced in this topic.
Still remains a database storage issue.
I suggest to open a topic in the Q&A discussion and post your support string which you can generate via the admin diagnostics page.