Who this guide is for
This is for people using a hardware wallet with MyEtherWallet (MEW) to send Ethereum or ERC-20 tokens who hit errors like a connect timeout, a frozen confirm screen, or a server rejection. I’ve been using hardware wallets since the 2017–2018 cycle and I’ve seen these problems crop up often with similar root causes. If you prefer a walkthrough-style solution set instead of generic troubleshooting, this is for you.
Quick checklist before you start
Do these simple checks first. They fix many issues quickly.
- Close any wallet apps that might be talking to your hardware wallet (example: desktop app managers). Try again. Short and effective.
- Use a supported browser (Chromium-based browsers are common choices). Try a different browser if you get errors.
- Use a good USB cable and direct port (avoid hubs). Reconnect. Reboot if needed.
- Unlock the device and open the Ethereum app on the hardware wallet before connecting to MEW.
- If you use a passphrase (25th word), confirm you’re using the same passphrase on both device and MEW.
If those don’t work, keep reading. And yes, I’ve seen stubborn cases where the culprit was a dirty USB port.
Common symptoms you may see (and what they mean)
- myetherwallet ledger timeout — MEW cannot complete the handshake with the device. Could be a browser/USB issue or another app holding the connection.
- ledger mew froze — The device displays a confirm screen and never moves forward. Often a large contract call, or the host side timed out.
- myetherwallet ledger nano froze on confirm — The transaction data exceeds what the web transport expects (or there’s a device/firmware mismatch).
- ledger wallet on myetherwallet timed out — The connection window closes before signing completes. Try a different connection method.
- ledger ethereum transaction rejected by the server — MEW’s node or your selected node rejected the raw transaction (nonce, gas, or node policy problem).
Why does this happen? A browser blocking WebUSB/WebHID, an outdated firmware or app, or a mismatched passphrase/derivation path are usual suspects.
Step-by-step: Desktop fixes (How to) — myetherwallet ledger timeout & freeze
What I've found in testing: most desktop issues are environmental. Follow these steps in order.
- Close wallet manager apps and browser extensions that touch hardware wallets (ad blockers, privacy extensions can interfere).
- Reboot the computer. I know it sounds basic. It works.
- Use a direct USB port and a short cable. Try another port if needed.
- Open the Ethereum app on your hardware wallet and ensure the device shows that app’s home screen.
- In MEW choose the hardware wallet path and select Ledger (or the hardware option MEW shows). Allow the browser to access the USB device when prompted.
- If MEW times out, try another browser (Edge/Chrome vs Firefox). Some browsers use different transport layers (WebUSB, WebHID). Trying both can resolve the handshake.
- If the device still freezes on the transaction confirm screen, cancel the connection, restart the wallet app on your device, and attempt the send again with a smaller gas limit or simpler transaction (if possible).
If you want a deeper walkthrough on connecting a hardware wallet to third-party wallets, see our app integration notes: MEW integration guide and the general desktop setup guide.
Step-by-step: Mobile / OTG fixes (How to)
Mobile adds variables. USB OTG adapters and phone USB permissions often cause trouble.
- Use a verified OTG cable and a phone that supports OTG host mode.
- Close mobile wallet apps that might hold the device. Reconnect.
- Open the Ethereum app on the device first, then connect.
- If the connection times out, try using a desktop. Mobile browsers and WebUSB support can be inconsistent.
But sometimes the simplest solution is to switch to desktop for a complicated contract interaction.
When MEW reports "transaction rejected by the server"
This message usually means the node that MEW is using refused the transaction. Common causes:
- Nonce mismatch: the node expects a different transaction sequence number. This happens when a previous transaction is pending.
- Gas too low: miners refuse to include the tx.
- Node policy or temporary outage: the node may be overloaded or rate-limited.
What to do (step-by-step):
- Check the account’s pending transactions on a block explorer to see the nonce.
- If a transaction is stuck, send a replacement transaction using the same nonce with a higher gas price (advanced). Only attempt this if comfortable with custom nonce settings.
- Switch MEW to a different node or custom RPC (MEW supports custom nodes) and retry the broadcast.
For more on transaction problems and how to replace or cancel a stuck transaction, see transaction-issues.
Firmware, secure element, and app updates
Firmware matters. The secure element and the firmware on the device handle signing and attestation. If the firmware or the Ethereum app on the device is out of date you can see incompatible behavior with web wallets. I always check firmware first.
Steps:
- Check and update firmware using official update procedures. See firmware-update-guide.
- Update the Ethereum app on the device through the manager app.
- After updating, retry the MEW connection and keep an eye on the device screen for prompts.
Firmware updates occasionally change the way data is presented on the device, which can affect third-party wallet compatibility. If an update coincides with a new failure, re-check MEW’s connection settings.
Passphrase (25th word) and derivation path mismatches
If you use a passphrase (25th word) the addresses you see depend on that passphrase. MEW will show a different account if the passphrase on the device and in MEW don’t match. The bad news is this is a common source of confusion. The good news is it’s straightforward to verify: make sure the passphrase entry method (on-device or via companion app) is consistent.
Derivation path differences can also hide funds from view. MEW offers advanced account selection; try different derivation path options if an expected address doesn’t appear. Read more on passphrase usage in our passphrase (25th word) guide and on seed safety in seed phrase management.
Symptom vs. fix quick reference (table)
| Symptom |
Quick fix |
| myetherwallet ledger timeout |
Close wallet apps, try another browser, use direct USB, open Ethereum app on device |
| ledger mew froze |
Cancel and restart device app, update firmware, attempt simpler tx |
| myetherwallet ledger nano froze on confirm |
Try another browser, check cable/USB, update device app |
| ledger wallet on myetherwallet timed out |
Switch WebUSB/WebHID transport or use desktop instead of mobile |
| ledger ethereum transaction rejected by the server |
Check nonce on block explorer, switch node/RPC, resend with higher gas |
FAQ: real user questions
Q: Can I recover my crypto if the device breaks?
A: Yes — if you have your seed phrase and passphrase (if used). See restore-recovery-phrase.
Q: Is Bluetooth safe for signing transactions?
A: Bluetooth adds an attack surface compared with USB. It can be convenient, but I recommend assessing your threat model first and following the guidance in bluetooth-usb-nfc-security.
Q: What if MEW times out repeatedly?
A: Try another browser and close any app that might hold the device. Update firmware and the Ethereum app, then retry.
Q: Should I use a passphrase?
A: It depends on your threat model. A passphrase gives extra compartmentalization but adds recovery complexity. Read passphrase-25th-word-guide.
Conclusion & next steps / CTA
Connection timeouts and frozen confirms are almost always environmental: browser, USB, firmware, or node. Troubleshoot in that order. In my testing the fastest wins were closing competing apps, using a direct USB port, and updating firmware. If you need step-by-step setup or a full refresh after a firmware change, see setup-ledger-step-by-step and firmware-update-guide. For persistent issues, collect connection logs (browser console + MEW error) and reach out to MEW’s support with the details — they can check node logs.
If you want more targeted fixes for other wallets or multisig setups, check our pages on using-ledger-with-wallets and multisig-for-ledger.
Stay methodical. Start simple. And if you get stuck, come back here — this guide will help you narrow the root cause quickly.
