Bitcoin Forum
December 25, 2025, 01:04:30 PM *
News: Latest Bitcoin Core release: 30.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: pairing sparrow on one machine to knots node on different machine via LAN/RPC  (Read 38 times)
BCC67 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 2


View Profile
December 24, 2025, 05:43:07 AM
Last edit: December 24, 2025, 07:45:15 AM by BCC67
Merited by ABCbits (2)
 #1

Has anyone been able to successfully pair a knots node to sparrow on a different machine?

I activated RPC in the bitcoin knots-qt GUI.

Then I went into the bitcoin conf file and added the following:

rpcuser:xyz
rpcpassword:abc
rpcbind:127.0.0.1
rpcbind:0.0.0.0
rpcbind: *actual machine IP*
rpcallowip: *IP of machine running sparrow*
server=1
txindex=1

My issue is probably the RPC bind line... I tried many combinations of the 3 listed above.

On sparrow side, in server settings I selected bitcoin core, entered the IP of the knots machine in the URL line. Entered username and PW. Port set to 8332, as it says that is the default.

The failure on sparrow is:

could not connect:

Connection refused

nc50lc
Legendary
*
Offline Offline

Activity: 3010
Merit: 8171


Self-proclaimed Genius


View Profile
December 24, 2025, 07:27:17 AM
 #2

rpcallow: *IP of machine running sparrow*
I haven't tested to reproduce your setup but try to change this one invalid config; it should be rpcallowip instead of rpcallow.
Don't forget to restart the node to apply the setting.

BCC67 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 2


View Profile
December 24, 2025, 07:44:51 AM
 #3

rpcallow: *IP of machine running sparrow*
I haven't tested to reproduce your setup but try to change this one invalid config; it should be rpcallowip instead of rpcallow.
Don't forget to restart the node to apply the setting.

Oh, good eye. Unfortunately I only typo'd in this post, was using the correct syntax on the conf file. Sad
nc50lc
Legendary
*
Offline Offline

Activity: 3010
Merit: 8171


Self-proclaimed Genius


View Profile
Today at 11:07:52 AM
 #4

Hmm, it's already using 0.0.0.0 so in theory, it doesn't even need the other bind settings.
Can you try to set rpcallowip=your_network_gateway/16 (e.g.: 192.168.1.1/16) to cover all of your local network's IP addresses.
Are the machines running with static IP? If not or not sure, this should work.

Also, I'm assuming that those ":" are also typos, because those should be "=" or will not be parsed otherwise.

If nothing works:
AFAIK, Sparrow writes something to its log file if there an issue with its configured server connection,
Try to check the "sparrow.log" file in you Sparrow Wallet's data directory.
In case you don't know its location, refer to this documentation: sparrowwallet.com/docs/faq.html

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!