MM bug? Ledger: Account does not belong to connected device

Swing · January 15, 2023, 5:41pm

So I connected the ledger nano s to MetaMask and added a new ETH address, where I sent my funds to. But when I try to move the funds out MetaMask is saying that the address does not belong to the connected device.

I have never had any other ledger device and if I try to add another address using my ledger MetaMask shows a different address in the list for the account number that I added previously and sent my funds to. Could this be a bug?

Someone please help, this is all my ETH!

KBeeTheCapybara · January 15, 2023, 6:15pm

Hi!,

Please check if your Ledger account is already paired with MetaMask? In the wallet extension, please click the identicon in the top right-hand corner and scroll down to see the account in your wallet.

If you have any other crypto wallets enabled on your browser, please disable them and clear your browser’s cache. Please then reboot your browser and try connecting your Ledger to MetaMask once again.

Please ensure your Ledger Live is closed when pairing via WebHID and the ETH app is open on your Ledger device before starting the "Connect Hardware Wallet > Ledger > Continue " sequence in MetaMask.

In addition, check out this article from Ledger for connection issues.

After reviewing above, please let us know if you’re still having issues.

Swing · January 15, 2023, 6:25pm

Hi there. Thanks for the quick reply.

My ledger is properly paired with MetaMask. I know for sure because I already tried sending small amounts from other addresses that are also connected to Ledger. The problem is with one specific address which, apparently, was not created properly by MetaMask (as I said before, if I repeat the process for the address in question on a different brouwser/pc I get an entirely different address).

Could it be possible that MetaMask did not request the address from the ledger device using the correct derivation path?

Luigi · January 15, 2023, 6:28pm

Hi @Swing try to find ETH address it with the help of this guide using the Findet site.

It must find this ETH address if it was created by your Ledger wallet
and it will show the ETH derivation path

Swing · January 15, 2023, 6:43pm

Hi Luigi. Thanks for trying to help.

I already tried Findeth but without luck. Upon further research it seems like the problem could have been due to a MetaMask bug related to associating addresses to incorrect derivation paths, as found on Reddit (I can’t post links, but the post is titled " Bug in MetaMask v10.0.2 when connected to the ledger, causing it to generate address not easily accessible.")

So if MetaMask sent a non-standard derivation path to the ledger device the address won’t be found on Findeth, as this website only looks into a few pre-set derivation paths.

KBeeTheCapybara · January 15, 2023, 6:56pm

Please contact MetaMask support. Go to support.metamask.io and choose ‘Start a Conversation’ this will help you open a ticket:

Luigi · January 15, 2023, 7:02pm

I am reading interesting bug.

Try download here the file bip39-standalone.html

Disconnect from the internet
and try to find yours derivation path good luck.

But it would like a better tool

Swing · January 15, 2023, 7:20pm

yeah thanks, but I won’t expose my seed phrase like that. I’m using a hardware wallet for a reason ;).

Luigi · January 15, 2023, 7:29pm

Without internet hard and you can create a live Ubuntu for greater security.

KBeeTheCapybara · January 15, 2023, 8:04pm

To share, have also passed along this to the team. Will let you know when I have a response!

Luigi · January 15, 2023, 10:21pm

@Swing this discussion is also interesting.

github.com/MetaMask/metamask-extension

Ledger Nano: Metamask Address does not correspond to Ledger

opened 09:44PM - 11 Jan 19 UTC

closed 01:29PM - 26 May 22 UTC

AusIV

type-bug needs-reproduction area-hardware Sev1-high hardware-ledger stability

**Describe the bug** Somehow a Metamask account was created in association with a Ledger Nano that did not correspond to any account supported by that ledger. **To Reproduce** We have not been able to reproduce this issue reliably, but here are the steps we took to encounter it in the first place: 1. Connect a ledger nano, unlock it, and navigate to the Ethereum app on the Ledger 2. In Metamask, select "Connect Hardware Wallet" from the accounts menu 3. Select Ledger and Connect 4. Select an account and click "Unlock" 5. Click the copy button next to the address to copy the wallet address. 6. Send ETH to that address. 7. Reboot, disconnect the ledger, come back later. 8. Reconnect the ledger nano, unlock it, etc. 9. Attempt to send a transaction from the Metamask account. 10. Get an error similar to the effects of #6011 - Metamask is sending from a different address than the attached ledger. 11. If you attempt to import another account from the ledger, the original address is not available. **Expected behavior** If I connect an account from a ledger nano, I expect that account / address to exist on the ledger nano. **Browser details (please complete the following information):** - OS: Windows 10 - Browser Chrome - MetaMask Version 5.3.0 **Additional context** I'm not certain how this happened. My understanding is that when a ledger is connected, Metamask asks it for a list of addresses, and those addresses are provided by the nano without any proof that it can sign messages with it. I suspect that some kind of interference (static electricity, gamma rays, a butterfly flapping its wings in China, etc.) caused the initial transmission of the address to be sent incorrectly, but it's hard to say for sure. Ledger Live does not allow a user to connect an account without first confirming the address by clicking a button on the ledger (I'm not sure how this works under the hood, but I have the impression it's signing a message). It strikes me that this could have been avoided if metamask had required the user to sign a message before considering the account connected. In our case we lost about $2 worth of ETH, but it could have been a lot worse.

But the tool I see there also needs a seed phrase
and your ETH address + Linux (without internet)

Derivation Path can also be changed on the myetherwallet page:

KBeeTheCapybara · January 16, 2023, 6:37pm

@Swing ,

Received a response fro support team, they asked if you would please submit a support ticket so they can take a deeper look. All the threads posted here to Reddit or GH were resolved. Follow the steps above to open one.

Support will never ask for your Secret Recovery Phrase or ask you to input it on a site, form, pop-up window. No matter how legit something may look, never provide it anywhere. Also, support will never ask to connect to your device or ask you to screenshare.

Thanks so much!

Swing · January 16, 2023, 8:36pm

Thanks, I appreciate it. It’d be great if they can release a fix that won’t require expose the seed…

Swing · January 16, 2023, 8:37pm

oh I just saw this reply. I’ll create a ticket, thanks.

Luigi · January 16, 2023, 10:19pm

@Swing I was looking for a better tool but I couldn’t find one.

Try the site https://mycrypto.com/
I read here that they have a hardware wallet scanner…

Swing · January 17, 2023, 9:01am

Already did! That indeed appears to be the best site for deriving addresses from custom paths. The problem is that I don’t know which path MetaMask sent to the ledger device, so I could be trying for ages before I find the correct one…

Swing · January 25, 2023, 3:14pm

I have been chatting back and forth with MetaMask Support for about a week now, but they haven’t been able to help me solve the issue; it’s a process I guess. When/if a solution is found I will share it here for future reference.

Swing · February 9, 2023, 10:38pm

This is just a message to keep the thread open. The issue is still being investigated by MM support.

Luigi · February 10, 2023, 11:55am

OK @Swing I will leave this topic open and when you find a solution let us know.