Beware of phishing attacks, Ledger will never ask for the 24 words of your recovery phrase. Never share them. Learn more

Solving a MetaMask connection issue

Ledger x MetaMask connection issues

  • For mobile users, if you wish to connect your Ledger device to MetaMask on a mobile device, please follow this guide. Note that this functionality is only available for Nano X devices on iPhones or Android through a Bluetooth connection (USB connection is not supported for the moment).  Second, make sure to update the Metamask app on your iPhone to v7.17.0 or above. This might require a manual update through the AppStore.
  • For desktop users, we're aware of ongoing problems connecting Ledger devices to MetaMask on Firefox.
  • Firefox users: Firefox 114 broke U2F compatibility -  disrupting the ability to connect Ledger or any other hardware wallets to MetaMask. Please use other browsers which support U2F or WebHID connection method type (eg. Chrome, Brave).
  • Chrome users: Make sure you have the latest version of MetaMask and Chrome installed in your browser. Newer versions of MetaMask now automatically use WebHID as the default connection method on Chrome and no longer support the 'Preferred Connection Type' option feature available in older versions.
    Additionally, make sure to enable HID devices in your Chrome settings as seen in the picture below:
    URL: chrome://settings/content/hidDevices

    If the issue persists, consider using Taho or Rabby as an alternative. Please note that you'll need to use the Chrome browser, as Taho and Rabby do not support Firefox.

In this article, you will learn a few tips that can help you connect your Ledger device to MetaMask.

Most MetaMask connection issues can be avoided by following the tips below.

 Please go through each item carefully then try connecting your Ledger device to MetaMask again.

  • Ensure you are using the latest versions of both MetaMask and Chrome in your browser. Recent updates to MetaMask have introduced WebHID as the default connection method on Chrome, replacing the 'Preferred Connection Type' option found in older versions.
  • Completely close and reopen the web browser. This clears all caches and forces a resync with the blockchain.
  • Switching browsers might solve the issue. We recommend using Chrome or Brave as connecting a Ledger device to MetaMask is no longer supported on FireFox.
  • Ensure that MetaMask is updated to version 10.5.2 or above. You can learn how to check your MetaMask version here.
     Chrome users can manually force an update by going to Manage extensionsDeveloper mode > Update
  • Ensure that your Ledger device runs the latest firmware version. You can learn more here (Nano S users), here (Nano X users) or here for (Nano S plus users).
  • Ensure that your Ledger device is running the latest version of the Ethereum (ETH) app. Learn more here.
  • Ensure that Ledger Live is closed otherwise it might prevent your Ledger device from connecting to MetaMask.
  • Open the Ethereum (ETH) app on your Ledger device before starting the "Connect Hardware Wallet > Ledger > Continue" sequence in MetaMask.
     This also applies to other EVM-compatible blockchain apps like Polygon, Binance Smart Chain, etc.
  • Ensure that blind signing is enabled in the Ethereum app settings on your Ledger device. Learn more here.
  • Ensure that Metamaks is opened in a tab by clicking the "three dots" icon and selecting Expand View. 
  • If the issue persists, try resetting your MetaMask account by going to Settings > Advanced > Reset Account. Once your account is reset, restart your browser and try connecting your Ledger device to MetaMask again.
     Resetting your MetaMask account is safe but it will wipe your transaction history in the Activity tab in MetaMask.
  • Try going through the 'connect hardware flow' again. If it works, great, if not, please save the error message and provide to support if needed.

  • Still having connection issues, and have some Ethereum in MetaMask? Try a basic "send" of some Ethereum and see what happens. If it doesn't work, we know this is a MetaMask issue. If it does work, it's likely something else that's causing the issue. 

Was this article helpful?