Skip to main content
Blockfront

Crypto markets, protocols and policy

cbridge wallet not connecting: Fix the wallet handshake

cBridge wallet not connecting? Resolve extension clashes, hidden approvals, stale sessions or unsupported networks, then reconnect and confirm your address appears.

Blockfront Editorial

2 min read

cbridge wallet not connecting: Fix the wallet handshake

For a first bridge, cBridge often fails to appear connected because the browser exposes the wrong wallet, hides its approval prompt, or the wallet is on an unsupported network. The site reads a wallet provider from the browser, and the wallet must approve the connection before its address appears.

cBridge usually fails at the browser handshake

Start with the browser and wallet connection before troubleshooting a transfer. These common causes have distinct signs and fixes:

  • Competing extensions: MetaMask and Coinbase Wallet, for instance, can both inject a browser provider, and one may take precedence. Disable the wallet extension you are not using, reload the page, then connect again.
  • Hidden approval: A locked wallet or blocked pop-up can leave the approval prompt out of sight. Unlock the wallet and open its extension manually to look for a pending request, then approve it.
  • Unsupported network: The wallet can be connected to a chain the app does not list. Switch the wallet to a network shown as supported, such as Ethereum or Arbitrum, and retry.
  • Stale WalletConnect session: A mobile wallet linked by QR code may have an expired session. End the old session, start a fresh connection, and scan the new QR code in the wallet.

The Celer bridge moves supported assets across networks, but the wallet handshake happens before any transfer begins. Opening cBridge gives you the place to retry that connection after fixing the browser or wallet issue.

Reset the site connection if the wallet says connected

A wallet can show a connection while the page still has a stale or mismatched session. Remove the site from the wallet’s Connected sites list, reload the page, and connect from scratch so the wallet can send a fresh approval and address.

For WalletConnect, disconnect the session in the mobile wallet as well before scanning a new QR code. This clears the old link on both sides and lets the browser request a new session.

If the same issue remains, check which account and network are active in the wallet, then try a fresh browser tab with only the intended extension enabled. Once the address appears in the page and the wallet is on a supported network, confirm that it is the account you want to use; that leaves the connection ready for transfer setup.