"Check Node" reports node is up, but "Node Status" says it isn't.

[Geremia]

Clicking the "Check Node" button on the bottom of the page reports that the node associated with this IP address is up; however, at the top of the page, "Node Status" says it isn't.

[ayeowch]

"Check Node" connects directly to your node since your IP is known. The "Node Status" page uses crawl data from the crawler which starts from a list of known nodes. It is possible your node is not well connected at the moment. Check how many peers you are connected to based on the getpeerinfo output.

[Geremia]

Yes, I have had very few incoming connections recently due to a router issue that brought the node down a few days ago. You're probably right that my node isn't well connected now.

[Geremia]

Well, it's been days now that the node has been up without interruption, yet the page still thinks it's down…

[ayeowch]

How many connections do you have now?

[Geremia]

It has about 3-4 inbound connections now and 732 MB sent.

[ayeowch]

That's an indication of the node not being well connected. Usually your node will be crawled within minutes once it has more than 8 peers. Another reason the crawler is not able to find you is due to change of IP if you are using dynamically allocated IP by your ISP.

[Geremia]

Does the node have to accept UDP packets? Currently, I'm only accepting TCP packets.

[ayeowch]

No. Only TCP is required.

[Geremia]

I'm running the node now on a different network (one even supporting IPv6), and I get the same issue.

I'm thinking it may have something to do with my running bitcoin-qt with a Tor proxy, although I am explicitly supplying the "--listen" flag to bitcoin-qt…

[Geremia]

Perhaps the network just doesn't have any need for another node in my area?

[ayeowch]

As long as the node has --listen and it is reachable by other peers, it should be on Bitnodes after being online for few minutes. Are you able to run your client without going Tor proxy to see if that makes it appear as UP on Bitnodes?

[Geremia]

It has appeared as up on Bitnodes even through Tor, when a couple IPv6 clients were connected to the node. Now, however, Bitnodes says it's down. Thus, going proxy through Tor or not doesn't seem to change things.

[Geremia]

It has appeared as up on Bitnodes even through Tor, when a couple IPv6 clients were connected to the node. Now, however, Bitnodes says it's down. Thus, going proxy through Tor or not doesn't seem to change things.

[Geremia]

It seems the Bitcoin network just isn't discovering my node (or perhaps it doesn't need it in my area?).

[ayeowch]

Whenever Bitnodes says DOWN, can you help check how many connections (inbound + outbound) do you have?

Also, it looks like you are behind dynamically allocated IP. Is that correct? If this is the case, it is possible your node changes its IP before it is able to establish itself among peers in the network.

[ayeowch]

The issue here may be related to bitcoin/bitcoin#48

[ayeowch]

Fixed with 802f3b6

[Geremia]

Well, today I have 8 incoming and 8 outgoing connections! I think it just took my node a few days of using the same IPv6 and IPv4 addresses before the network considered it stable.