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

ORD wallet synchronization issue - "wallet failed to synchronize with ord server after 20 attempts" #4111

Open
AksharPrajapati03 opened this issue Nov 28, 2024 · 1 comment

Comments

@AksharPrajapati03
Copy link

I’ve set up Bitcoin Core and it’s running fine in the background. I’m using rpcusername and rpcpassword in bitcoin.conf (not using cookie). Bitcoin Core is working smoothly.

I followed the official GitHub documentation to set up the ORD wallet, and the server is running on port 8080 using the command:
ord server --http-port 8080

I created the wallet with:
ord wallet create

and received the mnemonic. However, when I attempt certain commands, I get the following error:

ubuntu@bitcoin-node-backend:~$ ord wallet --server-url http://0.0.0.0:8080 transactions 
error: wallet failed to synchronize with ord server after 20 attempts

Additionally, trying to dump the wallet results in:

ubuntu@bitcoin-node-backend:~$ ord wallet --server-url http://127.0.0.1:8080 dump 
error: wallet failed to synchronize with ord server after 20 attempts

Interestingly, some commands, such as checking the block count, work fine:

ubuntu@bitcoin-node-backend:~$ curl http://127.0.0.1:8080/blockcount 
819487

Additional Information:
I noticed that block indexing is still in progress, as indicated by the following status message:

ubuntu@bitcoin-node-backend:~$ ord server --http-port 8080
Index file `/home/ubuntu/.local/share/ord/index.redb` needs recovery. This can take a long time, especially for the --index-sats index.
██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████░░░░░░░░░ 825563/872280
Listening on http://0.0.0.0:8080
[indexing blocks] ███████████████████████████████████████████████████████████████████████████████████████████████████████████████░░░░░░░░░ 827176/872280

Should I wait until indexing finishes, or is there something else I should check? Any guidance would be appreciated!

@cryptoni9n
Copy link
Collaborator

Hi @AksharPrajapati03 - yes, wait until the index is finished and retry. If you continue to see these errors after the index is up to date, please post the commands that are erroring.

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