bitcoin core full node unreachable - no incoming connections?

[santoteracomputing]

  I am synced, says i have 8 connections, but i dont think port 8333 is reachable from outside?
  I made a Windows Firewall rule, I setup port forwarding on my router?
  Do I have to have a static IP address?

  TCP    192.168.1.114:49746    customer:8333          ESTABLISHED
  TCP    192.168.1.114:49747    customer:8333          ESTABLISHED
  TCP    192.168.1.114:49756    165.227.184.238:8333   ESTABLISHED
  TCP    192.168.1.114:49758    89.47.217.222:8333     ESTABLISHED
  TCP    192.168.1.114:50199    ec2-35-183-172-98:8333  ESTABLISHED
  TCP    192.168.1.114:50699    ie-in-f188:5228        ESTABLISHED
  TCP    192.168.1.114:51125    ec2-34-205-224-226:8333  ESTABLISHED
  TCP    192.168.1.114:51885    cpe-24-209-84-114:8333  ESTABLISHED

Your Public IPv4 is: 63.142.204.198
Your IPv6 is: Not Detected
Your Local IP is: 192.168.1.114
Location: Omak, WA US
ISP: Pcnuthut

[1714773543]

1714773543

[1714773543]

1714773543

[bob123]

 I am synced, says i have 8 connections, but i dont think port 8333 is reachable from outside?

That's correct.
I made a quick nmap scan:

Code:

Nmap scan report for 63.142.xxx.198
Host is up.

PORT     STATE    SERVICE
8333/tcp filtered bitcoin

Nmap done: 1 IP address (1 host up) scanned in 2.07 seconds

It says the port is filtered (by firewall, ISP, etc..). It is not reachable from outside of your local network.

  Do I have to have a static IP address?

No, you don't need a static IP. Port forwarding and a firewall rule (in case you have a FW running) should be enough.

Do you mind showing us the forwarding/firewall rule you set up ?

[NeuroticFish]

No, you don't need a static IP. Port forwarding and a firewall rule (in case you have a FW running) should be enough.

Actually if he has a router he may need static IP for the computer/laptop inside the local network (192.168.xxx.yyy or 10.0.xxx.yyy) so the port forwarding rule can "reach" his computer/laptop.

[bob123]

No, you don't need a static IP. Port forwarding and a firewall rule (in case you have a FW running) should be enough.

Actually if he has a router he may need static IP for the computer/laptop inside the local network (192.168.xxx.yyy or 10.0.xxx.yyy) so the port forwarding rule can "reach" his computer/laptop.

Oh, inside of the local network he obviously needs a static IP. Port forwarding / firewall won't work if his IP changes daily.

But usually your machine is getting the same IP each time logging in (via DHCP). But if this is not the case for OP, he definitely needs a static local IP.


What i meant (and what i understood) was whether he needs a static (public) IP address. They can be quite hard to get from an ISP (especially since IPv4 is more than scarce currently).
And a static public IP is not necessary.

[aleksej996]

You really should be running Linux if you want to setup your PC to be accessible from the Internet.

It is insecure to let your Windows machine open to the Internet and it is a lot harder to setup and troubleshoot.
Try setting up Linux if you are not in need of some specific Windows programs that are not available on Linux for that PC.

It isn't secure in general to use Windows with cryptocurrencies. It just makes you a profitable target for hacking.

[mikeywith]

do you mean LAN static ip ? yes you do, if you don't, when and if your PC is given a different IP address by your router then the router won't find it's way to transmit the packets to that static ip, unless it uses a hostname or mac address, so easiest way to go is, set up a static ip address for your pc outside of the dhcp range to avoid ip conflict


if you mean you need a WAN ip address, if you want your node to be reachable 24/7 then of course you need a public-static ip or you can use some dns-redirect server application,which will give you a sort of "domain name" that is always connected to your public ip even if it's changed.

------------------------------------

back to your problem, here are the possible issues

1- something went wrong with your firewall filters , the easiest way to troubleshoot this would be to disable your firewall for a while "while you are disconnected from the internet"

try to access the port from within the lan using another PC or another OS on a virtual machine, until you are able to do so, then the prime suspect is your firewall.

2- you messed up with your router, if you tell us what router are you using, or and how did you actually make the port forwarding, i should be able to tell you where your problem is exactly.

3-it's possible that you do not have a PUBLIC IP  , this ip "63.142.204.198" could be your ISP's ip and you are under it's sub-net, this is not very common but i have a local ISP here that does not provide you with a public ip, the whole ISP acts as a large LAN, the ip that shows on the WAN is a shared-ip which is my gateway, there is noway for anyone from outside the LAN to access my router as it will be blocked by my public ip which is not public on the WAN. you should ask your ISP if this is your IP or theirs.

i scanned all the ports on this ip "63.142.204.198" and nothing is opened.