Quote from: NeuroticFish on October 16, 2021, 06:52:47 PM

( 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.}

Quote from: ranochigo on Today at 04:28:48 AM

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]}.

Quote from: ranochigo on Today at 04:28:48 AM

Are you running Bitcoin Core with listen=0?

Quote from: ETFbitcoin on Today at 09:41:50 AM

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.

Quote from: vv181 on Today at 05:07:48 AM

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?

Quote from: ETFbitcoin on Today at 09:41:50 AM

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?