0

I'm trying to connect my hardware wallet to my personal full node for the sake of privacy. I need to know the node's IP, port, and RPC credentials. The first two are easy, I can see my full node in bitcodes.io that's up and running. I added the

rpcuser=xxx
rpcpassword=****

to the bitcoin.conf file. But When I try to connect through my hardware wallet application, it says: The node is not reachable. I'm not sure whether the bitcoind is reading the rpc inputs from the config file or not. Is there anyway that I could try to reach to my node to make sure it's reachable using the rpc credentials.

Here is the content in the bitcoin.conf file:

prune=0
txindex=1
server=1
daemon=1
rpcuser=letsbegin
rpcpassword=*****
externalip=xx.xx.xx.xx
Improve this question
2
  • What hardware wallet software?
    – Claris
    Feb 25, 2021 at 3:18
  • It's the Ledger Live
    – Pishi
    Feb 25, 2021 at 17:29

1 Answer 1

Reset to default
0

How to connect your hardware wallet to a full node depends heavily on what wallet software you're using. But assuming your software connects to a full node via the bitcoind RPC interface:

By default, the RPC listener only listens on localhost. If you want to connect to the RPC service from another computer, you'll have to allow other connections by including these lines in your bitcoin.conf (replace:

server=1
rpcallowip=<add the IP you are connecting from here, or rpcallowip=* to allow all IPs>
rpcport=8332

If you want to simply test whether your bitcoind RPC is accessible, you can simply make an HTTP request to the RPC host at port 8332 from the computer you're trying to connect from.

Improve this answer
8
  • So, here is the issue: Both the connecting computer and my node are within the same network i.e., same IP address! I added the commands that you suggested, still I can't reach to my node even when I make an HTTP request!!!
    – Pishi
    Feb 25, 2021 at 17:29
  • By same network do you mean same computer? If so, then make sure you use "127.0.0.1:8332".
    – ieatpizza
    Feb 25, 2021 at 19:41
  • No not the same computer. Two different computers connected to the internet at my home. When I run the get networkinfo command:"name": "ipv4", "limited": false, "reachable": true, "proxy": "", "proxy_randomize_credentials": false }, { "name": "ipv6", "limited": false, "reachable": true, "proxy": "", "proxy_randomize_credentials": false }, { "name": "onion", "limited": true, "reachable": false, "proxy": "", "proxy_randomize_credentials": false
    – Pishi
    Feb 25, 2021 at 20:51
  • When I check the external ip address for both the computers I get the same ip! Should I use internal IP address assigned to my node?
    – Pishi
    Feb 25, 2021 at 21:01
  • @Pishi - yes, use the internal IPs for this.
    – ieatpizza
    Feb 26, 2021 at 4:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.