-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Disconnected from peer: 127.0.0.1 #979
Comments
I also encountered this problem. Is there a solution? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On one machine, i installed a bitcoin latest version 0.17 (latest as of today, fully sync node), then i install bitcore 5.0.0 beta 44, and tried to get it talk to my bitcoind on localhost. i got the following error message
[2018-11-22T15:51:12.443Z] info: Starting fee
[2018-11-22T15:51:12.444Z] info: Starting web
[2018-11-22T15:51:12.458Z] info: Starting insight-api
[2018-11-22T15:51:12.459Z] info: localhost-insight-api subscribe: mempool/transaction total: 1
[2018-11-22T15:51:12.459Z] info: localhost-insight-api subscribe: block/block total: 1
[2018-11-22T15:51:12.459Z] info: Starting insight-ui
[2018-11-22T15:51:31.492Z] info: Bitcore Node ready
[2018-11-22T15:51:31.492Z] info: Connecting to p2p network.
[2018-11-22T15:51:31.554Z] info: Disconnected from peer: 127.0.0.1
[2018-11-22T15:51:36.549Z] info: Retrying connection to p2p network.
[2018-11-22T15:51:36.550Z] info: Disconnected from peer: 127.0.0.1
[2018-11-22T15:51:41.556Z] info: Retrying connection to p2p network.
[2018-11-22T15:51:41.558Z] info: Disconnected from peer: 127.0.0.1
This error messages keep going forever. I check the bitcore v5 code, the protocol version is 700015. i think this version is correct.
Also I didn't see any error message on my bitcoind side, perhaps because such connection rejection is not printed/written to debug.log.
Really run out of idea how to fix this issue, anyone care to help? Many thanks!!
The text was updated successfully, but these errors were encountered: