For testing purposes, I need to connect from a web page in my shared hosting account (on the public internet) to my json rpc server which is running on my laptop . So bitcoind is running on my laptop, which is behind my router, and I have a shared web hosting account with easybitcoin.php running on it.

enter image description here

Let's say my router's public IP is, and the web server (where easybitcoin.php lives)'s IP address is, and my laptop LAN address is

The error I get is

Failed to connect to port 8332: Connection refused



Router Port Forwarding

enter image description here


Down. I checked it at the router and on the laptop (where there is an exception for bitcoind).


Laptop is in the router's DMZ.



Online Port Scanner Check (looks good)

Result: is listening on port 8332

Going to from inside the LAN (looks good)

JSONRPC server handles only POST requests

Going to from inside the LAN

A connection attempt timed out.

Going to from the public internet (I made an rpcallowip=IP of the testing website)

403 Response (0 characters)

Going to from the public internet (bogus port)

Connection timed out.

Once I get this working I will go back and tighten everything back up. But I need to get it working first. I must be missing something.

  • try to add: rpcallowip= instead of your IP address and see if it works.
    – Tailer
    Apr 27, 2018 at 3:28
  • Do you have a dedicated IP address? Most people have a dynamic IP with their ISP which makes things like this difficult. Look into a dynamic DNS service which will give you a static IP to provide to the internet, but will change in sync when your IP changes. The only way I've been able to make my laptop accessible to the public internet is by doing what you describe below in your answer by putting it behind a web server like wamp.
    – m1xolyd1an
    May 31, 2018 at 2:13
  • @m1xolyd1an, I don't think I do, but my provider hasn't changed my address in a year now. So for my purposes, my provider ip is static. My VPN IP might stay the same if I keep choosing the same VPN server to go through. But I have not looked into that since I turn it off when I want this functionality.
    – toddmo
    May 31, 2018 at 17:46

1 Answer 1


I could never get this to work. So as a work-around, I port forwarded http and https, and made and http endpoint that in turn called the function in question and returned the result. A roll-your-own http wrapper around bitcoind, because I couldn't get the bitcoind http server to accept a connection coming in from the outside to my router. This is not ideal, since I must turn off VPN to get even this to work.

I can tell by the settings available in bitcoin.conf that this functionality was intended to be possible. Therefore, I see this as a documentation failure. Someone somewhere knows how to do this, and I'm sure it's trivial to them, but it's a well kept secret.

I request an example of specifically this be added to bitcoin.org, since this is functionality intended to be possible.

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.