[GH-ISSUE #2548] Getting db errors during migration from 1.24 to 1.25 #1301

New issue

Closed

opened 2026-03-03 02:08:01 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 02:08:01 +03:00

Owner

Originally created by @ericlau-solid on GitHub (Jun 10, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2548

Getting the following errors:

I am completely stuck. The performance issues I had in 1.24 are back, so I tried to upgrade, and now upgrade is stuck, so I have no way of getting bitwarden server back up. Anything I can do? Devices new user seems interesting, but not sure what I can do.

Originally created by @ericlau-solid on GitHub (Jun 10, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2548 Getting the following errors: ![image](https://user-images.githubusercontent.com/8011182/172973856-ee10eba3-87dd-4135-9a8f-623b7832d090.png) I am completely stuck. The performance issues I had in 1.24 are back, so I tried to upgrade, and now upgrade is stuck, so I have no way of getting bitwarden server back up. Anything I can do? Devices new user seems interesting, but not sure what I can do.

kerem closed this issue

2026-03-03 02:08:01 +03:00

kerem commented

2026-03-03 02:08:02 +03:00

Author

Owner

@BlackDex commented on GitHub (Jun 10, 2022):

I suggest to check this comment https://github.com/dani-garcia/vaultwarden/issues/2504#issuecomment-1140281453

In short, run the 1.24.0 version, login into the admin interface, Deauthorize sessions of all users, then upgrade to 1.25.0.

But, first backup the database, just in case.

@BlackDex commented on GitHub (Jun 10, 2022): I suggest to check this comment https://github.com/dani-garcia/vaultwarden/issues/2504#issuecomment-1140281453 In short, run the 1.24.0 version, login into the admin interface, Deauthorize sessions of all users, then upgrade to 1.25.0. But, first backup the database, just in case.

kerem commented

2026-03-03 02:08:02 +03:00

Author

Owner

@aquanow-eric commented on GitHub (Jun 13, 2022):

I see. I didn't try that. Instead I exported to unencrypted JSON all the vaults out of 1.24, install clean 1.25, and import them. I find that JSON encrypted didn't work even though I didn't change the pwd.

At any event this did the trick. I also resolved write performance issues I had earlier as well. So all good.

@aquanow-eric commented on GitHub (Jun 13, 2022): I see. I didn't try that. Instead I exported to unencrypted JSON all the vaults out of 1.24, install clean 1.25, and import them. I find that JSON encrypted didn't work even though I didn't change the pwd. At any event this did the trick. I also resolved write performance issues I had earlier as well. So all good.

kerem commented

2026-03-03 02:08:02 +03:00

Author

Owner

@aquanow-eric commented on GitHub (Jun 13, 2022):

We can consider this issue closed.

@aquanow-eric commented on GitHub (Jun 13, 2022): We can consider this issue closed.