I am running bitcoind on a DigitalOcean droplet with public IP address e.g.
I would like to connect to it via RPC from another DigitalOcean droplet with public IP address e.g.
Both Droplets are running Ubuntu Linux 18.04.
datadir=/mnt/vol1 disablewallet=1 rpcbind=22.214.171.124 rpcuser=x rpcpassword=x rpcallowip=126.96.36.199/32 server=1
netstat -ln | grep 8332 on
tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN tcp6 0 0 ::1:8332 :::* LISTEN
RPC commands on
188.8.131.52 such as
./bitcoin-cli -rpcuser=x -rpcpassword=x -rpcconnect=localhost -rpcport=8332 getnetworkinfo return normally.
However, on machine
184.108.40.206, when I run
./bitcoin-cli -rpcuser=x -rpcpassword=x -rpcconnect=220.127.116.11 -rpcport=8332 getnetworkinfo I get:
error: Could not connect to the server 18.104.22.168:8332 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
22.214.171.124 has firewall rules in DigitalOcean as follows:
Type Protocol Port Range Sources SSH TCP 22 126.96.36.199/32 Custom TCP 8332 188.8.131.52/32
Note that SSH into
184.108.40.206 is working just fine.
sudo iptables -L on
Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
Is there anything obviously wrong in my configuration or setup?
curl -v 220.127.116.11:8332 on 18.104.22.168 immediately returns with:
* Rebuilt URL to: 22.214.171.124:8332/ * Trying 126.96.36.199... * connect to 188.8.131.52 port 8332 failed: Connection refused * Failed to connect to 184.108.40.206 port 8332: Connection refused * Closing connection 0 curl: (7) Failed to connect to 220.127.116.11 port 8332: Connection refused
which from what I have read likely indicates a firewall issue.