Post
Topic
Board Beginners & Help
Topic OP
Can't get bitcoind to accept RPC connections from other machines
by
tim_s_uk
on 02/04/2013, 22:59:55 UTC
I'm running bitcoind on a headless Debian 6.0 machine with the following bitcoin.conf, and the option '-daemon'
Code:
rpcuser=bitcoinrpc
rpcpassword=randompassword
It is successfully communicating with other nodes (currently 8 connections, and it has 229376 blocks). It is listening on ports 8332 and 8333:
Code:
user@server:~$ netstat -lp | grep bitcoind
tcp        0      0 localhost:8332          *:*                     LISTEN      32153/bitcoind
tcp        0      0 *:8333                  *:*                     LISTEN      32153/bitcoind
tcp6       0      0 localhost:8332          [::]:*                  LISTEN      32153/bitcoind
tcp6       0      0 [::]:8333               [::]:*                  LISTEN      32153/bitcoind
As you can see, the RPC port (8332) is only listening for local connections, as expected. I want to modify this to allow other machines to connect. The server is behind a firewall, so a wildcard is acceptable. I have tried modifying bitcoin.conf as follows:
Code:
rpcuser=bitcoinrpc
rpcpassword=randompassword
rpcallowip=*
but with this configuration bitcoind no longer listens on 8332 ipv4 at all:
Code:
user@server:~$ netstat -lp | grep bitcoind
tcp        0      0 *:8333                  *:*                     LISTEN      6981/bitcoind
tcp6       0      0 [::]:8332               [::]:*                  LISTEN      6981/bitcoind
tcp6       0      0 [::]:8333               [::]:*                  LISTEN      6981/bitcoind
I have also tried various combinations of the lines:
Code:
rpcallowip=*.*.*.*
rpcallowip=192.168.1.3
rpcport=8332
with the same result.

The log doesn't show any obvious reason. It includes the following lines:
Code:
Bound to [::]:8333
Bound to 0.0.0.0:8333
ThreadRPCServer started

Any ideas why bitcoind isn't listening on port 8332 when I specify rpcallowip?
I have seen this question on the forum a couple of times, but it either remains unsolved (https://bitcointalk.org/index.php?topic=159504.0), or the problem was something simple like a firewall or misspelling (http://stackoverflow.com/questions/6018304).
I would like to allow other machines on my network to connect as miners (using poclbm).