[GH-ISSUE #1152] Lost passwords after sqlite->mysql migration #812

New issue

Closed

opened 2026-03-03 02:03:29 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 02:03:29 +03:00

Owner

Originally created by @francescocarzaniga on GitHub (Sep 23, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1152

Subject of the issue

I have migrated my bitwarden_rs instance from docker to compiled binary and with it also the database from sqlite to mysql, and now usernames/passwords are not visible anymore. The items are present, as well as the collections and organisations, but under each item password and username are no longer there. Weirdly enough secure notes are intact. I can add new items and sync them as well, so the problem is probably not the binary.

Your environment

Bitwarden_rs version: 1.16.3

Install method: previously docker, now compiled from source
Clients used: all
Reverse proxy and version: nginx
Version of mysql/postgresql: previously sqlite3, now mysql 5.7
Other relevant information:

Steps to reproduce

Migrate from sqlite to mysql using the guide. Ensure the ciphers table is intact and contains all the elements in mysql.

Expected behaviour

Everything works as before.

Actual behaviour

Usernames and passwords are no longer available.

Relevant logs

Sadly the logs are not interesting, even in trace mode.

Originally created by @francescocarzaniga on GitHub (Sep 23, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1152  ### Subject of the issue I have migrated my bitwarden_rs instance from docker to compiled binary and with it also the database from sqlite to mysql, and now usernames/passwords are not visible anymore. The items are present, as well as the collections and organisations, but under each item password and username are no longer there. Weirdly enough secure notes are intact. I can add new items and sync them as well, so the problem is probably not the binary. ### Your environment  * Bitwarden_rs version: 1.16.3  * Install method: previously docker, now compiled from source * Clients used: all * Reverse proxy and version: nginx * Version of mysql/postgresql: previously sqlite3, now mysql 5.7 * Other relevant information: ### Steps to reproduce  Migrate from sqlite to mysql using the guide. Ensure the ciphers table is intact and contains all the elements in mysql. ### Expected behaviour  Everything works as before. ### Actual behaviour  Usernames and passwords are no longer available. ### Relevant logs  Sadly the logs are not interesting, even in trace mode.

kerem closed this issue

2026-03-03 02:03:29 +03:00

kerem commented

2026-03-03 02:03:30 +03:00

Author

Owner

@BlackDex commented on GitHub (Sep 23, 2020):

Hello @francescocarzaniga

I have updated the wiki ( https://github.com/dani-garcia/bitwarden_rs/wiki/Using-the-MySQL-Backend ) which will probably fix your issue.

I think the Foreign-Keys were causing some issues, which i now added into the script.
Also, i have tested this my self on a MariaDB v10.5.4 which worked as a charm!

Also, please keep in mind that this not something we can fully support, any loss to data is not something we can be responsible for. Always make backups!

@BlackDex commented on GitHub (Sep 23, 2020): Hello @francescocarzaniga I have updated the wiki ( https://github.com/dani-garcia/bitwarden_rs/wiki/Using-the-MySQL-Backend ) which will probably fix your issue. I think the Foreign-Keys were causing some issues, which i now added into the script. Also, i have tested this my self on a MariaDB v10.5.4 which worked as a charm! Also, please keep in mind that this not something we can fully support, any loss to data is not something we can be responsible for. Always make backups!

kerem commented

2026-03-03 02:03:30 +03:00

Author

Owner

@francescocarzaniga commented on GitHub (Sep 23, 2020):

That was lighting fast! Indeed foreign keys were the problem, everything's working fine now.

Also, please keep in mind that this not something we can fully support, any loss to data is not something we can be responsible for. Always make backups!

Of course, I was only testing the new instance. Databases are not something I like to mess with.

@francescocarzaniga commented on GitHub (Sep 23, 2020): That was lighting fast! Indeed foreign keys were the problem, everything's working fine now. > Also, please keep in mind that this not something we can fully support, any loss to data is not something we can be responsible for. Always make backups! Of course, I was only testing the new instance. Databases are not something I like to mess with.

kerem referenced this issue

2026-03-03 08:53:09 +03:00

[PR #812] [MERGED] Fixes #635 - Unique constraint violation when using U2F tokens on PostgreSQL #2806