<p>I had a brain fart. The local node was not on 192.168.0.0/24. I resolved the issue by removing rpcallowip=127.0.0.1 rpcallowip=192.168.0.0/24 and replacing with rpcallowip=0.0.0.0/0, which is fine because this is behind a firewall and public access is restricted</p>

CC BY-SA 4.0
2024-07-04T20:03:01.530Z
2024-07-04T20:03:01.530Z
Alement
<p>try:</p>
<p>rpcbind=0.0.0.0:8332</p>
<p>rpcallowip=0.0.0.0/0</p>
<p>whitelist=0.0.0.0/0</p>

CC BY-SA 4.0
2024-07-04T21:45:07.843Z
2024-07-04T21:45:07.843Z
BitcoinCore.Dev
<p>Sparrow v1.9.1
Bitcoin Core v27.0</p>
<p>When trying to connect remotely from Sparrow to my remote Bitcoin Core node, I am getting:
Could not connect:</p>
<p>Server returned HTTP response code: 403 for URL: <a href="http://x.x.x.x:8332/wallet/cormorant" rel="nofollow noreferrer">http://x.x.x.x:8332/wallet/cormorant</a></p>
<p>Any tips on why I might be getting this are greatly appreciated!</p>
<p>My Bitcoin Core config:</p>
<pre class="lang-text prettyprint-override"><code>datadir=/data/bitcoin  
rpcuser=a  
rpcpassword=b  
  
[main]  
rpcbind=127.0.0.1  
rpcbind=192.168.0.122  
rpcallowip=127.0.0.1  
rpcallowip=192.168.0.0/24
</code></pre>

<bitcoin-core><wallet><bitcoind><client><nodes>
Sparrow to Remote Bitcoin Core 403 issue
Alement
# Sparrow to Remote Bitcoin Core 403 issue

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

Sparrow v1.9.1
Bitcoin Core v27.0

When trying to connect remotely from Sparrow to my remote Bitcoin Core node, I am getting:
Could not connect:

Server returned HTTP response code: 403 for URL: <http://x.x.x.x:8332/wallet/cormorant>

Any tips on why I might be getting this are greatly appreciated!

My Bitcoin Core config:

```text
datadir=/data/bitcoin  
rpcuser=a  
rpcpassword=b  
  
[main]  
rpcbind=127.0.0.1  
rpcbind=192.168.0.122  
rpcallowip=127.0.0.1  
rpcallowip=192.168.0.0/24

```

**Tags:** bitcoin-core, wallet, bitcoind, client, nodes


---

## 2 answers

### Answer by username_0 on 2024-07-04. Score: 1

I had a brain fart. The local node was not on 192.168.0.0/24. I resolved the issue by removing rpcallowip=127.0.0.1 rpcallowip=192.168.0.0/24 and replacing with rpcallowip=0.0.0.0/0, which is fine because this is behind a firewall and public access is restricted


---

### Answer by username_1 on 2024-07-04. Score: 0

try:

rpcbind=0.0.0.0:8332

rpcallowip=0.0.0.0/0

whitelist=0.0.0.0/0


---

