-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallet Connect connection did not reply, I am not sure what network requirements are required #156
Comments
WalletConnect does not offer services in the following regions: Cuba, North Korea, Syria, Iran, Luhansk Oblast (Ukraine), Donetsk Oblast (Ukraine), and Crimea (Ukraine). However, this does not guarantee that the service will function seamlessly elsewhere. If your ISP blocks connections to the WalletConnect Relay, using a VPN might not resolve the issue. I can personally confirm that WalletConnect operates without any problems in Japan. There is one thing you could try though. In the |
This method has solved my problem, I really appreciate it. Thank you, thank you. |
Hi, I think we meet the same issue, if Chinese users have to use vpn, how to resolve this problem, now our app for Chinese users can not popup the transaction in metamask |
You can use However, this is only on the app side. Wallets need to do the same. I don't know if MetaMask uses Possibly related issue: #165 |
I conducted another test today, and when I connected to the Japanese network_ Client What are the network requirements for Connect (connectOptions) as it has not been successfully connected and has not timed out?

The text was updated successfully, but these errors were encountered: