bitcore
bitcore copied to clipboard
bitpay
Trying to sync BTC regtest on latest master results in an endless loop of "Not connected to peer: 127.0.0.1:12345"
Couldn't find a template, so i'll just try and make this as informative as possible
When syncing BTC regtest, bitcore-node doesn't seem able to sync, and keeps on looping these entries in the log.
Bitcoin-core node side, in the debug.log, I was able to see all network messages go through (verack, ver, sendheaders, ping) with no issue, until the first getheaders is sent. Bitcore-node drops the connection, and the log reports that. On next connection, the same happens.
Here's the full log:
2020-12-22T18:40:37Z received: version (102 bytes) peer=0
2020-12-22T18:40:37Z sending version (103 bytes) peer=0
2020-12-22T18:40:37Z send version message: version 70016, blocks=12, us=[::]:0, peer=0
2020-12-22T18:40:37Z sending verack (0 bytes) peer=0
2020-12-22T18:40:37Z sending sendaddrv2 (0 bytes) peer=0
2020-12-22T18:40:37Z receive version message: /bitcore:8.23.1/: version 70001, blocks=0, us=[::]:0, peer=0
2020-12-22T18:40:37Z added time data, samples 2, offset +1 (+0 minutes)
2020-12-22T18:40:37Z sending alert (168 bytes) peer=0
2020-12-22T18:40:37Z received: verack (0 bytes) peer=0
2020-12-22T18:40:37Z sending ping (8 bytes) peer=0
2020-12-22T18:40:37Z AdvertiseLocal: advertising address [2002:570e:138b:0:4c18:586e:b50f:ff77]:12345
2020-12-22T18:40:37Z sending addr (31 bytes) peer=0
2020-12-22T18:40:37Z initial getheaders (11) to peer=0 (startheight:0)
2020-12-22T18:40:37Z sending getheaders (421 bytes) peer=0
2020-12-22T18:40:37Z socket recv error for peer=0: Connection reset by peer (104)
2020-12-22T18:40:37Z disconnecting peer=0
Reproducing this should be simple, here are my steps: In this repos root dir, run:
npm install && npm run node
My config for bitcore-node is this
"bitcoreNode": {
"chains": {
"BTC": {
"regtest": {
"chainSource": "p2p",
"trustedPeers": [
{
"host": "127.0.0.1",
"port": 12345
}
],
"rpc": {
"host": "127.0.0.1",
"port": 12234,
"username": "test",
"password": "test"
}
}
}
}
}
}
My bitcoin node was started with:
regtest=1
port=12345
rpcport=12234
rpcuser=test
rpcpassword=test
I'm under the impression the whole 8.23.x branch is flawed, but trying 8.22 didn't solve the issue for me, so i'm quite lost Any feedback is welcome
The original node is in my hand on a piece of paper the original wallet was never on the internet ever it was printed and the qms 820 Turbo printer was the internet connection only one person has the original node you cannot synchronize to it
The original node will be the 20% daily transactions every day.. if you want the node ... Ask nice 👽
@giaki3003 is your BTC node in regtest mode correctly? The icon is blue right?
You may need
[regtest]
port=12345
rpcport=12234
rpcuser=test
rpcpassword=test
The bitcoin.conf file format has changed a little since 0.17+
How long has this been going on may I ask?
On Dec 22, 2020 12:30 PM, "micahriggan" [email protected] wrote:
@giaki3003 https://github.com/giaki3003 is your BTC node in regtest mode correctly? The icon is blue right?
You may need
[regtest] port=12345 rpcport=12234 rpcuser=test rpcpassword=test
The bitcoin.conf file format has changed a little since 0.17+
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bitpay/bitcore/issues/3025#issuecomment-749761357, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANL7CUW3U67JUW3MQBZZMRLSWD6VXANCNFSM4VGAF5EQ .
@giaki3003 is your BTC node in regtest mode correctly? The icon is blue right?
You may need
[regtest] port=12345 rpcport=12234 rpcuser=test rpcpassword=testThe bitcoin.conf file format has changed a little since 0.17+
Yes, my bitcoin node is in regtest correctly, I also made a few blocks, and everything seems in order. I'm actually using 0.2x, and according to latest documentation here the [network] brackets should only be used to confine options to a certain network (I have no need for said functionality). Either way, adding or removing them has no effect on the issue i'm experiencing.