-
Notifications
You must be signed in to change notification settings - Fork 49
Migration from bitwarden-ruby not working #63
Comments
The problem is with the location of database file. |
Yes, this solves the issue... Perhaps the migration script could take care of this automatically - or at least we should add a more prominent hint into the migration-documentation... I know that the new location is mentioned at the bottom of the migration-guide - but still, it was not clear enough for me to realize, that I need to manually adjust the paths... :-) |
That did solve the issue (thanks!). But now the syncing doesn't seem to work. I see the following exception in the logs -
|
I got this error too, but only on my chrome extension. The mobile app synced properly. Somehow the error went away on its own after a few restarts. You can try doing that a few times. |
Can you try the new migration script? You may want to delete the whole |
@jcs Thanks. The new migration script works. After this migration, the mobile app sync fine but the firefox extension doesn't. When I click on "Sync Vault Now", the extension shows an error message "Syncing failed", and the server logs contain the following exception -
I also tried restarting the server and the browser a few times as @tanshu suggested. But the problem still remains. |
That looks like your device record has no |
Awesome, this worked. Thanks! |
I tried to migrate from
bitwarden-ruby
this morning following the directions from https://github.com/jcs/rubywarden/blob/master/AR-MIGRATE.md .bundle --with migrate
worked without problems, after which I ran into the following exception.Not sure what I can do to fix this. Any help would be appreciated. Thank you!
The text was updated successfully, but these errors were encountered: