|
Title: solved Post by: TheBitcoinBadger on August 30, 2018, 02:08:51 PM solved
Title: Re: 14 connections but node "not reachable"? Whats the cause of this? Post by: Foxpup on August 30, 2018, 02:22:51 PM Bitnodes is not always accurate. If you have any incoming connections at all from other nodes, you are reachable. You can verify that the port is open by trying to connect to it from an outside machine (even just with telnet or something; you don't need another Bitcoin node for this).
Title: Re: 14 connections but node "not reachable"? Whats the cause of this? Post by: bob123 on August 30, 2018, 02:32:07 PM Do you have the 'Allow Incoming connections' box ticked in the settings of core ?
Outgoing and incoming connections are seperated. You need to allow incoming connections to be reachable from outside of your home network. There are several sites available online which can check whether your machine is reachable on specific ports. You may try this out. It takes half a minute and you know whether your machine is reachable. Title: Re: 14 connections but node "not reachable"? Whats the cause of this? Post by: jackg on August 30, 2018, 08:25:11 PM Hello Bitcoiners, i run a full node with 14 connections at the moment, so i share the blockchain to other peers. port forwarding in the router is enabled. Total connections is a bit of a useless figure. Usually this would happen that it doesn't show up on bitnodes due to bitnodes being faulty or the port not being opened. Also, if your core sin't synced, there will be no incoming connections? Is there a bar at the bottom that says you're a certain amount of time behind (few years/months)? Title: Re: 14 connections but node "not reachable"? Whats the cause of this? Post by: TheBitcoinBadger on September 01, 2018, 11:44:40 AM thx for your replies. at this point, i think bitnodes API is shit.
if something changes, i will post here. Title: Re: 14 connections but node "not reachable"? Whats the cause of this? Post by: DaveF on September 02, 2018, 08:53:42 PM You can cheat a bit.
Install the client on another machine outside your network. Start the sync, then from the console do an addnode and give it your IP/Port or you can add it in your bitcoin.conf file. Then do a getpeerinfo and see if you see it. -Dave Title: Re: 14 connections but node "not reachable"? Whats the cause of this? Post by: ranochigo on September 03, 2018, 01:42:04 AM Go to canyouseeme.org and check if your port is open.
Are you behind any proxy/VPN for your browser and your Bitcoin Core? Bitnodes tests the connection using your IP that they get when you visit the page. If you're behind a proxy or VPN, they would end up testing the wrong IP. |