Quick summary: who this guide is for
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.
How MEW + hardware wallet integration works
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.
Step-by-step: connect your Ledger Nano S to MEW
- Plug the device into your computer with a data-capable USB cable. Use the same cable you use for device management. Short cables are better.
- Enter your PIN to unlock the device, then open the Ethereum app on the device. The app must be open before MEW connects.
- In MEW (web): choose "Access My Wallet" → "Hardware" → select the Ledger option. Follow the on-screen prompts.
- MEW will scan for addresses. Select the address/account you want to use.
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.
Common issues and quick fixes (tokens not loading, connection errors)
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.
Why tokens sometimes don’t appear (and how to fix visibility)
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:
- Confirm you’re on Ethereum Mainnet in MEW. Testnets and other EVM chains won’t show ETH/ERC-20 balances.
- Add the token manually in MEW using the token contract address, symbol, and decimals. MEW will then display the token.
- If the token is on another EVM chain (BSC, Polygon), connect MEW to that network and use a compatible derivation path or bridge — MEW's network selector controls which chain balances are fetched.
Related internal pages: erc20-tokens, troubleshooting-connection.
Derivation paths & multiple Ethereum accounts
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.
Security considerations: contract data, passphrases, firmware
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.
Advanced troubleshooting checklist
If the connection still fails after the above:
- Close any manager software that might hold the device (desktop companion apps). Try again.
- Use a different browser. Chrome, Brave, and Firefox often behave differently with WebUSB; try an alternative.
- Try a different USB port and a different USB cable. Some cables are charge-only.
- Confirm the Ethereum app is open on the device. Unlock PIN first.
- Update the Ethereum app on the device and the device firmware (but only via official channels). See firmware-updates.
- Disable privacy extensions or adblockers temporarily (these can block the MEW site from reaching the device).
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 should use MEW + hardware wallet, and who should look elsewhere
Who this setup is good for:
- Users who want a simple, non-custodial desktop interface to manage ETH/ERC-20 tokens while keeping private keys offline.
- People comfortable with occasional manual steps (enabling Contract Data, adding tokens, handling derivation paths).
Who should look elsewhere:
- Users who need an integrated multisig workflow for high-value treasury management (consider multisig solutions; see multisig and multisig-compatibility).
- Users who want mobile-only access without a desktop bridge; direct mobile flows vary by device (see connecting-desktop-mobile).
Further reading and internal resources
External references used while testing and writing:
- MEW documentation and help center (official MEW support pages)
- Device support documentation on using hardware wallets with MEW (device vendor support articles)
Conclusion & next steps
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.
