If MetaMask won't connect, try these very quick steps first. They fix most issues in under a minute.
And yes, sometimes the simplest step — refresh the page — is the fix.
If you need setup reminders, see the extension and mobile guides: install-metamask-extension and install-metamask-mobile-app.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| "MetaMask can't connect to OpenSea" | Wrong network selected, blocked injected provider | Switch to the correct network; allow the site via extension; disable blockers. See connect-opensea |
| "MetaMask can't connect to Ledger" | USB/HID permissions, Ledger app not open, wrong connection mode | Open Ledger app, allow browser access, try WebHID or Ledger Live mode. See connect-ledger-desktop |
| "MetaMask cannot connect to Ethereum mainnet" | RPC outage or wrong RPC entry | Switch to the built-in Mainnet or add a healthy RPC. See connect-to-networks |
| "MetaMask wont connect to BSC" | BSC network not added or wrong chain ID | Add BSC network from guides: add-bsc-network |
| "MetaMask cannot connect to custom RPC" | Bad URL, wrong chain ID, CORS blocks | Re-check RPC URL and chain ID; try an alternate RPC provider. See add-custom-network |
Why does a site not see MetaMask? Usually it comes down to permissions or network mismatch.
Step-by-step:
What I've found: browser profiles quickly reveal whether a conflict is caused by another extension. (I once spent an hour troubleshooting a site that failed only because of a privacy extension.)
If you use mobile, remember that many marketplaces support WalletConnect instead of using an injected provider — see walletconnect-guide for mobile linking tips and connect-opensea-marketplaces for marketplace-specific notes.
Hardware integration adds a layer that can fail: cable, permission, app version, or browser transport.
Common checks:
But don't enable options you don't understand — if Ledger asks for unusual permissions, pause and verify.
Detailed guides: connect-ledger, connect-ledger-desktop, and connect-ledger-mobile. If problems persist, see our troubleshooting hub: ledger-troubleshooting.
If MetaMask cannot connect to Ethereum mainnet the cause is often RPC health or a misconfigured local setting.
Checks and fixes:
For adding or editing networks, consult the step-by-step pages: add-custom-network, add-bsc-network, and other chain guides such as add-polygon or add-arbitrum-optimism.
Desktop extension tips:
Mobile app tips:
If simple fixes fail, a little debugging helps. Open development tools on the page and watch for errors mentioning "rpc", "network", or HTTP status codes. Common messages point to:
You can also temporarily switch to a different browser or create a clean profile to isolate the problem. Developers may want to check developers-connect and metamask-api-connect for provider behaviors and integration notes.
Resetting your MetaMask account clears transaction history (it does not erase your accounts or seed phrase). Only reset as a last resort for stuck transactions. Reinstalling is safe if you have a verified seed phrase and private keys saved in secure storage. See backup-recovery and backup-recovery-seed for recovery details.
If nothing works, collect logs and specific error messages before contacting support. That makes troubleshooting faster.
Who it's best for:
Who should look elsewhere:
Q: Is it safe to keep crypto in a hot wallet? A: Hot wallets are convenient for daily use. They are less secure than cold storage. I keep small, active balances in a hot wallet and larger holdings in hardware wallets (or cold storage). See security-best-practices.
Q: How do I revoke token approvals? A: Use MetaMask or a dedicated approvals tool to review and revoke allowances. Revoking removes unlimited token approvals that dApps requested. See token-approvals-revoke.
Q: What happens if I lose my phone? A: If you have your seed phrase backed up, you can restore your wallet on another device. If you didn't, the wallet and private keys are lost. See recovery steps: lost-phone-recovery and backup-recovery-seed.
When MetaMask won't connect the issue is almost always one of three things: permissions, network/RPC, or hardware transport. Start with the quick checklist, then move through the targeted steps above. If you prefer guided walk-throughs, try the step-by-step guides for connecting Ledger or for adding networks like BSC and Polygon.
If problems persist, collect the error text (or console logs) and consult the related troubleshooting articles listed throughout this guide. I believe clear logs make support and self-troubleshooting much faster, and in my experience the fix is often just a single misconfigured setting away.
If you want a specific walkthrough for a problem you see on-screen, paste the exact error or take a screenshot and follow the relevant page: troubleshooting-connect (this page) and common-error-messages.
Good luck — and remember to keep your seed phrase offline and secure before trying any reinstall or reset.