-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 Hardware wallet (Ledger) to MetaMask on Linux #6732
Comments
User stated they tried all the troubleshooting steps shown on our support article here: https://metamask.zendesk.com/hc/en-us/articles/360020394612-How-to-connect-a-Trezor-or-Ledger-Hardware-Wallet I initially assumed it was a connection issue with the ledger and linux device (via USB). Changing ports and following the steps shown on Ledger's support site did not help: https://support.ledger.com/hc/en-us/articles/115005165269-Fix-connection-issues I've tried to connect a ledger to MM, on ubuntu, and experienced the same. |
I was able to connect Metamask to my Nano S, but I also have a Ledger Blue I’m trying to connect. I get the same “eternal spinner” when trying to connect my Blue. |
When using your Ledger blue, can you try to connect it to your computer via cable and not Bluetooth, to see if that works? |
I have an older Ledger blue that I don't thank does bluetooth. |
Yes this is likely the cause. You can only have one ledger connected per MM installation at this time. If you need both, I recommend installing MetaMask on another browser, or set up multiple chrome profiles. |
That makes sense. Thanks for the info!! |
@dpazdan, I've just run into the same problem with my Ledger Nano S on Linux. Brand new MetaMask install with no other hardware wallets connected, so it's not the number of wallets in my case. Also worth pointing out that my I can connect to the Ledger just fine on a Mac running the exact same version of Google Chrome that I'm using on Linux ('Version 76.0.3809.132 (Official Build) (64-bit)'). |
Had the same problem on Ubuntu + Metamask on any supported browser and without any other hardware wallet linked to metamask. The problem for me was solved by enabling Contract Data in my Ethereum app on the Ledger Nano X. Just connect the ledger through usb cable |
That worked for me too. Can't say how counter-intuitive this was. Thanks for sharing. |
thanks guys this solved the issue for me! |
Yea this is one small but crucial step in the process to make it all work (and is in our kb article found here: https://metamask.zendesk.com/hc/en-us/articles/360020394612-How-to-connect-a-Trezor-or-Ledger-Hardware-Wallet). |
This is a big issue now, I have tried many methods to get this working and metamask & ledger need to up their support. |
Can't connect. Have tried everything on the "Troubleshoot" page, still can't connect. |
I ran into this problem on Ubuntu 20.04.1 while using the Chromium browser with Metamask. It appears that the issue may be Chromium-only as switching to the Brave browser fixed the issue @JordyRacer @lieberscott: I'm not sure if y'all found a workaround yet, but this may help |
Make sure you open Ethereum application on your Ledger when trying to connect. |
I have a Ledger Blue, running on latest firmware. It connects to Ledger Live fine. It does not connect to MetaMask. I have followed the troubleshooting steps. (contract data on, tried different USB ports, cleared cache, tried different browsers) When connecting I get a message which states the security key is not familiar and try a different one. This is painful as like other users, it has cost me cash. Please help! |
Same here with the Ledger Blue. Nano S works fine but Blue doesn't connect ever. |
any plans to get this working? I'm on Windows 10, using Brave browser and same issue. Seems this browser extension is pretty much the only way to buy/store ETH currently..! |
Hi, I was told today that there was an issue with Ledger Blue and Metamask. I was offered a free hardware wallet and was effectively told there is no ETA on a fix.
…Sent from my iPhone
On 27 Feb 2021, at 22:35, David Walsh <notifications@github.com> wrote:
Hello @webprez<https://github.com/webprez> and @rebroad<https://github.com/rebroad> ! We're currently working with the @LedgerHQ<https://github.com/LedgerHQ> team to make this experience better! We'll announce progress soon!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#6732 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANMWTC2N3JC6H46KPMARQLLTBFXSTANCNFSM4HZMW5TA>.
|
Same issue on a ledger nano s here with metamask.. |
In respect of Ledger Blue, Ledger support have just offered me a different device for free as they are aware of an issue with the Ledger Blue and there is currently no ETA to fix it.
On 1 Mar 2021, at 21:13, ux33-331 <notifications@github.com> wrote:
Same issue on a ledger nano s here with metamask..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#6732 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANMWTC5F5PHOP2DELGO2ZETTBP7OZANCNFSM4HZMW5TA>.
|
That's great. What did you write/ask?
…On Mon, Mar 1, 2021, 1:29 PM richstew ***@***.***> wrote:
In respect of Ledger Blue, Ledger support have just offered me a different
device for free as they are aware of an issue with the Ledger Blue and
there is currently no ETA to fix it.
On 1 Mar 2021, at 21:13, ux33-331 ***@***.***> wrote:
Same issue on a ledger nano s here with metamask..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<
#6732 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/ANMWTC5F5PHOP2DELGO2ZETTBP7OZANCNFSM4HZMW5TA>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6732 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALYYMMUXQ6V6JLEPRVG63TTBQBK7ANCNFSM4HZMW5TA>
.
|
I just followed the support instructions from both Ledger and MetaMask, then created a ticket with Ledger support. They did not do any further troubleshooting, they asked me to confirm that I had followed the troubleshooting, said yes, then they said there was a known problem with Ledger Blue, but just that device.
From: WebPrez Videos <notifications@github.com>
Sent: 02 March 2021 07:33
To: MetaMask/metamask-extension <metamask-extension@noreply.github.com>
Cc: Richard Steward <richard.steward@stewardandco.com>; Comment <comment@noreply.github.com>
Subject: Re: [MetaMask/metamask-extension] Unable to connect Hardware wallet (Ledger) to MetaMask on Linux (#6732)
That's great. What did you write/ask?
On Mon, Mar 1, 2021, 1:29 PM richstew ***@***.***> wrote:
In respect of Ledger Blue, Ledger support have just offered me a different
device for free as they are aware of an issue with the Ledger Blue and
there is currently no ETA to fix it.
On 1 Mar 2021, at 21:13, ux33-331 ***@***.***> wrote:
Same issue on a ledger nano s here with metamask..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<
#6732 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/ANMWTC5F5PHOP2DELGO2ZETTBP7OZANCNFSM4HZMW5TA>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6732 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALYYMMUXQ6V6JLEPRVG63TTBQBK7ANCNFSM4HZMW5TA>
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#6732 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANMWTC2D7CT7EJOJFRJP37TTBSICTANCNFSM4HZMW5TA>.
|
Me having problems with Nano S and Nano X, same issue with both. Not working with any wallet (metamask, theta, terra station, etc.). The browser seems to recognize the device but when trying to access from the wallet I guess that the browser doesn't grant the access to it. Ubuntu 20 One of the wallets throws this error on the UI Seems like the browser is not providing access I've also tried to set the owner and group to my linux user on the usb dev with chmod as follows
as stated in a comment in this SO thread https://stackoverflow.com/questions/40908927/trouble-enabling-webusb-in-chrome |
So, I've read through all the comments above, walked through the ledger help and metamask help, submitted trouble tickets and received helpful but ineffective answers. I still see the spinning "Looking for your ledger" message. Has anyone solved this? I've tried different computers, a laptop (all windows 10), browsers (chorme, firefox, brave, edge), disconnected/reconnected ledge, logged out/in of metamask, checked ledger settings, turned off bluetooth, turned on contract data etc. ensured ledger live is not running, restarted my computer, closed all chrome instances and restarted chrome. I can't figure it out. Any ideas? Thx |
Same problem here using firefox's latest release... works in Brave browser, but it would be nice if it worked in Firefox as thats my go to browser! |
I can't get it to work in any browser. It works with the Ethereum chain but not with Expanse chain. It either does nothing or I see u2f device ineligible or ledger wrong app.
From: R4ZZB3RRY ***@***.***>
Sent: Wednesday, May 26, 2021 11:31 PM
To: MetaMask/metamask-extension ***@***.***>
Cc: wizardofwhere1 ***@***.***>; Comment ***@***.***>
Subject: Re: [MetaMask/metamask-extension] Unable to connect Hardware wallet (Ledger) to MetaMask on Linux (#6732)
Same problem here using firefox's latest release... works in Brave browser, but it would be nice if it worked in Firefox as thats my go to browser!
-
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#6732 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADVMVN37CJ5WAVPF3XJGXVTTPW4HXANCNFSM4HZMW5TA>.
…________________________________
[https://secureimages.mcafee.com/common/affiliateImages/mfe/logo.png]<https://home.mcafee.com/utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Scanned by McAfee<https://home.mcafee.com/utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> and confirmed virus-free.
|
edge browser infinite connect |
same issue, as a bove and torubleshoot same as everyone else i think problem is with recent firmware on ledger |
There's been some recent progress on the MetaMask/Ledger integration that could have fixed the issues here (https://consensys.net/blog/metamask/metamask-and-ledger-integration-fixed/). Could someone report that they are still experiencing this problem? Or I'll move towards closing this issue. |
I'm having issues connecting a ledger nano s plus to mm (v 10.14.7) on Ubuntu 22.04, Firefox v102.1 or Chrome v103. Using an original new USB cable (able to connect on windows machines). Tried another USB port. No AV or firewall. |
I'm also not able to connect to my ledger nano x on firefox 103.0.2+build1-0ubuntu0.22.04.1~mt1 on Ubuntu 22.04 (x86-64) from the mozillateam PPA. |
While we have fixed multiple ledger issues over the years, connection issues still persist on firefox. Most recently this is due to deprecated support for firefox+usb devices like ledger: https://support.ledger.com/hc/en-us/articles/10371387758493-Metamask-x-Ledger-Connection-Issue-On-Firefox?support=true It is unlikely we will be able to resolve connection problems with firefox+ledger in the foreseeable future. If anyone is still experiencing ledger connection issues in a browser other than firefox, please open a new ticket. |
Describe the bug
Users are unable to connect their ledger to MetaMask on linux.
Expected behavior
It should connect but when a user clicks "Connect Hardware Wallet, Ledger, Connect", an infinite spinner occurs, with no indication on the ledger device, and the account never is added.
Browser details (please complete the following information):
Additional context
related support ticket: 19873
The text was updated successfully, but these errors were encountered: