Quick summary
This guide explains how MetaMask (browser extension + mobile app) connects to DeFi dApps, why it sometimes shows "not connected", and practical fixes. I use MetaMask daily for swaps and NFT marketplaces, so these are hands-on tips — not just theory. What I've found: most connection failures are either a locked wallet, network mismatch, or a session/permission issue.
![Screenshot placeholder: MetaMask connection prompt]
How MetaMask connects to dApps (the mechanics)
Three common connection methods power most workflows:
- Injected provider (browser extension): the dApp detects window.ethereum and asks for permission (eth_requestAccounts). Granting that permission creates a connected session.
- Mobile in-app browser: the MetaMask mobile app includes a built-in dApp browser. Open the site there and the wallet injects itself into the page — same flow as the extension but on mobile.
- WalletConnect (bridge): dApps show a QR code or deep link. You scan from MetaMask mobile (or any WalletConnect-capable wallet) and approve a session. This is a proxied connection using a bridge relay.
Why does this matter? Because each method has slightly different failure modes. A QR scan can time out. An injected provider can be blocked by browser privacy settings. The app browser depends on the mobile app being unlocked.
Common "not connected" problems and why they happen
Why does MetaMask say not connected? Short answer: the dApp either never received permission or lost it.
Frequent causes:
- Wallet locked. You need to unlock your wallet MetaMask before approving connections. Simple, but common.
- Wrong network. Many dApps expect Ethereum mainnet (or a specific L2). If MetaMask is on Polygon or a testnet, the site will show "not connected." Switch networks and try again.
- Privacy mode / blocked providers. Some browsers block injected providers or third-party cookies. And yes, that can break connections.
- Multiple accounts. The site is connected to one account but you’re viewing another. Switch to the account the dApp knows.
- Stale WalletConnect session. Sessions can expire or fail if the mobile app went offline.
- Browser extension conflicts. Other wallet extensions or developer tooling can interfere.
I once paid gas waiting for a transaction that never went through because the extension was locked after a browser crash. Learn from that mistake.
Step by step: Fix "MetaMask not connected" errors
Step by step. Follow this in order.
- Unlock the wallet. If you see a lock icon, unlock and retry (you need to unlock your wallet MetaMask).
- Check the network. Match the dApp's required network (Ethereum mainnet for most NFT marketplaces).
- Refresh the page. Then click the site's "Connect" button and approve the connection.
- If it still says not connected, open MetaMask > Connected sites (or account menu) and remove/disconnect the site. Then reconnect.
- Try a different account. The dApp may have no permissions for your current address.
- Clear browser cache or disable strict privacy extensions temporarily (ad blockers can block web3 providers).
- For WalletConnect: close the mobile app, re-open, then re-scan the QR code. But sometimes you need to kill the old session first.
- Update MetaMask and the browser/app. Outdated versions can break the handshake.
- If you're using a hardware wallet via MetaMask, ensure the device is unlocked and the correct app (Ethereum) is open on the device.
If the dApp still won't connect, check the dApp's docs or status page. Sometimes the site itself is down.
For extension-specific glitches see extension-troubleshooting. If syncing mobile devices, try mobile-sync-troubleshooting.
Connecting to marketplaces like OpenSea (practical tips)
Why is MetaMask not connecting to OpenSea? Why isn't OpenSea connecting to MetaMask? These questions often boil down to network or permissions.
- Confirm OpenSea's expected network (usually Ethereum). Switch MetaMask to that network.
- Unlock MetaMask and make sure you allow the connection when the browser popup appears. (You need to allow MetaMask mobile on some sites.)
- If you declined the action in your wallet MetaMask, refresh and try again — the site may need a fresh permission request.
Step by step how-to: see how-to-connect-opensea for a full walkthrough including screenshots.
WalletConnect vs in-app browser vs extension (comparison)
| Method |
Device |
Connection method |
Best for |
Pros |
Cons |
| Browser extension (injected) |
Desktop |
window.ethereum injection |
Desktop trading, dApp dev |
Seamless UX, fast approvals |
Blocked by browser privacy settings, requires extension installed |
| Mobile in-app browser |
Phone |
In-app injection |
Mobile NFTs, quick swaps |
Native mobile signing, no QR |
Mobile UI constraints, phone loss is risk |
| WalletConnect |
Desktop + Mobile |
QR / deep link bridge |
Desktop dApps + mobile wallets |
Works across wallets, no extension |
Session expiry, bridge reliance |
This table helps you pick the right flow for your daily routine.
Security notes: approvals, rejected actions, and session handling
Never approve a transaction you don't understand. A signed transaction can move tokens or set a token allowance. If you see a permission you didn't expect, cancel.
- How to revoke: MetaMask shows connected sites, but for token approvals you'll often need a revoke tool or the dApp's revoke UI. See revoke-approvals.
- "You declined the action in your wallet MetaMask" is a real UX state. Declining stops the dApp flow and may require restarting the operation.
- If you lose your phone: treat mobile in-app browser sessions as compromised until you restore the seed phrase to a safe device.
Account abstraction and smart contract wallets are becoming more common (gasless transactions, session keys). MetaMask can interact with those wallets as long as the wallet exposes a compatible provider, but the UX depends on the dApp supporting those standards.
Who MetaMask fits — and who should look elsewhere
Who this wallet is best for:
- People who use DeFi and NFTs on Ethereum and EVM-compatible chains.
- Users who want a flexible hot wallet across desktop and mobile.
- Developers and power users who need custom RPCs and network switching.
Who should look elsewhere:
- Users who require built-in token-approval revocation in the wallet UI (some wallets offer dedicated tools).
- Users who need native Bitcoin or non-EVM-first chains without a bridge. See solana-tron-near and bitcoin-support pages for alternatives.
FAQ — real questions people search for
Why does MetaMask say not connected / why is MetaMask not connected?
Typically because the dApp doesn't have permission or your wallet is locked. Unlock, set the right network, disconnect and reconnect the site.
Why is MetaMask not connecting to OpenSea / why isn't OpenSea connecting to MetaMask?
Most often a network mismatch or a declined permission. Switch to Ethereum mainnet, unlock MetaMask, then approve the connection. See how-to-connect-opensea.
Why is DeFiSaver / Wonderland not connecting to MetaMask?
Those are dApps that expect specific chains or smart-contract interactions. Check the dApp's network, revoke stale approvals, and confirm WalletConnect sessions if you're using that path.
What type of wallet is MetaMask Web3bet?
MetaMask is a non-custodial software wallet (a hot wallet) with an injected provider for dApps. It supports EVM-compatible networks and custom RPCs.
"You need to unlock your wallet MetaMask" / "You need to allow MetaMask mobile"
Those are literal prompts. Unlock the app or approve the permission. Declining the action in your wallet MetaMask halts the dApp call — you'll need to retry.
Conclusion & next steps
Connection problems are almost always fixable. Start with the basics: unlock the wallet, match the network, and approve the request. But sometimes a stale WalletConnect session or a privacy blocker is the real culprit. In my experience, a clean disconnect and reconnect solves the majority of cases quickly.
Read the practical connect guides next: connect-to-dapps and walletconnect-and-mobile-browser. If you're troubleshooting extension issues, try extension-troubleshooting.
Want a step-by-step walkthrough for a specific dApp? Head to the relevant how-to guide (for example, how-to-connect-opensea).
