"Check Node" says 'Enter a valid IP address.' about bitnodes HOT 14 CLOSED

This is fixed now.

from bitnodes.

@tnull Should be good now.

from bitnodes.

@ratatosk9 Your IP should be reachable now from Bitnodes. It was in one of the excluded subnets.

from bitnodes.

Thanks, now I can see my node ^_^

from bitnodes.

I have the same problem, in this case with 130.149.80.221:8333.

from bitnodes.

I'm getting the same error on my ip address 192.168.0.121 Please help me also

from bitnodes.

@amplifysk The site can only check public IP addresses. 192.168.0.121 is a private IP address.

from bitnodes.

I have the same problem with my node. I have +20 peers connected to it but it won't show up on bitnode.
IP: 193.150.223.150.

from bitnodes.

@ayeowch Thank you! Have great week!

from bitnodes.

hello, pls check 150.129.237.71 - I show 8 active connections.

from bitnodes.

Hi, I have the same issue with ip 3.16.10.89

from bitnodes.

@ayeowch have been experiencing the same/similar issue since attempting to upgrade my Bitcoin Core full node from v0.17.0 to Bitcoin Core RPC client version v0.17.0.1 -- unsure if this is somehow an IP conflict (or excluded node, as stated above). The only changes I have made since the last successful check was the aforementioned version update. I receive this error when running the "Check Node" (port 8333) tool to check if your Bitcoin client is currently accepting incoming connections from other nodes. Pasting bitcoin-cli commands (and relevant output) below.

bitcoin-cli getblockcount: 555301

bitcoin-cli getnetworkinfo:

{
  "version": 170000,
  "subversion": "/Satoshi:0.17.0/",
  "protocolversion": 70015,
  "localservices": "000000000000040d",
  "localrelay": true,
  "timeoffset": 0,
  "networkactive": true,
  "connections": 51,
  "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": ""
}

bitcoin-cli getblockchaininfo:

{
  "chain": "main",
  "blocks": 555301,
  "headers": 555301,
  "bestblockhash": "000000000000000000232ce6552c839945d0b164b4f81b1ce9c2a57fac133f58",
  "difficulty": 5106422924659.822,
  "mediantime": 1545673543,
  "verificationprogress": 0.9999975297014476,
  "initialblockdownload": false,
  "chainwork": "00000000000000000000000000000000000000000479d62923ec5385ebe15fea",
  "size_on_disk": 223982050419,
  "pruned": false,
  "softforks": [
    {
      "id": "bip34",
      "version": 2,
      "reject": {
        "status": true
      }
    },
    {
      "id": "bip66",
      "version": 3,
      "reject": {
        "status": true
      }
    },
    {
      "id": "bip65",
      "version": 4,
      "reject": {
        "status": true
      }
    }
  ],
  "bip9_softforks": {
    "csv": {
      "status": "active",
      "startTime": 1462060800,
      "timeout": 1493596800,
      "since": 419328
    },
    "segwit": {
      "status": "active",
      "startTime": 1479168000,
      "timeout": 1510704000,
      "since": 481824
    }
  },
  "warnings": ""
}

This HTTP 404 error is what I'm presented with as of late when navigating to the URL to view my Bitcoin node's statistics:

Linux BTC 4.15.0-43-generic running on Ubuntu 18.04.1 LTS VM
Specs: 2 vCPUs, 4GB RAM, 500GB HDD

from bitnodes.

@cactuska Your IP should be reachable now from Bitnodes. It was in one of the excluded subnets.

@peatrick It's possible your IP is in one of the excluded subnets. Feel free to email me with your IP to have it removed from the exclusion list.

from bitnodes.

@peatrick It's possible your IP is in one of the excluded subnets. Feel free to email me with your IP to have it removed from the exclusion list.

Thank you kindly, @ayeowch. I'm not certain if you already went ahead and removed me from the exclusion list, or what, but things now appear to be working wonderfully, as they had been for the past 6+ months. Not sure what, or where I went wrong, but thank you kindly if you were responsible for remedying my little situation. Now able to report on my "Node Status" from the bitnodes.earn.com site once again. Happy holidays, sir.

from bitnodes.