pairing sparrow on one machine to knots node on different machine via LAN/RPC

[BCC67]

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]

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]

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.

[nc50lc]

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

[Cricktor]

Because OP doesn't say any details on which OS his Knots node operates, I don't want to make unnecessary guesses.

In addition to what others said, what about your local network and firewall settings both on the Knots and Sparrow machines? Nobody knows your local network configuration and how and/or if you secure your local network more than average John Doe.

I could assume that devices in your local network can all talk to each other without any restrictions, but frankly why should we make such an assumption?

Is there anything funky in the debug.log of Knots?

Does Sparrow happily connect and talk to your Knots node when you install and open it locally on the Knots machine? (Yes, I know, this is not exactly what you want, but if the local version works, this could indicate where to look more closely at.)

Try to approach the problem a bit more methodically and provide more details to avoid guess work.

[nc50lc]

Try to approach the problem a bit more methodically and provide more details to avoid guess work.

This is a good idea if the issue isn't solved by allowing his whole network.

One example would be running bitcoin-cli on the machine where Sparrow is running.
There, OP can try to issue RPC commands (with the correct args, e.g.: -rpcconnect -rpcport -rpcuser -rpcpassword) to his Bitcoin Knots and get an immediate response/error.
Useful in some cases where the issue isn't logged in the server (Knots) because the client (bitcoin-cli/Sparrow) failed to establish a connection.