Why does connecting work on desktop but not mobile?

Mobile browsers usually cannot talk to a wallet extension, so the connection goes through the wallet app's built-in browser or a WalletConnect session instead. Opening the site inside your wallet app fixes most mobile cases.

Is it dangerous if a site keeps asking me to connect?

Repeated prompts are usually a dropped session rather than an attack. What should concern you is a site escalating from connect to asking for a key or an approval.

Do I need to disconnect from sites afterwards?

Good hygiene, and it costs nothing. The bigger cleanup is revoking token approvals, since those grant real authority while a connection grants none.

Wallet will not connect to Pump.fun? Work through these

Connection failures have maybe six causes, and five of them take under a minute to rule out.

Work down the list rather than guessing, and check the last section before you retry anything.

Start with the boring ones

Is the wallet unlocked? A locked extension often fails silently rather than prompting. Open it, unlock, retry.

Is the popup blocked? Connection opens a window. Browsers block those, sometimes without an obvious indicator. Check the address bar for a blocked-popup icon.

Is another wallet interfering? Multiple Solana extensions installed means they compete to inject themselves, and the one you want may not win. Disable the others temporarily and retry.

Three checks, under a minute, and they resolve most cases.

Session and cache problems

If the basics pass, the connection state itself is probably stale.

Wallets store connection sessions in your browser. A session that expired or corrupted leaves the site thinking you're connected while the wallet disagrees, which produces silent failures with no error message anywhere.

Fix it by disconnecting the site inside your wallet's connected-sites list, then clearing site data for that domain, then reconnecting fresh. Sounds heavy-handed and takes 30 seconds.

Mobile is a different problem

Most mobile connection failures aren't failures at all. They're a missing path.

Mobile browsers generally can't reach a wallet extension the way desktop does, so the connection has to go through either your wallet app's built-in browser or a WalletConnect session that bridges the two.

Easiest fix: open the wallet app, find its browser, and navigate to the site from inside it. Then the wallet and the page are in the same process and connection works normally.

If a site supports WalletConnect, the other route is scanning or deep-linking from the site into your wallet app, approving there, and being returned. That's why our console uses WalletConnect rather than only injected detection, since injected-only sites simply don't work on phones.

Network and RPC issues

Occasionally the wallet connects and then everything else fails.

Your wallet talks to Solana through an RPC endpoint, and public endpoints get congested or rate-limited. Symptoms: connection succeeds, balances show as 0 or don't load, transactions hang without confirming.

Switching your wallet's RPC to a different endpoint in settings resolves it. Solana RPC errors covers the wider category.

When it's the site

Sometimes the problem genuinely isn't yours.

Test by connecting the same wallet to a different Solana site. Works elsewhere and fails on one place? That's a site-side issue and no amount of clearing your cache fixes it.

The security check before you retry

Now the part worth more than the troubleshooting, because connection trouble is exactly when people get careless.

You're frustrated, you've retried 4 times, and a helpful-looking prompt appears offering to fix it. That's the moment drainers are built for.

So before you approve anything during a connection problem:

Read the domain character by character. Not the page, the address bar
Confirm you navigated there yourself rather than following a link from a DM
Remember that connecting shares a public address and nothing else
Reject anything asking for a seed phrase, a private key or a token approval

No connection problem is ever solved by providing a seed phrase. There's no exception, no support tool, and no migration process that needs one. How to spot a wallet drainer covers the shapes these requests arrive in, and what connecting a wallet shares covers why connecting itself is harmless.

The order to work through

Unlock the wallet, check for a blocked popup, disable competing extensions
Disconnect the site in your wallet, clear site data, reconnect
On mobile, open the site inside your wallet app's browser
Switch RPC endpoint if balances won't load
Test the same wallet on a different site to isolate the cause
Never provide a key, whatever the prompt says