Return to Question

I am running bitcoind on a DigitalOcean droplet with public IP address e.g. 1.1.1.1.

I would like to connect to it via RPC from another DigitalOcean droplet with public IP address e.g. 2.2.2.2.

~/.bitcoin/bitcoin.conf on 1.1.1.1:

netstat -ln | grep 8332 on 1.1.1.1 yields:

RPC commands on 1.1.1.1 such as ./bitcoin-cli -rpcuser=x -rpcpassword=x -rpcconnect=localhost -rpcport=8332 getnetworkinfo return normally.

However, on machine 2.2.2.2, when I run ./bitcoin-cli -rpcuser=x -rpcpassword=x -rpcconnect=1.1.1.1 -rpcport=8332 getnetworkinfo I get:

Machine 1.1.1.1 has firewall rules in DigitalOcean as follows:

Note that SSH into 1.1.1.1 from 2.2.2.2 is working just fine.

sudo iptables -L on 1.1.1.1 gives:

I am running bitcoind on a DigitalOcean droplet with public IP address e.g. 1.1.1.1.

I would like to connect to it via RPC from another DigitalOcean droplet with public IP address e.g. 2.2.2.2.

~/.bitcoin/bitcoin.conf on 1.1.1.1:

netstat -ln | grep 8332 on 1.1.1.1 yields:

RPC commands on 1.1.1.1 such as ./bitcoin-cli -rpcuser=x -rpcpassword=x -rpcconnect=localhost -rpcport=8332 getnetworkinfo return normally.

However, on machine 2.2.2.2, when I run ./bitcoin-cli -rpcuser=x -rpcpassword=x -rpcconnect=1.1.1.1 -rpcport=8332 getnetworkinfo I get:

Machine 1.1.1.1 has firewall rules in DigitalOcean as follows:

Note that SSH into 1.1.1.1 from 2.2.2.2 is working just fine.

sudo iptables -L on 1.1.1.1 gives:

datadir=/mnt/vol1
disablewallet=1
rpcuser=x
rpcpassword=x
rpcallowip=2.2.2.2/32
server=1

datadir=/mnt/vol1
disablewallet=1
rpcbind=1.1.1.1
rpcuser=x
rpcpassword=x
rpcallowip=2.2.2.2/32
server=1

Running curl -v 1.1.1.1:8332 on 2.2.2.2 immediately returns with:

* Rebuilt URL to: 1.1.1.1:8332/
*   Trying 1.1.1.1...
* connect to 1.1.1.1 port 8332 failed: Connection refused
* Failed to connect to 1.1.1.1 port 8332: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 1.1.1.1 port 8332: Connection refused

which from what I have read likely indicates a firewall issue.