Still can’t figure out how to get incoming connections

8 replies 145 views
Posts: 2 · Reputation: 66
#1Sep 22, 2021, 07:03 PM
I’ve tried just about everything to get this thing to accept incoming connections. Running Windows 11 with an external 1TB SSD HDD. I set a static IP address, configured the router’s firewall to permit both incoming and outgoing connections for the Bitcoin software, and also made sure Norton 360’s firewall allows the connections for Bitcoin too. Plus, I switched off my VPN. Windows firewall is set up to allow both types of connections for the Bitcoin program as well. The Bitcoin software itself is set to permit incoming connections. Anyone got any ideas? Super frustrating! Thanks!
4 Reply Quote Share
blockhubMember
Posts: 1033 · Reputation: 43
#2Sep 23, 2021, 12:22 AM
You better tell us more information about your setup and what Bitcoin program you are using. If this is the only information you could share, we can't predict what the cause of your case is. You better start using this one from sticky thread Once you provide this, we might be able to understand and find the cause of your current issue.
4 Reply Quote Share
titanx539Member
Posts: 804 · Reputation: 117
#3Sep 23, 2021, 01:56 AM
Not just those firewalls, you also have to open Bitcoin's P2P port in the router (8333 by default) Setup differs per router so you do some separate research on how to configure that in your router's settings. Read this: bitcoin.org/en/full-node#network-configuration If you're out of options, you can try the less secure "UPnP" method by enabling it in the router and Bitcoin Core's settings. But if you want a safer and more private route, you can go for Tor proxy: github.com/bitcoin/bitcoin/blob/master/doc/tor.md That'll allow inbound connections even if your ISP or router can't be configured to do so.
0 Reply Quote Share
blockhub968Full Member
Posts: 978 · Reputation: 317
#4Sep 23, 2021, 07:10 AM
Have you checked whether your ISP or internet plan use CGNAT? If yes, that's probably the reason your node can't accept incoming connection.
2 Reply Quote Share
Posts: 2 · Reputation: 66
#5Sep 23, 2021, 01:04 PM
Once you provide this, we might be able to understand and find the cause of your current issue. [/quote] Bitcoin Core version v28.1.0 Windows 11 Pro V.24H2 Device name   Scotts-Home Processor   11th Gen Intel(R) Core(TM) i9-11900KB @ 3.30GHz   3.30 GHz Installed RAM   64.0 GB (63.6 GB usable) Device ID   810EAE2F-08E9-499C-B376-128F4B891390 Product ID   00330-53253-41183-AAOEM System type   64-bit operating system, x64-based processor Description of Problem: Not able to allow incoming connection on port 8333 for full node operation Any Related Addresses: Not sure what you want here? Any Related Transaction IDs: Not sure what you want here? Screenshot of the problem: will not upload here Log Files from the Bitcoin Client:[/code]:  Not sure what you want here?
3 Reply Quote Share
Posts: 790 · Reputation: 114
#6Sep 23, 2021, 05:26 PM
The file debug.log might have some hints to your problem.
2 Reply Quote Share
blockhubMember
Posts: 1033 · Reputation: 43
#7Sep 23, 2021, 08:19 PM
Like the above said, you may be able to find some hints under debug.log. If you don't know how to look for this, then open Bitcoin Core > Window> Information. Image below for reference: Uploaded by Bitmaxz And then this one below will pop up: Uploaded by BitMaxz Click the debug.log and paste it here with code tag let us analyze it for you.
6 Reply Quote Share
titanx539Member
Posts: 804 · Reputation: 117
#8Sep 25, 2021, 09:07 PM
How about the "Port Forwarding" in the link in my previous reply? (under "Enabling Connections" link) Have you already set-it in your router? Because it's not just Firewall exception and Static IP, the latter is just a pre-requisite for Port Forwarding so you can set a specific LAN IP address of your machine. BTW, the logs with default debug configuration may not be useful if it's not caused by an issue to log an error. Still check it though.
3 Reply Quote Share
degenx380Member
Posts: 344 · Reputation: 69
#9Sep 26, 2021, 01:42 AM
I just found this topic, so I may be late. Depending on where you live, port-forwarding on your router may not be as easy as it seems. In some jurisdictions, in order to forward the traffic from one port to another you need ISP permission, which needs a foolproof explanation to them about why you need it. I am usually (in fact, I used to be) able to allow incoming connections over Tor[1] quite easily, instead of messing with networking - which is my weak spot. In short, I believe it's the easiest and safest approach! [1] https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service edit: nc50lc suggested Tor already.
0 Reply Quote Share
?Reply
Sign in to reply to this topic

Related topics