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.

Sign up for GitHub

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

Jump to bottom

[Error: Bitcoin Core JSON-RPC: host=127.0.0.1 port=8332: Request Error: connect EADDRNOTAVAIL] #85

Closed
ser opened this issue Jul 25, 2015 · 2 comments · May be fixed by Matthelonianxl/bitcore-node#4, takeratta/bitcore-node#9, agustinkassis/bitcore-node#3, Matthelonianxl/bitcore-node#32 or agustinkassis/bitcore-node#31
Closed

[Error: Bitcoin Core JSON-RPC: host=127.0.0.1 port=8332: Request Error: connect EADDRNOTAVAIL] #85

ser opened this issue Jul 25, 2015 · 2 comments · May be fixed by Matthelonianxl/bitcore-node#4, takeratta/bitcore-node#9, agustinkassis/bitcore-node#3, Matthelonianxl/bitcore-node#32 or agustinkassis/bitcore-node#31

Comments

@ser
Copy link

ser commented Jul 25, 2015

During syncing, after a while, I am getting:

[Error: Bitcoin Core JSON-RPC: host=127.0.0.1 port=8332: Request Error: connect EADDRNOTAVAIL]
network monitor disconnected

and syncing is being stopped, indeed. How can I convince bitcore-node to restore the connection without shutting down and starting it again?
@braydonf
Copy link
Contributor

Hi @ser, we're working on running Bitcoin Core within the same Node.js process ( #57 ) with bitcoind.js. In that case, connecting via JSON-RPC isn't needed for syncing, getting blocks is around 20 times faster, and should resolve issues such as these.

@braydonf
Copy link
Contributor

The master branch now includes Bitcoin Core running within the same process.

This was referenced Jan 21, 2020
Open
Open
Open
@snyk-bot snyk-bot mentioned this issue Oct 9, 2020
Merged
@Matthelonianxl Matthelonianxl mentioned this issue Nov 26, 2023
Open
@agustinkassis agustinkassis mentioned this issue Nov 27, 2023
Open
@takeratta takeratta mentioned this issue Nov 28, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@ser @braydonf