1

I am running a node on Windows Server 2016. Everything seems to be running fine.

If I go to https://bitnodes.earn.com/ and put myip:8333, the node is successfully reachable.

My bitcoin.conf is: server=1 txindex=1 rpcuser=... rpcpassword=...

Locally, I can access it:

bitcoin-cli.exe -rpcuser=... -rpcpassword=... getinfo

returns:

{
  "deprecation-warning": "WARNING: getinfo is deprecated and will be fully removed in 0.16. Projects should transition to using getblockchaininfo, getnetworkinfo, and getwalletinfo before upgrading to 0.16",
  "version": 150001,
  "protocolversion": 70015,
  "walletversion": 139900,
  "balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 16,
  "proxy": "",
  "difficulty": 1,
  "testnet": false,
  "keypoololdest": 1506982194,
  "keypoolsize": 2000,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "errors": ""
}

However, any C# bitcoin lib I tried always returns the same web exception when trying to connect to bitcoind:

"The underlying connection was closed: The connection was closed unexpectedly."

and, also, I do not understand why some samples use port 8332, some 8333, etc. I don't have anything listening to 8332.

What could I be missing?

Improve this question

1 Answer 1

Reset to default
1

I do not understand why some samples use port 8332, some 8333, etc.

Port 8333 is the port that bitcoin uses to connect to other nodes on the network. Port 8332 is the default port for a bitcoin RPC interface. To connect with RPC, use port 8332 or specify a different port with rpcport=<port> option

Improve this answer
5
  • oh ok, so I'm going to look at a firewall issue then because 8333 is reachable and nothing replies at 8332
    – Thomas
    Oct 31, 2017 at 2:16
  • ok, I got it: the RPC calls are only allowing localhost by default...
    – Thomas
    Oct 31, 2017 at 3:17
  • Yes, you can allow other IPs with the rpcallowip=<ip> option
    – meshcollider
    Oct 31, 2017 at 3:25
  • @MeshCollider Is there a way to allow all IPs?
    – Eutherpy
    Nov 15, 2017 at 21:56
  • You can use wildcard * but is dangerous to accept connection from anywhere. You can limit to a specific IP range for example 192.168.0.*
    – meshcollider
    Nov 15, 2017 at 22:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.