Bitcoin Forum
September 01, 2024, 06:18:43 AM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Incorrect RPCuser or RPCpassword ( authorization failed )  (Read 893 times)
Stephenpaulraj (OP)
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
June 29, 2013, 10:26:03 AM
 #1

Hi

   I am running Eloipool on Gentoo linux and testing it over VMware workstation, I have installed Bitcoind and blocks are up to date, when i type

eloipool@mypool ~ $ ./bin/bitcoind getinfo
{
    "version" : 80100,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 243906,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 19339258.27238668,
    "testnet" : false,
    "keypoololdest" : 1371974854,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : "Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin will not work properly."
}

And when i type

eloipool@mypool ~ $ ./bin/bitcoind -rpcuser=stephen -rpcpassword=3QtnxrB7P5y4EpBdad1MkCeB2RHmArvcarw7udgXsAce getinfo
error: incorrect rpcuser or rpcpassword (authorization failed)

my bitcoin.conf
is this
### bitcoin.conf configuration file. Lines beginning with # are comments.
### Uncomment and edit options you wish to use.

## JSON-RPC options (for controlling a running bitcoin-qt/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.

rpcuser=stephen
rpcpassword=3QtnxrB7P5y4EpBdad1MkCeB2RHmArvcarw7udgXsAce

# How many seconds bitcoin will wait for a complete RPC HTTP request
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.*
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use bitcoind to send commands to bitcoin-qt/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert

## Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks proxy
#proxy=127.0.0.1:9050

# Select the version of socks proxy to use (4-5, default: 5)
#socks=5

# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=<ip:port>



Can you help me where i gone wrong

when i tried connecting with GUI miner with host : 192.168.1.9 ( local host server ip ) with rpcuser and rpcpass it says

2013-06-29 15:55:20: Running command: poclbm.exe stephen:3QtnxrB7P5y4EpBdad1MkCeB2RHmArvcarw7udgXsAce@192.168.1.9:8332 --device=0 --platform=0 --verbose -r1
2013-06-29 15:55:20: Listener for "Default" started
2013-06-29 15:55:23: Listener for "Default": No PyOpenCL
2013-06-29 15:55:23: Listener for "Default": Not using OpenCL
2013-06-29 15:55:23: Listener for "Default": Nothing to mine on, exiting

I need help on this.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!