<p>I am really confused. I am attempting to set up a listening node. When I look at bitnodes.earn.com it shows my node as <code>offline</code> when searching by IP, but when I run <code>getconnectioncount</code> it returns a positive number and getnetworkinfo returns</p>

<pre><code>{
  "version": 190001,
  "subversion": "/Satoshi:0.19.0.1/",
  "protocolversion": 70015,
  "localservices": "0000000000000409",
  "localservicesnames": [
  "NETWORK",
    "WITNESS",
    "NETWORK_LIMITED"
  ],
  "localrelay": true,
  "timeoffset": -13,
  "networkactive": true,
  "connections": 20,
  "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
    }
  ],
  "relayfee": 0.00001000,
  "incrementalfee": 0.00001000,
  "localaddresses": [
  ],
  "warnings": ""
}
</code></pre>

<p>What is going on? How can I tell if my node is actually accepting connections? Is this because I am still downloading the chain? All I am looking for it to rebroadcast/relay my transactions.</p>

CC BY-SA 4.0
2020-02-13T19:12:17.550Z
The `"reachable": true` config in both ipv4 and ipv6, as well as the >8 connection count leads me to believe you are indeed connected and port 8333 is open.
Septem151
CC BY-SA 4.0
2020-02-13T19:33:16.693Z
any idea why bitnodes.earn.com would say my node is unreachable?
danielsmith1789
CC BY-SA 4.0
2020-02-13T19:37:51.197Z
Bitnodes crawls the network hopping from node-to-node in order to paint a description of the network as a whole. The process in which Bitnodes uses is specific to their service, perhaps you could try reaching out to Bitnodes to see what the issue is. From a bitcoin core standpoint, you are receiving both inbound and outbound connections.
Septem151
<network><full-node>
How to tell if my node is online (conflicting information)
danielsmith1789
# How to tell if my node is online (conflicting information)

(Asked by: username_0 on 2020-02-13)

I am really confused. I am attempting to set up a listening node. When I look at bitnodes.earn.com it shows my node as `offline` when searching by IP, but when I run `getconnectioncount` it returns a positive number and getnetworkinfo returns

```
{
  "version": 190001,
  "subversion": "/Satoshi:0.19.0.1/",
  "protocolversion": 70015,
  "localservices": "0000000000000409",
  "localservicesnames": [
  "NETWORK",
    "WITNESS",
    "NETWORK_LIMITED"
  ],
  "localrelay": true,
  "timeoffset": -13,
  "networkactive": true,
  "connections": 20,
  "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
    }
  ],
  "relayfee": 0.00001000,
  "incrementalfee": 0.00001000,
  "localaddresses": [
  ],
  "warnings": ""
}

```

What is going on? How can I tell if my node is actually accepting connections? Is this because I am still downloading the chain? All I am looking for it to rebroadcast/relay my transactions.

**Tags:** network, full-node

> **Comments:**
> **username_1**: The `"reachable": true` config in both ipv4 and ipv6, as well as the >8 connection count leads me to believe you are indeed connected and port 8333 is open.  
> **username_0**: any idea why bitnodes.earn.com would say my node is unreachable?  
> **username_1**: Bitnodes crawls the network hopping from node-to-node in order to paint a description of the network as a whole. The process in which Bitnodes uses is specific to their service, perhaps you could try reaching out to Bitnodes to see what the issue is. From a bitcoin core standpoint, you are receiving both inbound and outbound connections.  

---

## 0 answers

