Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MetaMask can not send transactions to localhost:8545 #1722

Closed
quangleehong opened this issue Jul 3, 2017 · 7 comments
Closed

MetaMask can not send transactions to localhost:8545 #1722

quangleehong opened this issue Jul 3, 2017 · 7 comments

Comments

@quangleehong
Copy link

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

@danfinlay
Copy link
Contributor

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.

@soenkeba
Copy link

soenkeba commented Jul 4, 2017

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).

@kumavis
Copy link
Member

kumavis commented Jul 6, 2017

@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

@kumavis kumavis closed this as completed Jul 6, 2017
@quangleehong
Copy link
Author

quangleehong commented Jul 11, 2017

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.

@QingyangKong
Copy link

Hi @soenkeba , what is the chainId metamask uses? Is there a way changing chainId for MetaMask

@danfinlay
Copy link
Contributor

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.

maggie-wang-bbt pushed a commit to CyberMiles/travis that referenced this issue Feb 28, 2018
maggie-wang-bbt pushed a commit to CyberMiles/travis that referenced this issue Feb 28, 2018
@motafa1320
Copy link

hi
why at the metamask option local host 8545 dont active?

hjetpoluru added a commit that referenced this issue Apr 23, 2024
## **Description**
Change in the PR fixes the flaky test CircleCI job -
test-e2e-chrome-vault-decryption

https://app.circleci.com/pipelines/github/MetaMask/metamask-extension/77436/workflows/983b4b1c-104a-4acc-ad35-36fe09a03a29/jobs/2685234

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24195?quickstart=1)

## **Related issues**

Fixes: 
#24180
#1722

## **Manual testing steps**

Run the test in codespace or locally --> Checkout to the branch
yarn
yarn dist
yarn test:e2e:single test/e2e/vault-decryption-chrome.spec.js
--browser=chrome

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
hjetpoluru added a commit that referenced this issue Apr 23, 2024
## **Description**
Change in the PR fixes the flaky test CircleCI job -
test-e2e-chrome-vault-decryption

https://app.circleci.com/pipelines/github/MetaMask/metamask-extension/77436/workflows/983b4b1c-104a-4acc-ad35-36fe09a03a29/jobs/2685234

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24195?quickstart=1)

## **Related issues**

Fixes: 
#24180
#1722

## **Manual testing steps**

Run the test in codespace or locally --> Checkout to the branch
yarn
yarn dist
yarn test:e2e:single test/e2e/vault-decryption-chrome.spec.js
--browser=chrome

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants