If you're using MyEtherWallet (MEW) with a Ledger Nano S (search terms like "my ether wallet ledger nano s" or the common typo "my ehter wallet ledger nano s" are frequent), this guide explains what happens during the connection, step-by-step setup, and the practical fixes I use when tokens or accounts don’t show up. I’ve tested this workflow on desktop with multiple browsers. What I’ve found: most problems are fixable with a few checks (device app settings, derivation path, network selection). And some problems are simply caused by browser or cable issues.
This is practical. Not hype.
MEW is a third-party wallet interface that can read public addresses from a hardware wallet and ask the device to sign transactions without exposing private keys. On the hardware wallet you open the Ethereum app; MEW asks the device to provide a public address (derived from your seed phrase) and to sign when you send or interact with contracts. This means MEW never stores your private keys — the device signs on-device.
Sources: MEW support center and device documentation describe this workflow (see MEW and hardware wallet guides and general device support pages).
Related internal pages: myetherwallet, ethereum-guide.
On the device you'll sometimes be asked to confirm actions. Approve only the screens that match the transaction details you expect.
If that simple flow fails, skip ahead to the troubleshooting checklist.
Related internal pages: connecting-desktop-mobile, troubleshooting-connection.
Here’s a compact table of symptoms, likely causes, and quick fixes.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| Tokens not loading on MEW from Ledger | "Contract data" disabled on device or wrong network | Enable Contract Data in Ethereum app; confirm you’re on Ethereum Mainnet and add token manually if needed |
| Address/accounts differ from Ledger Live | Different derivation path / account index | Try the "Ledger Live" or "Legacy (MEW)" derivation path options in MEW (see Derivation paths) |
| Device not detected by MEW | Browser blocking WebUSB, a conflicting app running, or bad cable | Close Ledger Live/manager apps, use Chrome/Firefox, try another cable/port |
| Transactions won't sign | Out-of-date firmware or Ethereum app | Update firmware and the Ethereum app on the device (verify authenticity) |
(Alt image placeholder: Screenshot of MEW hardware connect UI)
A few specifics below.
Tokens on Ethereum are handled by smart contracts. MEW displays token balances by asking the network (via your connected address) what balances exist and then reading token contracts. If the device's Ethereum app has "Contract data" disabled, the device will refuse to interact with contract-based tokens — so MEW can't read or sign token-related operations. Enabling Contract Data in the device Ethereum app usually resolves this. (This behavior is documented in device support articles.)
If enabling Contract Data doesn’t help, check these concrete steps:
Related internal pages: erc20-tokens, troubleshooting-connection.
Why do addresses sometimes not match between MEW and other wallet software? Because of derivation paths. Most wallets follow BIP-44 but use different account indices. MEW offers options when you connect a hardware wallet (Ledger Live vs Legacy/Default). Try the alternate derivation selection in MEW to find the address with your funds. If you have many accounts, MEW will scan multiple indexes; still, manual selection sometimes helps.
If you use a passphrase (the so-called 25th word), addresses will be different on each passphrase. That explains many "missing funds" cases. See passphrase-25th-word and derivation-paths.
Enabling Contract Data is functionally necessary to interact with tokens and many smart contracts. But enabling it means the device will display contract details so you can confirm them. That’s a security trade-off you should accept if you use tokens. I believe enabling Contract Data is reasonable for token users, but only after verifying transaction contents on-device.
Always update firmware and app versions from official sources, and verify firmware signatures when possible. A firmware or app update can fix compatibility issues (and sometimes change user experience), but it never and should never change your seed phrase or make funds inaccessible if you have a recovery phrase. For update guidance see firmware-updates and verify-firmware.
If you use a passphrase, write it down reliably. Losing the passphrase is like throwing away one of your vault keys. See passphrase-25th-word and seed-phrase.
If the connection still fails after the above:
And if nothing works, export the receiving address (without connecting the hardware wallet) to confirm funds are associated with that public address; that helps isolate whether the issue is device-facing or address-facing.
Who this setup is good for:
Who should look elsewhere:
External references used while testing and writing:
MEW + Ledger Nano S flows work reliably once you understand three things: open the Ethereum app on the device, enable Contract Data if you use tokens, and pick the correct derivation path or account index. If tokens are missing, add them manually in MEW or verify you’re on the right network. In my experience, the gap between "it doesn't show up" and "fixed" is usually one or two of these checks.
Next steps: follow the setup checklist above, then review backup-and-recovery and passphrase-25th-word so your recovery plan matches how you actually use the device.
If you still have trouble, check the official MEW help center and the device support pages (linked above), and consider consulting the troubleshooting pages on this site.
Want step-by-step device setup for a Nano S or other models? See the model-specific guides: nano-s-guide, nano-s-unboxing-setup, nano-x-guide.
But remember: always confirm URLs and firmware sources before entering any sensitive information.