I have a full node running on a Linux device (A) with static IP and I want to run bitcoin-cli commands or even eclair instances from a different device (B) within the same local network.

Device (A) has bitcoin.conf configured to accept RPC calls with this basic bitcoin.conf


Actually I have an eclair running successfully on Device (A) and default RPC ports connect well. No typos on user_name and passwords.

When running the following command in device (B):

bitcoin-cli -rpcconnect= -rpcport=8332 -rpcuser=<user_name> -rpcpassword=<password> -getinfo

error: Could not connect to the server (error code 1 - "EOF reached")
Make sure the bitcoind server is running and that you are connecting to the correct RPC port.

Any ideas what can be wrong?

3 Answers 3


If you're going to just use within the network and not outside of the LAN then as mention below, use rpcallowip= will work and also don't use rpcconnect as it may cause issues. If your planning future to use that option outside of the LAN (aka WAN) then there will be security issues so make sure to not use it outside of the LAN unless you can configure it correctly to not allow accept all ip.


add rpcallowip= to your bitcoin.conf and restart your daemon. or may rpcallowip= is your option.


There's a discussion on this with some answers here:

Cannot call rpc api from other machine in same local network

tl;dr: you need to also set the rpcbind setting to something like rpcbind= or rpcbind='ipaddress of node'. I needed to start the daemon with the -rpcbind=... option, it wouldn't work if I just set it in the conf file.

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.