Not able to connect to external nodes

[sharath1101]

I have started two nodes. One is synced till block number 853759 and another is synced till block number 838999. After this point, I am not able to get any blocks.

I am running bitcoin core version 25.0 on linux

Here is my config

server=1
txindex=1

I enabled net debug and here is the log of my node1

2024-08-02T07:47:22Z [net:debug] trying connection 65.109.19.78:8333 lastseen=135.8hrs
2024-08-02T07:47:22Z [net] Added connection peer=276
2024-08-02T07:47:22Z [net] sending version (102 bytes) peer=276
2024-08-02T07:47:22Z [net] send version message: version 70016, blocks=853759, txrelay=1, peer=276
2024-08-02T07:47:29Z [net] socket no message in first 60 seconds, 0 1 peer=267
2024-08-02T07:47:29Z [net] disconnecting peer=267
2024-08-02T07:47:29Z [net] Cleared nodestate for peer=267
2024-08-02T07:47:29Z [net:debug] trying connection 47.198.60.180:8333 lastseen=114.0hrs
2024-08-02T07:47:29Z [net] Added connection peer=277
2024-08-02T07:47:29Z [net] sending version (102 bytes) peer=277
2024-08-02T07:47:29Z [net] send version message: version 70016, blocks=853759, txrelay=1, peer=277
2024-08-02T07:47:31Z [net] socket no message in first 60 seconds, 0 1 peer=268
2024-08-02T07:47:31Z [net] disconnecting peer=268
2024-08-02T07:47:31Z [net] Cleared nodestate for peer=268
2024-08-02T07:47:31Z [net:debug] trying connection 177.72.196.38:8333 lastseen=140.8hrs
2024-08-02T07:47:31Z [net] Added connection peer=278
2024-08-02T07:47:31Z [net] sending version (102 bytes) peer=278
2024-08-02T07:47:31Z [net] send version message: version 70016, blocks=853759, txrelay=0, peer=278
2024-08-02T07:47:32Z [net] socket no message in first 60 seconds, 0 1 peer=269
2024-08-02T07:47:32Z [net] disconnecting peer=269
2024-08-02T07:47:32Z [net] Cleared nodestate for peer=269
2024-08-02T07:47:32Z [net:debug] trying connection [2001:4091:a245:83de:4a21:bff:fe51:3d2d]:8333 lastseen=142.0hrs
2024-08-02T07:47:32Z [net] connect() to [2001:4091:a245:83de:4a21:bff:fe51:3d2d]:8333 failed: Network is unreachable (101)
2024-08-02T07:47:32Z [net:debug] trying connection [2001:0:9d38:6ab8:44:12e:9244:aa17]:8333 lastseen=117.3hrs
2024-08-02T07:47:32Z [net] connect() to [2001:0:9d38:6ab8:44:12e:9244:aa17]:8333 failed: Network is unreachable (101)
2024-08-02T07:47:33Z [net:debug] trying connection [2001:0:4137:9e76:340c:c36:aa19:b8bf]:8333 lastseen=82.9hrs
2024-08-02T07:47:33Z [net] connect() to [2001:0:4137:9e76:340c:c36:aa19:b8bf]:8333 failed: Network is unreachable (101)
2024-08-02T07:47:33Z [net:debug] trying connection 96.231.185.218:8333 lastseen=99.2hrs
2024-08-02T07:47:38Z [net] connection attempt to 96.231.185.218:8333 timed out
2024-08-02T07:47:39Z [net:debug] trying connection 76.71.203.61:8333 lastseen=139.4hrs
2024-08-02T07:47:41Z [net] socket no message in first 60 seconds, 0 1 peer=270
2024-08-02T07:47:41Z [net] disconnecting peer=270
2024-08-02T07:47:41Z [net] Cleared nodestate for peer=270
2024-08-02T07:47:44Z [net] connection attempt to 76.71.203.61:8333 timed out
2024-08-02T07:47:44Z [net:debug] trying connection 217.76.56.56:8333 lastseen=137.4hrs
2024-08-02T07:47:45Z [net] connect() to 217.76.56.56:8333 failed after wait: Connection refused (111)
2024-08-02T07:47:45Z [net:debug] trying connection 203.94.32.168:8333 lastseen=154.0hrs
2024-08-02T07:47:45Z [net] Added connection peer=279
2024-08-02T07:47:45Z [net] sending version (102 bytes) peer=279
2024-08-02T07:47:45Z [net] send version message: version 70016, blocks=853759, txrelay=1, peer=279
2024-08-02T07:47:46Z [net:debug] trying connection [2406:5900:100c:84ce:10b7:f67b:564f:6497]:8333 lastseen=128.7hrs
2024-08-02T07:47:46Z [net] connect() to [2406:5900:100c:84ce:10b7:f67b:564f:6497]:8333 failed: Network is unreachable (101)
2024-08-02T07:47:46Z [net:debug] trying connection 179.110.115.144:8333 lastseen=153.8hrs
2024-08-02T07:47:47Z [net] Added connection peer=280
2024-08-02T07:47:47Z [net] sending version (102 bytes) peer=280
2024-08-02T07:47:47Z [net] send version message: version 70016, blocks=853759, txrelay=0, peer=280
2024-08-02T07:47:47Z [net] Making feeler connection to 81.163.21.221:8333
2024-08-02T07:47:47Z [net:debug] trying connection 81.163.21.221:8333 lastseen=128.1hrs
2024-08-02T07:47:48Z [net] Added connection peer=281
2024-08-02T07:47:48Z [net] sending version (102 bytes) peer=281
2024-08-02T07:47:48Z [net] send version message: version 70016, blocks=853759, txrelay=0, peer=281

