According to the docs, 8333/tcp/out is required. As mentioned before, make sure your INPUT chain has the required rules to let packets back in which belong to establised connections.
Check your complete chains to make sure a previous rule doesn't affect your rule (like having a DROP as the last default rule in a chain and then using -A with your rule).
Topic: [SOLVED] CentOS bitcoind connection problem. I need help. (Read 1219 times)
Quote
Stop iptables for a quick test;
Thank you so much.
"version" : 60300,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 13782,
"connections" : 8,
"proxy" : "",
"difficulty" : 1.00000000,
"testnet" : false,
"keypoololdest" : 1345161090,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
Now what rules do i have to put, I need my firewall back.
Thanks
rpcpassword=hunter2
rpcallowip=*
Seriously? You might want to limit that. Also, are you reading bash.org sometimes?rpcallowip=*
membersrv@linnareacu [~]# iptables -L | grep '8333'
ACCEPT tcp -- anywhere anywhere tcp dpt:8333
Bitcoin will also try to use IRC since you did not exclude it. That aside, the grep result doesn't show if it's in the INPUT or OUTPUT chain. I assume you have a rule for ESTABLISHED/RELATED too?ACCEPT tcp -- anywhere anywhere tcp dpt:8333
Stop iptables for a quick test; if bitcoind connects, you can adjust your rules (netstat helps there)
Guess you've already been through this thread:
https://bitcointalksearch.org/topic/bounty-done-update-bitcoind-build-script-for-v063-on-centos-32-bit-64-bit-98647
https://bitcointalksearch.org/topic/bounty-done-update-bitcoind-build-script-for-v063-on-centos-32-bit-64-bit-98647
Yes I've read this thread, it was very useful. I got it running but no connections. I can connect via rpc https://i.imgur.com/kPSuC.jpg.
It's installed on a dedicated server with hostgator. The iptable seems correct but I cant ping the port with http://www.yougetsignal.com/tools/open-ports/.
Here is a quote from hostgator about opening ports:
Quote
Dedicated Server and VPS accounts can open new inbound and outbound ports. Please email [email protected] with this request.
Would this be the reason? Is there anything I can check before I contact them?
This guy had the same problem: https://bitcointalksearch.org/topic/my-upgrade-issue-to-62-81818 I tried removing the files in .bitcoin but leaving the wallet.dat and bitcoin.conf, but it still wouldnt start connecting to peers.
I tried to add the fallback nodes from https://en.bitcoin.it/wiki/Fallback_Nodes but they all seem down? Is there a recent list?
Thanks
Mods: please move this to support/dev discussion. Thank you.
I've got bitcoind installed on a centos server with the help of [1] http://www.firenzee.com/bitcoin-centos.sh.
./bitcoind -daemon
bitcoin server starting
./bitcoind getinfo
{ "version" : 60300, "protocolversion" : 60001, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 0, "connections" : 0, "proxy" : "", "difficulty" : 1.00000000, "testnet" : false, "keypoololdest" : 1345161090, "keypoolsize" : 101, "paytxfee" : 0.00000000, "errors" : "" }
here is my bitcoin.conf file:
rpcuser=user
rpcpassword=hunter2
rpctimeout=90
rpcport=8332
rpcallowip=*
server=1
Iptable:
membersrv@linnareacu [~]# iptables -L | grep '8333'
ACCEPT tcp -- anywhere anywhere tcp dpt:8333
I've got bitcoind installed on a centos server with the help of [1] http://www.firenzee.com/bitcoin-centos.sh.
./bitcoind -daemon
bitcoin server starting
./bitcoind getinfo
{ "version" : 60300, "protocolversion" : 60001, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 0, "connections" : 0, "proxy" : "", "difficulty" : 1.00000000, "testnet" : false, "keypoololdest" : 1345161090, "keypoolsize" : 101, "paytxfee" : 0.00000000, "errors" : "" }
here is my bitcoin.conf file:
rpcuser=user
rpcpassword=hunter2
rpctimeout=90
rpcport=8332
rpcallowip=*
server=1
Iptable:
membersrv@linnareacu [~]# iptables -L | grep '8333'
ACCEPT tcp -- anywhere anywhere tcp dpt:8333
Jump to: