<p>I'm leaving this as the answer merely to have the question marked as done.</p>
<p>First thing: the questions I linked to and what I described as my node configuration are indeed the correct configuration to have a node accept RPC requests over a network.</p>
<p>My issue was that my router seemed to be interfering. I'm unsure how this should work but 2 things lead me to believe this is true:</p>
<ol>
<li>The router's configuration had port forwarding turned off. I guess this is the evidence with the least force since it also mentions this is needed to forward requests from the public internet. But hey, it was the only thing that I could remotely relate to something blocking requests between computers in my LAN.</li>
<li>I just made a VPN using tailscale and my RPC requests just worked. And since against facts there can be no arguments, that pretty much settles it in my mind.</li>
</ol>
<p>Unfortunately, my ISP thinks I'm not allowed to reconfigure these settings, for my own &quot;safety&quot;. In other words, I need to get a different router. One that <em>I</em> control.</p>
<p>So to future readers, the advice is: check your router and use a VPN like tailscale. You even get the benefit of <em>not</em> having to be in your LAN to use your node.</p>

CC BY-SA 4.0
2024-10-22T10:54:52.533Z
2024-10-22T10:54:52.533Z
Mateus Pereira
<p>So, I'm trying to setup my node on a small computer I have lying around and, for practical reasons, I want to be able to do RPC requests to it from computers within my own LAN. Specifically I'm running it on an ubuntu machine and trying to send requests from a windows machine.</p>
<p>I've found 2 questions already <a href="https://bitcoin.stackexchange.com/questions/90996/cannot-call-rpc-api-from-other-machine-in-same-local-network">here</a> and <a href="https://bitcoin.stackexchange.com/questions/84265/connect-to-bitcoind-from-a-different-device-within-the-same-local-network">here</a> and I did attempt their answers, but they didn't work.</p>
<p>As far as I can tell, curl is connecting successfully to the server. It prompts me for the RPC password, but then I get no response back.</p>
<h2>What I've tried so far</h2>
<p>Running bitcoind with:</p>
<pre class="lang-shell prettyprint-override"><code>bitcoind -rpcbind=0.0.0.0 -rpcallowip=192.168.1.0/24
</code></pre>
<p>I get:</p>
<p><em>EDIT:</em> I later found out that, in windows, I should use curl.exe to use the same curl as in linux. I still get the same results</p>
<pre><code>PS C:\Users\Mateus&gt; curl.exe --user ceuta --data-binary '{&quot;jsonrpc&quot;: &quot;1.0&quot;, &quot;id&quot;: &quot;curltest&quot;, &quot;method&quot;:&quot;getblockchaininfo&quot;, &quot;params&quot;: []}' -H 'content-type: text/plain;' http://192.168.0.8:8332/

PS C:\Users\Mateus&gt;
</code></pre>
<p>If I set these values in bitcoin.conf, I get the same results. If I do the curl command from a terminal session in the node machine, using the 127.0.0.1 ip, I get the response back.</p>
<p>Alternatively, if I specify <code>rpcbind</code> to be 192.168.0.8 (my node's computer ip address), I get the same behavior, except that in the node's machine now I also don't get the response.</p>
<p>I'm sorry if this might actually be more of a networking question, but I'm just wondering what is a standard way to configure one's node to be able to do RPC requests from other machines on the same LAN and if there are any configuration prerequisites for the machines like firewalls, static ips or whatever, pointing me to a resource would be quite helpful too...</p>

CC BY-SA 4.0
2024-10-05T14:35:04.323Z
Is it possible you have a firewall on the server, or your router, which blocks port 8332?
Pieter Wuille
CC BY-SA 4.0
2024-10-07T13:17:29.977Z
Yeah. I actually also have made sure this wasn't a firewall issue. Now, I'm unsure wether its the router. I did try to setup port forwarding, just to be 100% sure (I found nothing mentioning it was blocking anything) but my provider configured it so I can't add port forwarding rules. So now that's where I'm heading....
Mateus Pereira
<bitcoin-core><bitcoind><json-rpc>
What is the proper configuration and command to run bitcoincore and use RPC over LAN?
Mateus Pereira
# What is the proper configuration and command to run bitcoincore and use RPC over LAN?

(Asked by: username_0 on 2024-10-03)

So, I'm trying to setup my node on a small computer I have lying around and, for practical reasons, I want to be able to do RPC requests to it from computers within my own LAN. Specifically I'm running it on an ubuntu machine and trying to send requests from a windows machine.

I've found 2 questions already [here](https://bitcoin.stackexchange.com/questions/90996/cannot-call-rpc-api-from-other-machine-in-same-local-network) and [here](https://bitcoin.stackexchange.com/questions/84265/connect-to-bitcoind-from-a-different-device-within-the-same-local-network) and I did attempt their answers, but they didn't work.

As far as I can tell, curl is connecting successfully to the server. It prompts me for the RPC password, but then I get no response back.

## What I've tried so far

Running bitcoind with:

```shell
bitcoind -rpcbind=0.0.0.0 -rpcallowip=192.168.1.0/24

```

I get:

*EDIT:* I later found out that, in windows, I should use curl.exe to use the same curl as in linux. I still get the same results

```
PS C:\Users\username_0> curl.exe --user ceuta --data-binary '{"jsonrpc": "1.0", "id": "curltest", "method":"getblockchaininfo", "params": []}' -H 'content-type: text/plain;' http://192.168.0.8:8332/

PS C:\Users\username_0>

```

If I set these values in bitcoin.conf, I get the same results. If I do the curl command from a terminal session in the node machine, using the 127.0.0.1 ip, I get the response back.

Alternatively, if I specify `rpcbind` to be 192.168.0.8 (my node's computer ip address), I get the same behavior, except that in the node's machine now I also don't get the response.

I'm sorry if this might actually be more of a networking question, but I'm just wondering what is a standard way to configure one's node to be able to do RPC requests from other machines on the same LAN and if there are any configuration prerequisites for the machines like firewalls, static ips or whatever, pointing me to a resource would be quite helpful too...

**Tags:** bitcoin-core, bitcoind, json-rpc

> **Comments:**
> **username_1**: Is it possible you have a firewall on the server, or your router, which blocks port 8332?  
> **username_0**: Yeah. I actually also have made sure this wasn't a firewall issue. Now, I'm unsure wether its the router. I did try to setup port forwarding, just to be 100% sure (I found nothing mentioning it was blocking anything) but my provider configured it so I can't add port forwarding rules. So now that's where I'm heading....  

---

## 1 answers

### Answer by username_0 on 2024-10-22. Score: 0 | Accepted answer

I'm leaving this as the answer merely to have the question marked as done.

First thing: the questions I linked to and what I described as my node configuration are indeed the correct configuration to have a node accept RPC requests over a network.

My issue was that my router seemed to be interfering. I'm unsure how this should work but 2 things lead me to believe this is true:

1. The router's configuration had port forwarding turned off. I guess this is the evidence with the least force since it also mentions this is needed to forward requests from the public internet. But hey, it was the only thing that I could remotely relate to something blocking requests between computers in my LAN.
2. I just made a VPN using tailscale and my RPC requests just worked. And since against facts there can be no arguments, that pretty much settles it in my mind.

Unfortunately, my ISP thinks I'm not allowed to reconfigure these settings, for my own "safety". In other words, I need to get a different router. One that *I* control.

So to future readers, the advice is: check your router and use a VPN like tailscale. You even get the benefit of *not* having to be in your LAN to use your node.


---

