Replace value of your rpcbind to 0.0.0.0 which makes RPC accessible from other device. And IIRC value of bind should be changed as well.
Changing rpcbind to 0.0.0.0 worked. Thanks!
Topic: Bitcoin Core RPC remote not Working (Read 102 times)
Changing rpcbind to 0.0.0.0 worked. Thanks!
Replace value of your rpcbind to 0.0.0.0 which makes RPC accessible from other device. And IIRC value of bind should be changed as well.
Hi,
I've been trying to configure my bitcoin core node to be able to use rpc commands from another laptop in the same network, but I'm unable to do it. Idk if I am leaving out any necessary settings.
Please, see bellow the bitcoin.conf file
I think the problem is that port 8332 is only open for loopback and not for the entire net.
Also, nmap from the other laptop shows port 8332, 8333 and 8334 closed.
Note: there are no iptables or something like that closing those ports. (at least that I know)
Thanks for your time!
SS
I've been trying to configure my bitcoin core node to be able to use rpc commands from another laptop in the same network, but I'm unable to do it. Idk if I am leaving out any necessary settings.
Please, see bellow the bitcoin.conf file
Code:
pi@raspberrypi:/mnt/btc_blockchian-externalDisk/bitcoin/data $ cat bitcoin.conf
proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
prune=100000
server=1
rpcuser=****
rpcpassword=****
[main]
rpcbind=127.0.0.1
rpcbind=192.168.1.2
rpcallowip=192.168.1.0/24
rpcallowip=127.0.0.1
Proxy settings on the top are for Tor connection, just ignore it.proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
prune=100000
server=1
rpcuser=****
rpcpassword=****
[main]
rpcbind=127.0.0.1
rpcbind=192.168.1.2
rpcallowip=192.168.1.0/24
rpcallowip=127.0.0.1
I think the problem is that port 8332 is only open for loopback and not for the entire net.
Code:
pi@raspberrypi:~ $ sudo netstat -tulpn | grep LISTEN
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 545/tor
tcp 0 0 127.0.0.1:9051 0.0.0.0:* LISTEN 545/tor
tcp 0 0 127.0.0.1:8334 0.0.0.0:* LISTEN 556/bitcoind
tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN 556/bitcoind
tcp 0 0 127.0.0.1:8333 0.0.0.0:* LISTEN 556/bitcoind
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 540/sshd: /usr/sbin
tcp6 0 0 :::22 :::* LISTEN 540/sshd: /usr/sbin
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 545/tor
tcp 0 0 127.0.0.1:9051 0.0.0.0:* LISTEN 545/tor
tcp 0 0 127.0.0.1:8334 0.0.0.0:* LISTEN 556/bitcoind
tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN 556/bitcoind
tcp 0 0 127.0.0.1:8333 0.0.0.0:* LISTEN 556/bitcoind
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 540/sshd: /usr/sbin
tcp6 0 0 :::22 :::* LISTEN 540/sshd: /usr/sbin
Also, nmap from the other laptop shows port 8332, 8333 and 8334 closed.
Code:
PORT STATE SERVICE VERSION
8332/tcp closed unknown
8333/tcp closed bitcoin
8334/tcp closed unknown
8332/tcp closed unknown
8333/tcp closed bitcoin
8334/tcp closed unknown
Note: there are no iptables or something like that closing those ports. (at least that I know)
Thanks for your time!
SS
Jump to: