- Use a throwaway account funded with small amounts (under $5) on each network to avoid losses. And yes, use test amounts.
- Record the exact environment: mobile OS, browser (Chrome/Firefox), MetaMask extension version, and RPC endpoints used.
- Reproduce the action: send a basic ETH transfer, perform a simple swap with low slippage, or connect to a dApp via WalletConnect.
- Capture logs: on desktop use the browser extension background page console (chrome://extensions → Developer mode → Service worker/Inspect views). On mobile take screenshots and use WebView debug if available.
- Note the dApp and contract addresses involved. (Never share your seed phrase while reporting issues.)
These steps help distinguish whether an error is coming from the RPC node, the dApp, or the wallet itself.
Quick diagnostic checklist
Before deep-diving, run this checklist. Many fixes are one small setting away.
- Is MetaMask updated to the latest release? (extension or app store)
- Are you on the correct network? (EVM-compatible mismatch is common.)
- Is your RPC healthy? Try switching to a public RPC or the default provider in Add networks / custom RPC.
- Do you have a pending transaction? Check the activity list and try cancel or speed up.
- Try reconnecting the dApp: disconnect in MetaMask then reconnect the site (disconnect and remove connected sites).
If the wallet still appears to be metamask not working, continue below.
Common errors and fixes
internal json rpc error metamask mobile
Why it happens: This typically means the wallet failed to get a response from the RPC node the app is using. On mobile this shows up after submitting a transaction or when switching networks.
Fixes I test (repeatable):
- Switch networks to a known-good RPC (e.g., a major public RPC) and retry the action.
- Restart the MetaMask app and force stop the app process in Android settings.
- Clear any custom RPCs that might be misconfigured: open network list → Edit network → Remove → add a validated RPC via Add networks / custom RPC.
If error persists, export the transaction data and check the RPC node status (many public nodes publish status pages). I believe collecting the app logs helps support teams debug.
metamask transaction failed — common causes
A "metamask transaction failed" message can come from several layers: insufficient gas, failed smart contract require() checks, or nonce mismatch.
How I debug:
- Check the transaction receipt (Etherscan or block explorer). If status = 0 the contract reverted. The revert reason (if available) points to the issue.
- If reverted due to token allowance, confirm the dApp has a proper token approval or revoke and re-approve with the correct amount (token approvals and revoke).
- If gas spike caused failure, estimate gas with a higher priority fee and retry using "speed up".
metamask pending transaction — how to clear or speed up
Pending transactions occur when the mempool hasn't mined your transaction, often because of low priority fees or a stuck nonce.
Steps to clear:
- Use "Speed up" to resubmit with higher gas fees. If you need a more aggressive fix, submit a zero-value transaction with a higher nonce to replace the stuck tx (advanced).
- If multiple pending transactions exist, note the nonce and use a manual nonce replace method (desktop extension) or see Cancel or replace transaction.
If you're on an L2 (Layer 2), check L2 gas rules. See Gas fees, EIP-1559 and L2.
metamask extension blocked / metamask background connection unresponsive
Symptoms: pages say the extension is blocked, sites can't detect your wallet, or the extension UI never loads.
Common causes and fixes:
- Browser blocked the extension content scripts. Check extension permissions and allowlisted sites.
- Another privacy extension is interfering. Temporarily disable ad-blockers or script-blockers and reload the dApp.
- Browser blocked background pages: open the extension details and inspect the service worker logs to find errors.
If you see "metamask extension blocked" try reinstalling the extension after exporting your seed phrase (backup first). But first try a browser profile without other extensions.
metamask can't import account
If MetaMask can't import account using a private key or seed phrase it often means a format issue or the phrase was typed incorrectly.
Checklist:
- Confirm the seed phrase has the correct word count (12 or 24) and correct spacing.
- Avoid copying extra whitespace or hidden characters. Paste into a plain text editor first.
- If importing a private key, ensure the string begins with or without 0x as required by the import dialog.
See full import guides: Import wallet to MetaMask and Import private key.
Network, gas and RPC diagnostics
RPCs, gas estimation, and EIP-1559 behavior matter for DeFi. If you consistently see bad gas estimates, test by switching to a public RPC and comparing estimated base fees. I run small test transactions on each network to compare. (Yes, it takes time.)
Tip: When testing swaps I use an aggregator and a tiny amount on each chain so I can compare real-world gas and slippage.
WalletConnect, dApps and connection troubleshooting
If a dApp won't connect, try this sequence:
- Disconnect the dApp from MetaMask. (See Disconnect and remove connected sites.)
- Reconnect via WalletConnect instead of injected provider to see if the issue is provider-specific (WalletConnect and mobile dApps).
- If a dApp asks for unusual approvals, revoke them and inspect with a token-approval tool.
Who MetaMask is for — and who should look elsewhere
Who it fits: users who want a flexible, non-custodial software wallet for daily DeFi interactions across EVM-compatible chains and L2s. In my experience it's the most convenient hot wallet for experimenting with swaps, staking, and dApps.
Who might look elsewhere: if you need enterprise-level transaction batching, advanced account abstraction features, or the highest-security private key storage for large holdings (consider hardware integrations—see Ledger step-by-step integration).
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient for daily DeFi. But they expose private keys to your device. For significant amounts, combine MetaMask with hardware devices or move funds to cold storage.
Q: How do I revoke token approvals?
A: Use the token approvals tool in MetaMask or a third-party revocation tool. See the guide: Token approvals and revoke.
Q: What happens if I lose my phone?
A: If you have your seed phrase, you can restore on a new device. If not, funds may be irrecoverable. See Backup and recovery — seed phrase.
Conclusion and next steps
If MetaMask is not working for you right now, follow the diagnostic checklist above, reproduce the error using a test account, and collect logs before making changes. But don't rush—back up your seed phrase before reinstalling. If you want step-by-step setup or import instructions, check Create MetaMask wallet and Import wallets overview.
If the problem persists after these checks, consider reaching out to official support with your environment details and logs. For more guides on gas and transaction management, visit Gas fees, EIP-1559 and L2 and Cancel or replace transaction.
Thanks for reading. If you found one of these fixes helpful, try the step-by-step reproductions I described—repeating them is the best way to learn how MetaMask behaves across networks. And if you want more troubleshooting pages like this, check the main troubleshooting hub: Troubleshooting.
