bug: Attempt to connect to relay via transportOpen has stalled. Retryin

[meetkosiso]

Is there an existing issue for this?

• I have searched the existing issues

Package Version

2.0.0

Current Behavior

After upgrading to wallet connect v2, our website shows Attempt to connect to relay via transportOpen has stalled. Retryin each time the website is loaded and wallet is connected, however,

this was not the case with wallet connect v1

Expected Behavior

I expect this error not to be shown on the console when the website is loaded or when a wallet is connected.

Steps To Reproduce

1. Upgrade to wallet connect v2
2. Try to load the website or connect your wallet after loading the website
3. Go to the developer console of your browser.

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)

No response

Anything else?

No response

[ignaciosantise]

hey @meetkosiso 👋 this error usually happens when a a VPN/ISP block .com urls, and our default relay url is wss://relay.walletconnect.com

• Are you using a VPN? If so, can you try disabling it?
• Do you know if your ISP is blocking .com domains?

Once #384 is merged:

• the connection should automatically attempt to fall back to using wss://relay.walletconnect.org
• you will be able to manually specify a relayUrl to override default behaviour

[yumingvvv]

An error still occurs when the vpn is disabled

[ck256-2000]

started getting this issue on local host/hardhat instance. Scaffold ETH 2 framework