[Ethereum] Error: etherbase address must be explicitly specified

accountsjson-rpcweb3js

When I make a RPC to geth running remotely, I cannot get the account list / balance of the account. It also says that the coinbase is not set. But as far as I know, isnt the coinbase supposed to be the first account created if coinbase is explicitly not defined ? If I use geth command line in the remote machine, the two accounts that I have created show up, while the RPC returns 0 accounts. What could be the issue?

Best Answer

Try starting geth with explicit rpcapi flag

geth --rpc --rpcapi="db,eth,net,web3,personal,web3"

Related Solutions

[Ethereum] jsonrpc eth_accounts returns no accounts

You don't need to use the params field in your call. By doing this, you are executing this command: eth.accounts[] which returns a null value. If you want to get a list of all the accounts, you should be executing eth.accounts. So, your RPC command should be:

curl -X POST -d '{"method":"eth_accounts","id":1}' 127.0.0.1:8545

P.S: I'm assuming you already enabled RPC on port 8545. Through the console, you can use admin.startRPC() to start RPC.

[Ethereum] Error “no key for given address or file” when unlocking coinbase account

We were getting the same error and it turned out that there were two conflicting keyfiles. One in the default (~/.ethereum) and one in a custom location that we had specified using --datadir.

In the end it was just a case of cleaning up the scripts we were using to deploy the geth node to make sure that we consistently only used one or the other keystore (we went with the default in our case)

Once we had done that, the problem was solved.

Best Answer

Related Solutions

[Ethereum] jsonrpc eth_accounts returns no accounts

[Ethereum] Error “no key for given address or file” when unlocking coinbase account

Related Topic