Log of node2. I didn't enable net debug here

2024-08-02T07:16:00Z txindex thread exit
2024-08-02T07:16:00Z loadblk thread start
2024-08-02T07:16:00Z Bound to 0.0.0.0:8333
2024-08-02T07:16:00Z torcontrol thread start
2024-08-02T07:16:00Z Bound to 127.0.0.1:8334
2024-08-02T07:16:00Z 0 block-relay-only anchors will be tried for connections.
2024-08-02T07:16:00Z init message: Starting network threads…
2024-08-02T07:16:00Z dnsseed thread start
2024-08-02T07:16:00Z net thread start
2024-08-02T07:16:00Z Loading addresses from DNS seed seed.bitcoin.wiz.biz.
2024-08-02T07:16:00Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2024-08-02T07:16:00Z loadblk thread exit
2024-08-02T07:16:00Z init message: Done loading
2024-08-02T07:16:00Z addcon thread start
2024-08-02T07:16:00Z msghand thread start
2024-08-02T07:16:00Z opencon thread start
2024-08-02T07:16:01Z Loading addresses from DNS seed seed.bitcoin.sipa.be.
2024-08-02T07:16:03Z Loading addresses from DNS seed seed.bitcoin.sprovoost.nl.
2024-08-02T07:16:03Z Loading addresses from DNS seed seed.bitcoinstats.com.
2024-08-02T07:16:03Z Loading addresses from DNS seed dnsseed.bluematt.me.
2024-08-02T07:16:03Z Loading addresses from DNS seed dnsseed.bitcoin.dashjr.org.
2024-08-02T07:16:04Z Loading addresses from DNS seed seed.bitcoin.jonasschnelli.ch.
2024-08-02T07:16:04Z Loading addresses from DNS seed dnsseed.emzy.de.
2024-08-02T07:16:05Z Loading addresses from DNS seed seed.btc.petertodd.org.
2024-08-02T07:16:06Z 219 addresses found from DNS seeds
2024-08-02T07:16:06Z dnsseed thread exit
2024-08-02T07:48:16Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1891 seconds ago)
2024-08-02T07:58:46Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2521 seconds ago)

I


Here is --netinfo of node1

Bitcoin Core client v25.0.0 - server 70016/Satoshi:25.0.0/

         ipv4    ipv6   total   block
in          0       0       0
out         9       0       9       1
total       9       0       9

Local addresses: n/a

And this is my getnetworkinfo

{
  "version": 250000,
  "subversion": "/Satoshi:25.0.0/",
  "protocolversion": 70016,
  "localservices": "0000000000000409",
  "localservicesnames": [
    "NETWORK",
    "WITNESS",
    "NETWORK_LIMITED"
  ],
  "localrelay": true,
  "timeoffset": 0,
  "networkactive": true,
  "connections": 11,
  "connections_in": 0,
  "connections_out": 11,
  "networks": [
    {
      "name": "ipv4",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "ipv6",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "onion",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "i2p",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    },

Please let me know if you have any suggestions.

[LoyceMobile]

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.

[sharath1101]

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.

Thanks. Yes, it is syncing now.

[nc50lc]

When weird things happen, -snip-

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.

[Cricktor]

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.