<p>It turns out that the solution didn't really have anything to do with bitcoind itself - I was running it on a virtual machine hosted on Azure, and I needed to create firewall rules for the port not only on the actual Windows machine, but also in the Azure portal! </p>

CC BY-SA 3.0
2017-12-12T20:28:37.190Z
2017-12-12T20:28:37.190Z
Eutherpy
<p>I am running a Bitcoin Cash node on my server, and starting it like this:</p>

<pre><code>start bitcoind.exe --server=1 --rpcuser=user --rpcpassword=password --rest=1 --rpcport=8332 --datadir=F:\Bitcoin --bind=10.1.0.4 --testnet=1 --rpcallowip=0.0.0.0/0
</code></pre>

<p>The node runs, and I can connect to it locally.</p>

<p>However, I can't connect to it remotely, from my C# application, using the BitcoinLib library:</p>

<pre><code>ICoinService coinService = new BitcoinService(ConfigurationManager.AppSettings["Bitcoin_DaemonUrl"], ConfigurationManager.AppSettings["Bitcoin_RpcUsername"],
ConfigurationManager.AppSettings["Bitcoin_RpcPassword"], ConfigurationManager.AppSettings["WalletPassword"]);
</code></pre>

<p>I am getting this error: </p>

<blockquote>
  <p>BitcoinLib: There was a problem sending the request to the wallet.
  System: Unable to connect to the remote server.</p>
</blockquote>

<p>I have created inbound/outbound rules in the server's firewall settings, allowing access to the 8332 port, and I think that <code>--rpcallowip=0.0.0.0/0</code> should allow all IPs to connect to my node... So I really don't know what the problem is.</p>

<p><strong>Edit:</strong> I can't access the node from <a href="https://bitnodes.earn.com/" rel="nofollow noreferrer">https://bitnodes.earn.com/</a> either.</p>

<p><em>Update:</em> the node has finished reindexing blocks, and I still can't connect to it remotely.</p>

CC BY-SA 3.0
2017-11-16T03:08:28.170Z
You're running in testnet mode (which Bitcoin Cash doesn't have), and trying to bind to the normal RPC port, and bitnodes don't support tesstnet.
Claris
CC BY-SA 3.0
2017-11-16T11:15:18.827Z
@eponymous I have started it in main net mode now, and bitnodes still says it's unreachable. It says in the logs that it's "reindexing blocks" - will my server be unreachable untill the reindexing is done?
Eutherpy
<bitcoin-core><bitcoind><client><json-rpc><bitcoin-cash>
Can't connect to Bitcoind remotely
Eutherpy
# Can't connect to Bitcoind remotely

(Asked by: username_0 on 2017-11-15)

I am running a Bitcoin Cash node on my server, and starting it like this:
start bitcoind.exe --server=1 --rpcuser=user --rpcpassword=password --rest=1 --rpcport=8332 --datadir=F:\Bitcoin --bind=10.1.0.4 --testnet=1 --rpcallowip=0.0.0.0/0

The node runs, and I can connect to it locally.
However, I can't connect to it remotely, from my C# application, using the BitcoinLib library:
ICoinService coinService = new BitcoinService(ConfigurationManager.AppSettings["Bitcoin_DaemonUrl"], ConfigurationManager.AppSettings["Bitcoin_RpcUsername"],
ConfigurationManager.AppSettings["Bitcoin_RpcPassword"], ConfigurationManager.AppSettings["WalletPassword"]);

I am getting this error: 

BitcoinLib: There was a problem sending the request to the wallet.
  System: Unable to connect to the remote server.

I have created inbound/outbound rules in the server's firewall settings, allowing access to the 8332 port, and I think that --rpcallowip=0.0.0.0/0 should allow all IPs to connect to my node... So I really don't know what the problem is.
Edit: I can't access the node from https://bitnodes.earn.com/ either.
Update: the node has finished reindexing blocks, and I still can't connect to it remotely.

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

> **Comments:**
> **username_1**: You're running in testnet mode (which Bitcoin Cash doesn't have), and trying to bind to the normal RPC port, and bitnodes don't support tesstnet.  
> **username_0**: @eponymous I have started it in main net mode now, and bitnodes still says it's unreachable. It says in the logs that it's "reindexing blocks" - will my server be unreachable untill the reindexing is done?  

---

## 1 answers

### Answer by username_0 on 2017-12-12. Score: 1

It turns out that the solution didn't really have anything to do with bitcoind itself - I was running it on a virtual machine hosted on Azure, and I needed to create firewall rules for the port not only on the actual Windows machine, but also in the Azure portal!


---

