i used MetaMask for private Eth blockchain talking to network via geth client the issue is i can import the accounts created via geth client cli with the private key, the MetaMask can see the money on coinbase acc by mining, but i try to send eth between accounts then the spinner icon keep spinning and then the transaction failed. dont know if any extra step to start geth client parameters so that the metamask can work with geth client via localhost:8545 ?
currently i start the geth with: geth --datadir "path\to\node" --networkid 12346493 --rpc --rpcport 8545 --rpcaddr 0.0.0.0 --rpccorsdomain "*" --rpcapi "db,eth,net,web3,personal,web3" --unlock 0,1,2 --nodiscover --testnet console
is there any thing to adjust so that metamask can send eth transactions ?
metamask chrome plugin version : 3.8.1, install from chrome extension
Our guide to using geth with MetaMask is here:
https://github.com/MetaMask/faq/blob/master/USERS.md#using-a-local-node
I'd think your --rpccorsdomain="*" would work, but looks like our guide makes it specific, so maybe worth trying those flags exactly.
I run into the same issue, I realized that the CHAINID in the genesis block and the geth --networkid was not the same (similar https://ethereum.stackexchange.com/questions/13498/invalid-sender-error-on-private-chain).
@soenkeba i think geth 1.6 no longer defaults the net id to chain id, so we're hearing this issue recently. we dont currently have a way to query the chainId directly so have always used the network id
i found that the issue coming from networkid is not the same with chainId in genesis block , change the networkid to be the same with chainID then the transaction done.
Hi @soenkeba , what is the chainId metamask uses? Is there a way changing chainId for MetaMask
When spinning up a local network, you have to set both its networkId and chainId to the same value for MetaMask compatibility. These are flags on geth, and are probably on parity, too.
hi
why at the metamask option local host 8545 dont active?
Most helpful comment
I run into the same issue, I realized that the CHAINID in the genesis block and the geth --networkid was not the same (similar https://ethereum.stackexchange.com/questions/13498/invalid-sender-error-on-private-chain).