Try replacing the second rpcuser with rpcpassword instead.
Hopefully that should do it.
kosta
Topic: Help using RPC-JSON w/ BITCOIND on Ubuntu 12.04 and Windows 7 (Read 774 times)
UPDATE:
When I connect using Bitcoin-qt under Windows port 8332 opens! So it's not a port forwarding issue.
Can someone please tell me where I'm going wrong using the daemon (bitcoind)
When I connect using Bitcoin-qt under Windows port 8332 opens! So it's not a port forwarding issue.
Can someone please tell me where I'm going wrong using the daemon (bitcoind)
I simply cannot get port 8332 to open for me when using BITCOIND both under Ubuntu and Windows.
The bitcoin.conf file reads as follows:
server=1
rpcuser=hello1
rpcuser=12345
rpcallowip=*
rpcport=8332
gen=0
It is located in ~/.bitcoin and %appdata%\bitcoin for Ubuntu and Windows, respecitvely.
I've opened a port forward for TCP/UDP 8332-8333 on router.
What on Earth am I doing wrong? I need to access BITCOIND via RPC to run a Ruby script and no matter what I do, I simply cannot get port 8332 to open (and hence get RPC to work).
The bitcoin.conf file reads as follows:
server=1
rpcuser=hello1
rpcuser=12345
rpcallowip=*
rpcport=8332
gen=0
It is located in ~/.bitcoin and %appdata%\bitcoin for Ubuntu and Windows, respecitvely.
I've opened a port forward for TCP/UDP 8332-8333 on router.
What on Earth am I doing wrong? I need to access BITCOIND via RPC to run a Ruby script and no matter what I do, I simply cannot get port 8332 to open (and hence get RPC to work).
Jump to: