Quote from: n0nce on October 26, 2022, 11:12:35 PM

Quote from: Mobber on October 26, 2022, 07:09:58 PM

Quote from: nc50lc on October 26, 2022, 04:40:31 AM

Quote from: Mobber on October 25, 2022, 09:29:59 PM

When I setup the node I followed the tutorial on bitcoin.org and did the port forwarding. The node I still receiving incoming connections fine. I followed the sparrow tutorial and all info is still correct.

The node is running on a PC with windows 10 and sparrow is on a pc with windows 11. I haven't changed anything but sparrow just won't connect now. Any suggestions?

How about the guide above it about setting a static IP: bitcoin.org/en/full-node#configuring-dhcp?

By saying "still receiving incoming connections", do you mean you're still getting "Inbound" Peers or not?
Because if not, my best guess is your set 'rpcbind' IP address didn't match after getting a new IP address.

The node is definitely receiving incoming connections. It has 21 inbound right now and bitnodes shows it as accepting incoming. The WAN ip is automatic and has changed since I setup the node. But it looks like the internal ip's for the two PC's are static. Should I change that WAN ip to static?

Which IP do you use to connect Sparrow to Bitcoin Core? Your external / WAN IP or your local IP (192.xx... or similar)?
Again; opening ports in your router improves your node, since it can now accept incoming connections - by other Bitcoin Core nodes, speaking Bitcoin protocol. Not by light clients trying to do RPC.

Sparrow can use the RPC interface running on 8332 to connect to a Bitcoin node but you don't (or at least definitely shouldn't) expose that to the public internet, as it would give everyone full access to your node (e.g. spending funds).

Therefore, Sparrow connection to a Bitcoin node (without Electrum) works when both are on the same machine and also if they're on a LAN & the 8332 port is opened in the node's own firewall. Then you can access it through its local IP.
Here are the official instructions by the Sparrow team: https://www.sparrowwallet.com/docs/connect-node.html
Notice how they always mention local IPs; since connecting to Bitcoin Core's RPC interface remotely is basically completely out of the picture, anyway, they don't even mention that.

More on this here: https://bitcoin.stackexchange.com/a/88948/119879

Quote from: Mobber on October 26, 2022, 07:09:58 PM

I also just tried installing sparrow on the node PC and it won't connect to node either.

That's very weird. Is Bitcoin Core still running, fully synced and has the settings in its config file that are mentioned in the official guide?

Here is all that is in my bitcoin core config file

server=1

rpcuser=bitcoin
rpcpassword=yourpassword

[main]
rpcbind=127.0.0.1
rpcbind=node ip
rpcallowip=127.0.0.1
rpcallowip=sparrow ip

I've triple checked these are correct and they worked before. It's so strange that even sparrow on the same pc as the node won't connect. I might try just reinstalling bitcoin core and see if that fixes it.

Mobber

Posts

Merits