Issues with Node Syncing and Port Mapping

7 replies 288 views
wizard_2016Full Member
Posts: 127 · Reputation: 575
#1Aug 29, 2022, 07:11 PM
I’ve got some issues with my node syncing. Running Windows 11, 16 GB RAM, HDD with 707 GB free and using Bitcoin Core 25.0. 1. My debug.log shows errors every 5 minutes. I set port to 8335 since another node is using 8333. Router should be good forwarding those ports. Is this a problem?
6 Reply Quote Share
wallet_vaultFull Member
Posts: 321 · Reputation: 431
#2Aug 31, 2022, 05:01 PM
Sounds like a UPnP issue. If you have static port mappings, that might mess things up a bit. What's your sync status? Only getting 1 block every 30 seconds seems slow for HDD, but not that slow. Can you add the private IP from the other node and see if they recognize each other? - Dave
4 Reply Quote Share
wizard_2016Full Member
Posts: 127 · Reputation: 575
#3Aug 31, 2022, 07:05 PM
I was at 6 weeks behind, now it’s only 3. I think connection speed and performance matter a lot. I’ve got 8 outgoing, still just 1 incoming, and block time is sometimes down to 15 seconds. Also, that inbound connection is weird. I think router’s configured right but the AddPortMapping error makes me doubt it. Got two local nodes: 100 and 119. They see each other as peers.
3 Reply Quote Share
0xNodeMember
Posts: 671 · Reputation: 80
#4Aug 31, 2022, 07:53 PM
Yeah, that’s logical since Bitcoin Core is listening on your network. But can you ping it from outside? Check your external IP with bitcoin-cli getnetworkinfo | jq '.localaddresses' and try telnet <ip> 8333 from an external PC.
4 Reply Quote Share
wizard_2016Full Member
Posts: 127 · Reputation: 575
#5Sep 1, 2022, 12:50 AM
I tested it! I managed to telnet to port 8335 from an outside network.
1 Reply Quote Share
0xNodeMember
Posts: 671 · Reputation: 80
#6Sep 1, 2022, 02:12 AM
Cool, so it's definitely on port 8335. What if you tried connecting another outside node to your network? If you need help, send me your IP, I can try connecting from my node. If that works, then your node is receiving connections properly.
2 Reply Quote Share
cobra51Newbie
Posts: 100 · Reputation: 31
#7Sep 1, 2022, 05:15 AM
Error is likely from your UPnP config, meaning it failed to open that port. Maybe your router doesn’t even support UPnP. Not a biggie, just open it manually. Also, how's your system performance? Check I/O, RAM, CPU usage when Core runs. The syncing process is pretty good, so local resources shouldn’t be a big deal unless your internet’s super slow.
0 Reply Quote Share
gang2015Member
Posts: 682 · Reputation: 62
#8Sep 1, 2022, 10:14 AM
I use HDD too with a higher dbcache and don't have these issues. Have you tried bumping up your dbcache setting? Also, think about replacing addnode with connect. That way, you'll only pull data from your local node.
5 Reply Quote Share

Related topics