MetaMask Swap Troubleshooting — Failed Swaps & Connection Errors
Table of contents
Quick checklist — first things to try
If a swap fails or you see an error like "swap failed metamask is having trouble connecting to the network", start with these quick checks (fast, practical, and often effective):
- Confirm the wallet is on the correct blockchain (Ethereum mainnet vs an L2 or testnet).
- Check you have native token for gas (ETH on Ethereum, native token for the chain).
- Refresh the dApp page and reconnect the site in the wallet's connected sites list (manage-connected-sites).
- Try switching RPCs (return to default network or choose an alternate public RPC).
- If using a hardware wallet, make sure the device is unlocked and the chain app is open.
I've been using swaps daily, so I try the checklist in under two minutes before doing anything deeper. And yes, many failures are resolved here.
Common error messages and what they mean
| Error shown |
Likely cause |
Quick fix |
| "Swap failed" (generic) |
Reverted smart contract call (insufficient output amount, slippage, or reverted logic) |
Increase slippage tolerance slightly or use a different route; check token decimals/balances |
| "Is having trouble connecting to the network" |
RPC node timeout or wrong chain selected |
Switch RPC / check connectivity / reset account in settings |
| "User denied transaction" |
Signature not confirmed on device or wallet |
Confirm on device (Ledger) or approve in wallet UI |
| Pending/queued transactions never mined |
Low priority fee or nonce collision |
Speed up/cancel pending tx or set higher priority fee |
(Placeholder image: )
Why do these happen? Networks and dApps expect precise conditions: the right chain, enough gas, and either a valid signature or a successful contract call. If any piece is out of sync the swap can revert.
Step-by-step fixes: browser extension (desktop)
- Confirm network and balance. Make sure MetaMask is set to the chain your dApp expects. Check you have enough native token for gas.
- Switch RPC temporarily. Open network dropdown, choose the default RPC or add a known public RPC — then retry the swap.
- Clear cached data for the extension: Settings → Advanced → Reset Account (this clears transaction history but not keys). Use this if you see stale pending transactions. (Back up your seed phrase before removing the extension.)
- Check approvals. If the dApp requires a token approval transaction first, ensure it succeeded. Visit revoke-approvals for more on managing allowances.
- If the dApp shows a large price impact, increase slippage tolerance sensibly (0.5–1% vs 10% depends on token liquidity).
If none of this helps, open the browser console for the extension and look for JSON-RPC errors (see internal-json-rpc-errors).
Step-by-step fixes: mobile app & WalletConnect
Swap failures on mobile often stem from the in-app browser or WalletConnect session issues.
- Update the mobile app to the latest version and clear the dApp browser cache. Re-open the dApp from the wallet's browser.
- If using WalletConnect, re-establish the session: disconnect, scan the QR or reopen the deep-link from the dApp.
- Check mobile network and airplane mode. Sounds obvious, but mobile connections drop mid-signature.
Swap failures metamask mobile are frequently fixed by toggling the connection and confirming the signature on the phone screen. But be cautious: never share your seed phrase when troubleshooting.
Ledger and hardware wallet specific problems (common search: "cant swap on uniswap from ledger on metamask")
Common cause: the hardware device isn't ready to sign the contract interaction. Another cause: the wrong chain app is open on the device.
Step-by-step for Ledger + MetaMask:
- Unlock your Ledger and open the matching blockchain app (e.g., Ethereum app for an Ethereum swap).
- Ensure firmware and the app on the Ledger are up to date.
- Connect the device using the supported method (USB for desktop, Bluetooth for compatible setups) and re-add the hardware account in MetaMask if needed (ledger-setup).
- When MetaMask prompts to sign the transaction, confirm on the Ledger. Some complex contract calls require enabling additional options (check the device prompts carefully).
Searches like "cant swap on uniswap from ledger on metamask" often point to step 1 or 3 above. If problems persist, see ledger-troubleshoot and swap-ledger-issue.
Gas, slippage, and token approval causes of failed swaps
- Gas estimation can be off during spikes (EIP-1559 base fee rises). If priority fee is too low your tx can be dropped. Try a higher priority fee or a different gas preset. (See gas-fees-eip1559 for the mechanics.)
- Slippage: Automated market makers will revert if price moves beyond your tolerance. Increase tolerance or refresh quotes.
- Token approvals: On first-time swaps with a new ERC-20 token you may need to approve token spending. If approval is blocked (hardware wallet prompt not confirmed) the swap will fail.
Table of common fixes: see the first table above. I once left approval unconfirmed and paid two gas fees—lesson learned.
Advanced diagnostics: RPC, nonces, and tx simulation
- Check JSON-RPC responses for errors (method and error object). If the network RPC is returning 5xx or timeouts, MetaMask can't relay transactions.
- Nonce collisions: if you have a stuck transaction with a low gas price, subsequent transactions may never be mined. Use the wallet's "speed up" or "cancel" feature (or replace with identical nonce and higher gas).
- Use transaction simulation (or the dApp’s quote tools) to see why a swap reverts before spending gas. See tx-simulation for tools and steps.
Advanced users can switch to a different RPC provider or run a temporary node to rule out provider-side throttling. (But keep the device secure.)
Preventive tips and best practices
- Keep the device and wallet app up to date. Firmware matters.
- Keep a small gas buffer in the native token so signed transactions can be executed.
- Revoke unused token allowances periodically (revoke-approvals).
- Back up your seed phrase securely before any reinstall or reset (seed-phrase-backup-and-recovery).
A good mental model: treat a swap like a bank transfer with three steps — check identity (wallet), check funds (balances), and confirm the transfer (signature on a device). If any step fails the bank returns the payment.
FAQ - quick answers to common questions
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient for daily DeFi activity but carry greater risk than hardware-only storage. For large holdings, split funds and use a hardware wallet for cold storage. See security-overview.
Q: How do I revoke token approvals?
A: Use the wallet’s approvals page or a reputable revoke tool. Confirm on your device and keep records. See revoke-approvals.
Q: What happens if I lose my phone?
A: Restore your accounts on a new device using your seed phrase (never share it). Read lost-phone and seed-phrase-backup-and-recovery.
Conclusion & next steps
Swap failures and connection errors are frustrating. But most are solvable with the checklist above: confirm network and balances, check approvals, and make sure hardware devices are unlocked and the right app is open. If you want a deeper walkthrough, start with how-to-swap and then check swap-gas-optimization for tuning your transactions. In my experience, a methodical approach saves time and gas.
If you still see specific errors, copy the exact message and consult the related troubleshooting pages like ledger-troubleshoot or metamask-extension-troubleshooting before contacting support.
Want more step-by-step guides? See the Swap overview and detailed guides: swap-overview • how-to-swap.
And remember: back up your seed phrase first, then troubleshoot.