Bitcoin Core v25 Problem with Inbound Connections

10 replies 327 views
Posts: 1 · Reputation: 109
#1May 26, 2019, 05:25 AM
Hey folks, I'm running Bitcoin Core v25 as a full node, but I can only connect out and have zero inbound connections. I've got a few questions: Is there something wrong with my config file? Should I stick with the default configuration? Do I need to tweak any network or firewall settings? Here’s what I'm working with: Bitcoin Core version: v25 Operating System: Windows 11 I’d really appreciate any advice or pointers on this issue. Thanks a bunch!
8 Reply Quote Share
humbleledgerLegendary
Posts: 1027 · Reputation: 6554
#2May 27, 2019, 08:19 PM
Assuming you're using a generic home internet setup, you probably need some port forwarding in your router.
0 Reply Quote Share
hash_bossLegendary
Posts: 1166 · Reputation: 5261
#3May 27, 2019, 09:15 PM
You forget to share your configuration file, so nobody can give answer. How long have you run Bitcoin Core? If it's just recently (after completing sync/IBD), that may be reason you don't see any inbound/incoming connection. Some member don't like this approach, but you could verify whether you node can accept inbound/incoming connection by visiting https://bitnodes.io/#join-the-network and click "check node".
4 Reply Quote Share
gr3g.0rbitHero Member
Posts: 1025 · Reputation: 2646
#4May 27, 2019, 11:57 PM
The default (no "bitcoin.conf" file) is already set to enable inbound connections. Most of the time, it's just the user's network that's prohibiting it. For that, read the port-forwarding guide linked in Loyce's reply. Or alternatively, you can connect through Tor proxy which will enable your node to get inbound connections even without port-forwarding. Bitcoin Core Tor set-up Doc: github.com/bitcoin/bitcoin/blob/master/doc/tor.md
5 Reply Quote Share
alt21Senior Member
Posts: 398 · Reputation: 1732
#5May 28, 2019, 05:43 AM
LoyceV and nc50lc must have covered your question, but I 'd like to ask why it's necessary for you to accept incoming connections? Since you have outbound connections, your node is fully functional.
4 Reply Quote Share
humbleledgerLegendary
Posts: 1027 · Reputation: 6554
#6May 28, 2019, 02:50 PM
To help the network, of course Which reminds me, my bitcoind wasn't running so I just restarted it. I'm kinda curious to see how much it would upload per month now.
4 Reply Quote Share
alt21Senior Member
Posts: 398 · Reputation: 1732
#7May 30, 2019, 10:05 AM
The thing is, as long as the connection is established, it doesn't matter who initiated it and the network gets helped anyways. Obviously if nobody accepts inbound connections, there can't be a network (I think, but never actually thought about it).
3 Reply Quote Share
humbleledgerLegendary
Posts: 1027 · Reputation: 6554
#8May 30, 2019, 01:12 PM
I don't think you're uploading blocks that way. I'm more curious why OP is running such an old version of Bitcoin Core.
6 Reply Quote Share
hash_bossLegendary
Posts: 1166 · Reputation: 5261
#9May 30, 2019, 01:24 PM
Despite the name, you can perform both upload and download. But node which accept incoming connection is more likely to receive block from other node first before your node, since it have more connected node.
2 Reply Quote Share
alt21Senior Member
Posts: 398 · Reputation: 1732
#10Jun 1, 2019, 02:49 PM
That's also my take on this subject, but wanted to verify it, so thanks. The thing is, there must be nodes that accept inbound connections for the network to work. So, indeed accepting incoming connections helps the network, but, personally, I run two nodes, one Tor only and one with "default networking". For the latter, I didn't really bother messing with port forwarding, because I need ISP permission and I am also not very good with network configs.
4 Reply Quote Share
humbleledgerLegendary
Posts: 1027 · Reputation: 6554
#11Jun 1, 2019, 04:13 PM
Unless your ISP puts you behind NAT, you shouldn't need them to forward ports from your own router to your own computer.
6 Reply Quote Share
?Reply
Sign in to reply to this topic

Related topics