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

Unable to connect to Ledger on M1 mac mini #11836

Closed
doovers opened this issue Aug 13, 2021 · 7 comments
Closed

Unable to connect to Ledger on M1 mac mini #11836

doovers opened this issue Aug 13, 2021 · 7 comments
Labels
area-hardware hardware-ledger hardware-wallet-connection-error Sev2-normal Normal severity; minor loss of service or inconvenience. stale issues and PRs marked as stale type-bug Something isn't working

Comments

@doovers
Copy link

doovers commented Aug 13, 2021

Describe the bug
Everything has been working perfectly for months without issue until today when I tried to interact with my ledger through metamask and it didn't work. Typically when I confirm the transaction it will prompt me to confirm on the ledger but this time it didn't. Instead metamask behaved as if I had approved on the device and started to process the transaction. The transaction subsequently failed. I tried a few times with the same result. I then removed the hardware wallet account from metamask with the intention of re-adding it but now I can't. When I try to connect, I get Internal JSON-RPC error.

Steps to reproduce

  1. Connect a hardware wallet
  2. Select Ledger and continue
  3. See Internal JSON-RPC error

Expected behavior
The wallet is connected.

Browser details (please complete the following information):

  • OS: OS X
  • Hardware Wallet: Ledger Nano S Firmware version 2.0.0
  • Browser: Brave Version 1.28.105 Chromium: 92.0.4515.131 (Official Build) (arm64)
  • MetaMask Version: 9.8.4

Additional context (Error Messages, etc.)

Things I've tried:

  • Restarting computer (same issue)
  • Switching cables and ports (same issue)
  • Using Chrome instead of Brave (same issue)
  • Ledger Live bridge (gets stuck in loop trying to open ethereum app)
  • Using another (non M1) laptop with same Metamask and Brave browser versions (WORKS!!)
  • Connecting Phantom Solana app (WORKS!!)
@aloceros
Copy link

This error (Internal JSON-RPC error) also occurs on Chromebook (no Ledger Live). Windows works fine (also Chrome without Ledger Live).

@darkwing
Copy link
Contributor

I believe this is related: MetaMask/eth-ledger-bridge-keyring#89

@dpazdan
Copy link

dpazdan commented Aug 31, 2021

Please note we will be deprecating the ledger live bridge and implementing webhid support. This will likely resolve your issue. In the meantime please use Firefox with MetaMask + Ledger. Refer to: #11978, thanks!

@dpazdan dpazdan added the type-bug Something isn't working label Aug 31, 2021
@awigen
Copy link

awigen commented Sep 5, 2021

Make sure your ledger is unlocked (pin). That resolved the "Internal JSON-RPC error" issue for me.

@darkwing
Copy link
Contributor

@doovers Could you provide an update as to whether this works at the moment? If not, does toggling off and on the Ledger Live setting have an effect? As @dpazdan mentioned, we'll be supporting WebHID very soon, to help remedy this issue.

@AlexJupiter AlexJupiter added the Sev2-normal Normal severity; minor loss of service or inconvenience. label Feb 17, 2022
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

@github-actions github-actions bot added the stale issues and PRs marked as stale label Jul 24, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 7, 2023

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 7, 2023
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-hardware hardware-ledger hardware-wallet-connection-error Sev2-normal Normal severity; minor loss of service or inconvenience. stale issues and PRs marked as stale type-bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants