<p>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:</p>
<p>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:</p>
<pre><code>server=1
rpcallowip=&lt;add the IP you are connecting from here, or rpcallowip=* to allow all IPs&gt;
rpcport=8332
</code></pre>
<p>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.</p>

CC BY-SA 4.0
2021-02-25T17:29:05.120Z
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
CC BY-SA 4.0
2021-02-25T19:41:49.600Z
By same network do you mean same computer? If so, then make sure you use "127.0.0.1:8332".
ieatpizza
CC BY-SA 4.0
2021-02-25T20:51:10.653Z
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
CC BY-SA 4.0
2021-02-25T21:01:36.250Z
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
CC BY-SA 4.0
2021-02-26T04:20:29.000Z
@Pishi - yes, use the internal IPs for this.
ieatpizza
CC BY-SA 4.0
2021-02-27T23:11:36.047Z
I still have the issue of not being able to connect to my node. Even when I enter the local IP address for my node in a browser with the port (8332) still I can't connect. Do you think it's a firewall thing imposed by the Ubuntu running on my node? The node is running on a static IP with the port forwarded in my router. The node currently has 55 connections and roughly sends 10G of data daily!!
Pishi
CC BY-SA 4.0
2021-02-27T23:15:16.503Z
Did you add the line `rpcallowip=<the local IP address of the computer you're connecting from>`?
ieatpizza
CC BY-SA 4.0
2021-02-28T14:29:52.980Z
Yes, I added and for the IP I added the external IP and the Internal IP but none worked.
Pishi
CC BY-SA 4.0
2021-02-25T10:15:38.723Z
2021-02-25T10:15:38.723Z
ieatpizza
<p>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</p>
<pre><code>rpcuser=xxx
rpcpassword=****
</code></pre>
<p>to the bitcoin.conf file. But When I try to connect through my hardware wallet application, it says: <em>The node is not reachable.</em> 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.</p>
<p>Here is the content in the bitcoin.conf file:</p>
<pre><code>prune=0
txindex=1
server=1
daemon=1
rpcuser=letsbegin
rpcpassword=*****
externalip=xx.xx.xx.xx
</code></pre>

CC BY-SA 4.0
2021-02-25T03:18:52.430Z
What hardware wallet software?
Claris
CC BY-SA 4.0
2021-02-25T17:29:49.137Z
It's the Ledger Live
Pishi
<json-rpc><full-node><wallet-security>
Connecting a Hardware wallet to a full node
Pishi
# Connecting a Hardware wallet to a full node

(Asked by: username_0 on 2021-02-25)

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

**Tags:** json-rpc, full-node, wallet-security

> **Comments:**
> **username_1**: What hardware wallet software?  
> **username_0**: It's the Ledger Live  

---

## 1 answers

### Answer by username_2 on 2021-02-25. Score: 0 | Accepted answer

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=
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.

> **Comments:**
> **username_0**: 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!!!  
> **username_2**: By same network do you mean same computer? If so, then make sure you use "127.0.0.1:8332".  
> **username_0**: 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  
> **username_0**: 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?  
> **username_2**: @username_0 - yes, use the internal IPs for this.  
> **username_0**: I still have the issue of not being able to connect to my node. Even when I enter the local IP address for my node in a browser with the port (8332) still I can't connect. Do you think it's a firewall thing imposed by the Ubuntu running on my node? The node is running on a static IP with the port forwarded in my router. The node currently has 55 connections and roughly sends 10G of data daily!!  
> **username_2**: Did you add the line `rpcallowip=<the local IP address of the computer you're connecting from>`?  
> **username_0**: Yes, I added and for the IP I added the external IP and the Internal IP but none worked.  

---

