Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to load database path after update #2413

Open
gccollect opened this issue Feb 3, 2024 · 4 comments
Open

Failed to load database path after update #2413

gccollect opened this issue Feb 3, 2024 · 4 comments

Comments

@gccollect
Copy link

gccollect commented Feb 3, 2024

Describe the bug
After upgrading Specter in umbrel to 2.0.2, my wallets no longer load properly with the error messages in the screenshot below. When l attach to the docker container, I see that there is no /data/.bitcoin folder, but I can still see the wallets json files in /data/wallets/main as well as a db.sqlite in /data/sqlite. Any chance I can recover the wallets and especially the labels associated with the addresses?

Screenshots
image

  • Where is your node running: umbrel
  • Where is your specter running: umbrel
  • Browser: Chrome
  • Specter Version: 2.0.2
@damanic
Copy link

damanic commented Jan 30, 2025

@gccollect

I have just run into the same issue.

Did you manage to find a solution?

@gccollect
Copy link
Author

Yes, I moved to a different wallet (Sparrow)

@damanic
Copy link

damanic commented Feb 3, 2025

For the searchers that may arrive here, my steps to resolve this issue:

  • Hit show details on the wallet that failed to load
  • Download the wallet file and check that your wallet info is all there
  • If all looks to be correct, hit Recreate the wallet

This basically rebuilds the wallet transaction data for the wallet in wallet file, and re-assigns all the data added by Specter (eg UTXO labels).

So really nothing was lost, only a reference to a database/cache file that can be 'recreated'.

@gccollect
Copy link
Author

gccollect commented Feb 3, 2025

It worked the first time I had this issue, then it broke again with the next update, and the "recreate the wallet" method wouldn't fix it any more. IMO, this app is too brittle, and I don't want a "move fast and break things" wallet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants