A user installs Rabby Wallet on their browser, attempts to connect a mobile wallet through WalletConnect, scans the QR code from their phone, and waits. The connection either never completes, times out mid-session, or drops immediately after pairing succeeds. These failures are frustrating because the error messages are often generic—”connection failed,” “pairing timeout,” “network unreachable”—without clarity on whether the problem originates from the browser extension, the mobile wallet, the network layer, or the WalletConnect relay infrastructure itself.

The issue is common enough that support channels receive repeated reports, yet the root cause varies case by case. A rabby wallet download that works flawlessly for some users produces persistent connection failures for others, not because the software is broken, but because diagnostic steps must follow a specific sequence to isolate which component in the connection chain has failed. The goal of this guide is to provide that sequence, starting with the simplest verifications and progressing to more complex resets.

Understanding the WalletConnect connection chain

Before troubleshooting, it helps to understand what happens during a successful connection. When you attempt to connect Rabby Wallet to a mobile wallet application via WalletConnect, several components must work together: the browser extension itself, the mobile wallet app, the WalletConnect relay service, your local network, and the internet connectivity on both devices. A failure in any one of these components will break the entire chain.

The process typically begins when the desktop user (via Rabby Wallet) generates a QR code or a connection URI. The mobile user scans that code or pastes the URI into their mobile wallet app. Both devices then establish a communication channel through WalletConnect’s relay, which acts as an intermediary server. This relay does not hold your private keys or see transaction details; it merely routes encrypted messages between the two wallets. However, if the relay is overloaded, experiencing downtime, or if either device cannot reach it, the pairing fails.

The connection also depends on a shared network understanding between the devices. If the desktop browser and mobile phone are on completely different internet paths, or if one device is using a restrictive network (corporate firewall, school network, carrier-level blocking), the relay communication can be blocked. Additionally, once paired, the connection must be maintained; if network conditions change during the session—switching from WiFi to cellular, a brief internet interruption, or even a brief DNS resolution delay—the session can drop.

Step one: Verify both wallets are genuine and up to date

Before troubleshooting connection problems, ensure that you have installed legitimate versions of both applications. A phishing clone of Rabby Wallet or a mobile wallet can appear identical but deliberately fail to connect, either as a scam mechanism or because it lacks proper WalletConnect integration. Verify the rabby wallet download from the official source by checking the browser extension URL (it should direct to a recognizable official domain or app store listing).

For Rabby Wallet, confirm that your browser extension version is current. Open the extension and check if an update notification appears. For mobile wallets, open your phone’s app store (Apple App Store or Google Play Store) and search for the specific app (MetaMask, Trust Wallet, TokenPocket, imToken, Math Wallet, Rainbow, Bitget Wallet, or Zerion). If an update is available, install it before attempting to connect again.

Outdated versions may have incompatibilities with WalletConnect’s relay protocol or lack certain bug fixes that prevent pairing from completing. This is particularly common after WalletConnect releases major updates to its v2 protocol. A wallet login that failed last week may succeed after both applications have been updated because the connection layer has been improved on both sides.

Step two: Test the QR code scanner in isolation

A surprising number of WalletConnect failures stem from QR code scanning issues rather than from the connection itself. The mobile phone’s camera may be failing to capture a clear code, the mobile wallet’s scanner may have permission issues, or the screen displaying the QR code may be too dim or reflective.

Start by ensuring that your mobile wallet has camera permissions granted. Go to your phone’s settings, find the app permissions section, and verify that the mobile wallet application (MetaMask Mobile, Trust Wallet, etc.) has permission to access the camera. If permission is denied, grant it and restart the mobile wallet app.

Next, test the QR code scan in good lighting. Position the camera so that the QR code fills most of the frame, hold steady for 2–3 seconds, and wait for the scanner to register the code (it should produce a visual or audio feedback). If the scanner fails repeatedly, try manually copying and pasting the connection URI instead of scanning. Rabby Wallet typically provides a button or option to copy the connection URI as text; open that text in your mobile wallet’s WalletConnect connection screen and paste it rather than scanning.

If manual pasting succeeds while scanning fails, the problem is the scanner, not the WalletConnect connection logic. If manual pasting also fails, proceed to the next diagnostic step.

Step three: Verify network connectivity and DNS resolution

Both your desktop and mobile device must have working internet connectivity, and both must be able to reach the WalletConnect relay servers. Test connectivity by opening a web browser on both devices and visiting a simple website such as example.com. If either device cannot load any web content, fix the network connectivity on that device first (reconnect to WiFi, enable airplane mode and disable it, or restart your router) before attempting the wallet connection again.

A more subtle connectivity problem is DNS resolution failure. Even if you can browse the web, your device may struggle to resolve the hostname of the WalletConnect relay. To test this, use a DNS lookup tool on your desktop (on Windows, open Command Prompt and type `nslookup relay.walletconnect.com`; on Mac, use Terminal with the same command). The response should return an IP address. If it returns “host not found” or times out, DNS resolution is failing.

If DNS resolution fails, try changing your device’s DNS server to a public alternative such as Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1. On most home networks, this is available in WiFi settings under “advanced options” or “DNS settings.” Some corporate or school networks may block alternative DNS servers; if so, you may need to test from a different network to isolate whether the connection failure is due to local network restrictions.

For mobile devices, DNS issues are often resolved by forgetting and reconnecting to the WiFi network. Go to WiFi settings, select the network, tap “Forget,” then reconnect by entering the password again. This forces the device to re-perform DNS lookups for all services.

Step four: Check for network switching during pairing

One of the most common reasons for WalletConnect timeouts occurs when the mobile device switches networks during the pairing process. If you began the pairing process on WiFi but your phone’s cellular carrier momentarily switched you to LTE, or if you switched from one WiFi network to another, the relay connection drops.

To prevent this, ensure that both devices remain on stable networks during the entire pairing sequence. Disable cellular data on your mobile phone (if connected via WiFi) to prevent automatic fallback. On some devices, there is a toggle in quick settings to “turn off mobile data” or “WiFi only mode.” Additionally, move closer to your WiFi router to ensure signal strength remains high throughout the pairing.

If pairing consistently fails at the same point in the sequence (for example, always after 10–15 seconds), network switching or signal loss is likely the culprit. Try pairing again, but this time monitor your mobile phone’s WiFi connection indicator in the status bar throughout the entire process. If the signal icon flickers or the connection appears unstable, move to a better location or restart the WiFi connection on your mobile device.

Step five: Clear cache and reset WalletConnect sessions

Browser extensions and mobile apps store WalletConnect session information locally. If a previous session ended abnormally or partially, the new pairing attempt may conflict with stale data. Clearing this cache often resolves timeout or “already paired” errors.

For Rabby Wallet in your browser: Open the extension, navigate to settings, and look for an option to clear cache, reset sessions, or clear WalletConnect data. Some versions display this in a “Developer” or “Advanced” section. If no such option is visible, try clearing your browser’s entire site data for the extension origin, though this is more extreme and may require you to re-import your wallet. Consult the official documentation accompanying your rabby wallet download for the specific steps applicable to your version.

For your mobile wallet app: Open the mobile wallet, navigate to settings, find “WalletConnect” or “Connected Apps,” and disconnect any existing Rabby Wallet sessions or legacy connections. Then force-stop the mobile app (go to phone settings, find the app in your installed applications list, and select “Force Stop”). Wait 10 seconds, then restart the app fresh before attempting to pair again.

This reset procedure clears conflicting session state that can cause the relay to reject a new pairing attempt or cause one device to think a connection is already active when the other believes it is not.

Step six: Test with an alternative relay or WalletConnect version

WalletConnect v2 is the current standard, but some older mobile wallets may still support v1. Similarly, WalletConnect operates multiple relay servers; if the primary relay is experiencing issues, switching to an alternative relay may succeed. Most users have no direct control over which relay is used, as it is determined by the version of WalletConnect embedded in each wallet. However, some advanced configurations allow specifying a custom relay URL.

If you are technically experienced, you can attempt to modify the WalletConnect relay configuration in your Rabby Wallet settings (if such an option is exposed). Otherwise, if connection failures persist despite following all previous steps, try switching to a different mobile wallet that you know uses the latest WalletConnect implementation. If MetaMask Mobile fails, try Trust Wallet; if imToken fails, try Bitget Wallet. This isolation test reveals whether the problem is specific to one mobile wallet’s WalletConnect implementation or whether it is a more general issue with your Rabby Wallet installation.

If a different mobile wallet connects successfully, the problem is with the original mobile wallet’s WalletConnect integration, not with Rabby Wallet. Uninstall and reinstall that mobile wallet, or contact its support. If all mobile wallets fail to connect to Rabby Wallet, the problem is more likely on the Rabby Wallet side or your network, and the next step should be a fresh installation.

Step seven: Reinstall Rabby Wallet as a last resort

If connection failures persist after all previous steps, a corrupted or conflicting Rabby Wallet installation may be the cause. Before reinstalling, export your wallet data. Rabby Wallet provides an export function in settings; use it to create a backup file containing your account information (note that private keys may or may not be included depending on your export settings, so verify before relying on this for recovery).

Remove the extension from your browser. In Chrome or Edge, right-click the extension icon and select “Remove from Chrome/Edge.” In Firefox, go to about:addons, find Rabby Wallet, and click “Remove.” Then, perform a rabby wallet download from the official source again, reinstall it as a fresh extension, and test WalletConnect pairing with a mobile wallet. Often this resolves subtle state corruption that survived cache clearing.

If a mobile wallet login still fails after reinstalling Rabby Wallet, move on to testing from a different computer or browser profile. Some system-level network filtering, proxy configuration, or browser extension conflict (particularly with other wallet extensions or security software) can interfere with WalletConnect even if both the Rabby and mobile wallet installations are clean.

Distinguishing between temporary and persistent failures

Not every connection timeout is permanent. WalletConnect’s relay infrastructure is distributed, but it can experience temporary overloads, especially during high-traffic periods (major market events, large migrations, or release days). If your connection fails, wait 5–10 minutes and try again. If it succeeds on the second attempt, the issue was likely transient relay congestion.

However, if failures are consistent, reproducible, and occur even hours later, the problem is not transient relay issues. At that point, systematic troubleshooting following the steps above is warranted. A pattern of failures only during specific hours may indicate geographic relay issues or your ISP’s traffic shaping during peak times; testing from a mobile hotspot (switching from your home WiFi to cellular data) can help identify such patterns.

Once you have successfully paired Rabby Wallet with a mobile wallet via WalletConnect, document the successful configuration (which mobile wallet app, which network conditions, which browser). If failures resume later, the problem may be an app update (either Rabby or the mobile wallet), a network change, or temporary relay issues. Rerun the diagnostics starting from the simplest step (update checks) rather than assuming the solution is more complex.