enter image description here

I can verify that my node is up and that the port is up via the above method, however no amount of effort has allowed me to successfully make a remote RPC call.

I am booting my node via $ bitcoind -daemon

I can make RPC calls via the same server without an issue using $ bitcoin-cli getinfo

My bitcoin.conf file looks like:

rpcuser=rpcuser rpcpassword=anthony rpcallowip=::/0

I have also tried:

rpcuser=notmyrealuser rpcpassword=notmyrealpass rpcallowip=

Without luck, both of which were suggested here: https://github.com/bitcoin/bitcoin/issues/4894 by the lead Bitcoin engineer.

I am trying to authenticate using curl, the two scripts I am using are:

curl --user notmyrealuser --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;'

and also: curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://notmyrealuser:[email protected]:8333/

Nothing is working so I figured I would ask here after several hours of not making progress, everytime I receive:

curl: (52) Empty reply from server

1 Answer 1


You're trying to send RPC queries to the P2P network port. You should use port 8332 instead of 8333.

Bitcoin Core:

  • interacts with other Bitcoin nodes on the network using the P2P protcol via port 8333 (or whatever you configure -port to be)
  • responds to RPC queries (JSON-RPC) via port 8332 (or whatever you configure -rpcport to be).
  • And just like that it's working. :) Infinite thanks man!
    – Anthony
    Mar 19, 2016 at 23:59
  • I have the same issue. it's still "connection refused" for me even though i use 8332. but works locally when i execute on my cloud instance as any other things to check ?
    – Sonic Soul
    Aug 22, 2018 at 12:06
  • i get a different error on 8333: "RemoteDisconnected: Remote end closed connection without response"
    – Sonic Soul
    Aug 22, 2018 at 12:13

Your Answer

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

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