bitcoind uses wrong interface to send commands #2028

The problem: fresh install start the daemon like ./bitcoind -rpcuser=foo -rpcpassword=bar using other terminal, try to send command: ./bitcoind -rpcuser=foo -rpcpassword=bar help I get the following message: error: server returned HTTP error 403

Versions: bitcoin-0.7.1-linux $ uname -a Linux server 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux

What is going on: the daemon is using the loopback to receive connections, my machine has the loopback (127.0.0.0) and two other interfaces eth0 and eth1, when I use the bitcoind to send commands, the process gets the IP from the eth0 and not from the loopback!

What I did to get it working: after some debuging I realised what was the problem, so I started the daemon like ./bitcoind -rpcuser=foo -rpcpassword=bar -rpcallowip=10.0.0.1 that IP is from my eth0, now when I send the commands the daemon answer correctly.

If you need more info, let me know.

Thank you very much, this bitcoin thing is a great idea!

The parameter that determines where the RPC client should connect to, -rpcconnect, has hardcoded default to 127.0.0.1:(rpcport) (see https://github.com/bitcoin/bitcoin/blob/master/src/bitcoinrpc.cpp#L1122), so I don't understand how it could have been using a different interface on your system. Maybe you have some different rpcconnect setting around in bitcoin.conf?

In any case you can provide the IP to connect to using that parameter, no need to change the rpcallowip.