Can't connect to external nodes

4 replies 280 views
Posts: 8 · Reputation: 79
#1Jun 9, 2023, 08:21 PM
I set up two nodes. One's all good up to block 853759, while the other is at 838999. After that, no new blocks are coming in. I'm using bitcoin core version 25.0 on linux. Here’s my config. I turned on net debug for node1 and here’s its log. For node2, I didn't enable net debug, so no log there. Here's the netinfo for node1. And this is what I got from getnetworkinfo. Any thoughts or suggestions? Let me know.
6 Reply Quote Share
degen_apeMember
Posts: 28 · Reputation: 231
#2Jun 9, 2023, 09:51 PM
When weird things happen, I'd start by upgrading to the latest version. I doubt it helps in this case, but it's a quick check.
4 Reply Quote Share
Posts: 8 · Reputation: 79
#3Jun 9, 2023, 10:28 PM
Thanks. Yes, it is syncing now.
2 Reply Quote Share
gr3g.0rbitHero Member
Posts: 1025 · Reputation: 2646
#4Jun 10, 2023, 03:27 AM
Weird indeed. The major difference in his version and the latest is the utilization of "P2P_V2" protocol by default. but his node should still be able to connect (outbound) to P2P_V2 nodes which can be seen in his getnetworkinfo result which contradicts the topic title. Perhaps it was something else, (the logs are incomplete) But it's great that he upgraded to the latest version to gain the benefits of BIP324 plus it somehow solved the issue.
0 Reply Quote Share
im_lynxHero Member
Posts: 515 · Reputation: 2161
#5Jun 12, 2023, 02:23 AM
Because OP isn't verbose about it, just to be sure: your two nodes run on different Linux boxes or if on one Linux box, the two nodes don't share directories with each other. (From the incomplete logs, it doesn't look like they share something which would cause issues that Core would've spitted out. But incomplete logs don't tell the whole story and guesswork is clumsy.) Edit: Oh, nevermind, I somehow read over OP's post that his nodes are syncing fine.
1 Reply Quote Share

Related topics