Core 20.0 node unreachable

[Csmiami]

I've been searching trough the archives, but I haven't found any (recent) solution to the problem I'm having.

This week, after a long break, I came back to the forum, and with that, I plugged my node back on. It did download the 12 weeks of blockchain with rather no issue, and I checked that port mapping had the 8333 port open to the node device. Now, upon checking some stuff on it, I have realized that there are no inboud connections, only 10 outbound, and the node is unreachable to bitnodes.

For what I've read, bitnodes is not an infalible website; but shouldn't I be getting at least 1 inboud connection? I've also checked the debug log and there is no single reference to inbound connections since I switched it on again

[Evgueni Leonov]

I'm having the same issue. More than a week ago I set up a full bitcoin node. It is synchronizing correctly, but it seems like its not reacheable from the internet

[LoyceV]

I'm having the same issue. More than a week ago I set up a full bitcoin node. It is synchronizing correctly, but it seems like its not reacheable from the internet

See Bitcoin.org - Running A Full Node: chances are your router doesn't allow inbound connections, unless you forward port 8333.

[simpleSliv3r]

I've been searching trough the archives, but I haven't found any (recent) solution to the problem I'm having.

This week, after a long break, I came back to the forum, and with that, I plugged my node back on. It did download the 12 weeks of blockchain with rather no issue, and I checked that port mapping had the 8333 port open to the node device. Now, upon checking some stuff on it, I have realized that there are no inboud connections, only 10 outbound, and the node is unreachable to bitnodes.

For what I've read, bitnodes is not an infalible website; but shouldn't I be getting at least 1 inboud connection? I've also checked the debug log and there is no single reference to inbound connections since I switched it on again

Hi I recommend you try to use telnet from the Internet and see if you can reach your node. See how to use it here: https://linux.die.net/man/1/telnet

[nc50lc]

I'm having the same issue. More than a week ago I set up a full bitcoin node. It is synchronizing correctly, but it seems like its not reacheable from the internet

If you're willing to enable UPnP in your router and in Bitcoin Core's setting or bitcoin.conf file, it should do the trick.
(What are the security implications of enabling UPnP in my home router?)

Different router models have different settings so you'll have to find it yourself, try Google search: UPnP <router model>.
You can enable UPnP in Bitcoin Core's GUI in "Settings->Options->Network->Map port using UPnP" or add a line upnp=1 in your bitcoin.conf file.

[NotATether]

I'm having the same issue. More than a week ago I set up a full bitcoin node. It is synchronizing correctly, but it seems like its not reacheable from the internet

See Bitcoin.org - Running A Full Node: chances are your router doesn't allow inbound connections, unless you forward port 8333.

Or you can enable uPnP in your router & OS followed by passing the -upnp option to Core, in case some ISP is messing with your port 8333 from outside in the internet.

[DaveF]

Also make sure you have the firewall open on the PC / RPi / whatever.
A lot of times the default settings will not let in traffic from off your local network so the PC / laptop you are testing in locally with is fine but anything off your local subnet gets blocked.

Somewhere along the line some settings even changed on some versions / configs of linux that local traffic passed but outside does not.
Not sure when that happened since I run a config script to set it up at build time but it's there on some distros.

-Dave