bitcoin core – Listening Node behind CG-NAT

My router is behind a CG-NAT protocol.

I believe this given my WAN IP and my public IP are totally different.

This prevents me from operating a full listening node provided that my public IP shouldn’t be uniquely figuring out me.

In consequence exposing port 8333 on router doesn’t allow inbound node connections.

Therefore I can run a completely validating node however can not run a listening node as I’m unable to obtain incoming requests.

Bitcoin Core v22.0.0 - 70016/Satoshi:22.0.0/
        ipv4    ipv6   onion   whole   block
in         0       0       0       0
out       10       0       0      10       2
whole     10       0       0      10

I discover being a leech deeply unsatisfying.

To deal with this I attempted utilizing a cloudflare tunnel to show the server operating my btc node.
cloudflared config beneath:

tunnel: <my_tunnel_id_string>
credentials-file: /residence/me/.cloudflared/<my_tunnel_id_string>.json
  - hostname: dashboard.<my_domain>.on-line    
  - service: http_status:404

    enabled: true

The cloudflare tunnel is working efficiently.
I’m able to expose a nextcloud occasion on port 80 for instance, however I nonetheless can not get my node to just accept inbound connections.

This drawback is driving me mad.

Assist appreciated.

Related Articles


Please enter your comment!
Please enter your name here

Stay Connected

- Advertisement -spot_img

Latest Articles