Why isn't bitcoind listening on its rpc port?

Ask Question

Asked 10 years, 8 months ago

Modified 10 years, 8 months ago

Viewed 2k times

I run

sudo netstat --ip -lpa | grep bitcoin

After starting the bitcoin daemon and all I get is the 8333 port and the connections with other peers.

But when I do the same but with | grep namecoin, I get the rpc port and everything else.

I'm not being able to make poolserverj to work because of that. Since it's not listening, poolserverj gives me a 404 response on the rpc port.

My bitcoin.conf:

server=1
rpcuser=xxx
rpcpassword=xxx
rpcport=8332
rpcallowip=*
gen=0

Stéphane Gimenez

5,0943 gold badges30 silver badges37 bronze badges

asked Oct 3, 2012 at 12:07

rafael.js

1535 bronze badges

Hmm, maybe you should look for bitcoind - the Bitcoin server?
– ThePiachu
Oct 3, 2012 at 12:22
I'm using the headless version, and grep filters bitcoind with or without the "d".
– rafael.js
Oct 3, 2012 at 17:44
I commented "rpcallowip=*" and now it's working. Does anyone know why?
– rafael.js
Oct 18, 2012 at 0:44
Have you been able to reproduce this problem with any recent versions? Looking through the code, I can't seem to find a problem in the code where the wildcard is tested.
– Colin Dean
Nov 24, 2012 at 5:32

Add a comment |

0 Your Answer

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

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