Can't get inbound connections on Bitcoin Core! [Solved]

[SFR10]

After it got fully synched, I went to the information tab to see if finally there's an inbound connection; unfortunately, nothing changed while there are 10 outbound connections!

I've already tried the following things, but bitnodes still says "unreachable":

• Opened port 8333 ^{[both TCP and UDP]} on my router page.
• Added inbound rule for port 8333 on "Windows Defender Firewall with Advanced Security".
• A VPN connection with a static IP address.
• "Allow incoming connections" is checked ^{[bitcoin core]}.

Client version: v22.0
Windows: 10

Is there anything else that I could try?

Update:

I found a workaround of some sort and I'll probably stick with it for the time being ^{[credit goes to "this video"]}:
^{Note: It doesn't work with a VPN connection [if you try it, you need to restart your windows to get it back to work].}

• Steps:
  
  • Download uTorrent
  • Option > Preferences > Connections > Listening Port > 8333 > Apply > Ok.
  • Keep it open!

Update 2 ^[solution]:

I forgot if UPnP is turned on by default, and I'm assuming the torrent client uses it to open the port. Can you go to Settings>Options>Network and check Map port using UPnP?

[1715215446]

1715215446

[1715215446]

1715215446

[1715215446]

1715215446

[1715215446]

1715215446

[1715215446]

1715215446

[NeuroticFish]

Is there anything else that I could try?

( I don't know how the VPN helps/works there, hence: ) Is the router forwarding 8333 to the windows 10 IP?

[ranochigo]

Running a VPN and portforwarding your router does nothing, traffic is routed through your VPN and not your router. Go to canyouseeme.org and check if your port 8333 is reachable from the outside. Are you running Bitcoin Core with listen=0?

[vv181]

• A VPN connection with a static IP address.

I believe if you are using VPN, then you must use remote port forwarding. The port that comes from the VPN service is different from the default listening port, so you must manually set the config to that particular port. Anyway, AFAIK, even if you did that, other nodes will not prioritize making a connection to you since you did not use the default port.

About your whole issue, I don't actually know how it works, but I don't know if a brand new node immediately gets an inbound connection. My Tor only nodes only get an inbound connection after I leave it ~20days, after that, I also can verify it on Bitnodes.

[ABCbits]

• A VPN connection with a static IP address.

Does your VPN (or your VPN plan) allow port forwarding?

Are you running Bitcoin Core with listen=0?

It should be listen=1 since OP mentioned he checked "Allow incoming connections", unless it's override by listen=0 on bitcoin.conf or parameter when opening Bitcoin Core.

[SFR10]

( I don't know how the VPN helps/works there, hence: ) Is the router forwarding 8333 to the windows 10 IP?

I used it because of the static IP address ^{[someone mentioned it in either one of the threads here or on the "Bitcoin Stack Exchange"]}.
^{- Apparently, I had the wrong idea.}

Running a VPN and portforwarding your router does nothing, traffic is routed through your VPN and not your router. Go to canyouseeme.org and check if your port 8333 is reachable from the outside.

I checked ^{[with my real IP and I've already repeated the first two steps that I've listed before]} and it gave an error ^{[on bitnode is still unreachable]}.

Are you running Bitcoin Core with listen=0?

It should be listen=1 since OP mentioned he checked "Allow incoming connections", unless it's override by listen=0 on bitcoin.conf or parameter when opening Bitcoin Core.

I believe that means disabling it ^["=0"] and it appears that it has something to do with Tor users using it, am I right? I'm using the default settings and judging by @nc50lc's comment, it seems there's no need for me to add it.

My Tor only nodes only get an inbound connection after I leave it ~20days, after that, I also can verify it on Bitnodes.

That's interesting and weird at the same time! Can someone else confirm if all of the Tor-only nodes act like this?

Does your VPN (or your VPN plan) allow port forwarding?

Unfortunately, "it doesn't".
I've already tried everything that I knew and others suggested but it's still pretty much the same...

• CMIIW: If I continue to run it in its current state, I'm still contributing by verifying and connecting to others while other nodes just can't connect to me. Am I right?

[ABCbits]

Are you running Bitcoin Core with listen=0?

It should be listen=1 since OP mentioned he checked "Allow incoming connections", unless it's override by listen=0 on bitcoin.conf or parameter when opening Bitcoin Core.

I believe that means disabling it ^["=0"] and it appears that it has something to do with Tor users using it, am I right? I'm using the default settings and judging by @nc50lc's comment, it seems there's no need for me to add it.

AFAIK it's not related with Tor usage or Tor user. But @nc50lc is right, you don't need to add listen=0.

• CMIIW: If I continue to run it in its current state, I'm still contributing by verifying and connecting to others while other nodes just can't connect to me. Am I right?

Correct.

[ranochigo]

I checked ^{[with my real IP and I've already repeated the first two steps that I've listed before]} and it gave an error ^{[on bitnode is still unreachable]}.

If you're running through a VPN, then you should check with your VPN. Are there any steps to enable portforwarding using your VPN? If canyouseeme.org shows false, then the problem is with your portforwarding and not Core.

I believe that means disabling it ^["=0"] and it appears that it has something to do with Tor users using it, am I right? I'm using the default settings and judging by @nc50lc's comment, it seems there's no need for me to add it.

Yup. The setting is only disabled if you're running a proxy or through Tor. I was asking that on the premise that you might have specified that, given that it is turned on by default.

CMIIW: If I continue to run it in its current state, I'm still contributing by verifying and connecting to others while other nodes just can't connect to me. Am I right?

This is correct. It is good to be able to have inbound connection, for the network but it doesn't necessarily mean that you're not contributing to the network. Even if you do enable inbound connection, then the primary benefits should fall on you and the overall benefits on the network is secondary.

[SFR10]

But @nc50lc is right, you don't need to add listen=0.
~Snipped~
Correct.

Yup. The setting is only disabled if you're running a proxy or through Tor.
~Snipped~
This is correct. It is good to be able to have inbound connection, for the network but it doesn't necessarily mean that you're not contributing to the network. Even if you do enable inbound connection, then the primary benefits should fall on you and the overall benefits on the network is secondary.

Thank you for all of the above confirmations ^{[I appreciate it]}

Are there any steps to enable portforwarding using your VPN?

Unfortunately, "there's none".

If canyouseeme.org shows false, then the problem is with your portforwarding and not Core.

You're right... I found a workaround of some sort and I'll probably stick with it for the time being ^{[credit goes to "this video"]}:
^{Note: It doesn't work with a VPN connection [if you try it, you need to restart your windows to get it back to work].}

• Steps:
  
  • Download uTorrent
  • Option > Preferences > Connections > Listening Port > 8333 > Apply > Ok.
  • Keep it open!

I'll keep the thread open for now ^{[hopefully, there are still a few other things/solutions to try]}.

[ranochigo]

You're right... I found a workaround of some sort and I'll probably stick with it for the time being ^{[credit goes to "this video"]}

I forgot if UPnP is turned on by default, and I'm assuming the torrent client uses it to open the port. Can you go to Settings>Options>Network and check Map port using UPnP?

[SFR10]

1. I would recommend you to use qBitTorrent since it's open source and doesn't have ads.

I preferred that one as well, but I keep getting inconsistent results ^{[not sure why]} with zero inbound connections:

• Bitnode = Unreachable
• Other port checking websites = Open/success

2. Can you download/upload something on uTorrent when Bitcoin Core has incoming connection?

Yes, there's no issue with doing those at the same time: Screenshot

I forgot if UPnP is turned on by default, and I'm assuming the torrent client uses it to open the port. Can you go to Settings>Options>Network and check Map port using UPnP?

It wasn't turned on by default, but that did the trick ^{[thank you so much]}
- Can someone merit his/her post on my behalf (I have no sMerits).
I'll lock the thread in 24 hrs.

Update:
/locked