Binance testnet rpc proxy partial outage

[Droppix]

Describe the bug

1/ When we call the ModalCtrl.open() function (from the 2nd time, but sometimes randomly), we have an error which is displayed "Failed preloading" (see screenshot)

Any idea?

2/ We would like to hide "w3m-modal-backcard + w3m-toolbar", would it be possible to have an option?
By playing with the style + timer, it's works, but we have a "flicking"

SDK Version

• Version [2.0.0 RC3]

Desktop (please complete the following information):

• OS: [Mac OS]
• Browser [Chrome]

**Environment

• Vue + Nuxt 2

Thanks

[xzilja]

If you open network tab, can you pinpoint which requests are failing during preload please. Also you can try await web3modal.open() (there is no ModalCtrl in rc3, so I assume that was a typo?)

Currently no plans to removing header section, but we will be re-reviewing that soon once we release stable version and start on customisation tasks.

[Droppix]

Strange...
1/ Package.json
"@web3modal/core": "^2.0.0-rc.3",
"@web3modal/ethereum": "^2.0.0-rc.3",
"@web3modal/ui": "^2.0.0-rc.3",

import { ClientCtrl, ConfigCtrl, ModalCtrl, OptionsCtrl } from '@web3modal/core'
import { WalletConnectConnector } from '@wagmi/core/connectors/walletConnect'
import { EthereumClient, modalConnectors, walletConnectProvider } from '@web3modal/ethereum'

2/ the node_modules directory has been destroyed

3/ npm i @wagmi/core@latest @web3modal/core@latest @web3modal/ethereum@latest @web3modal/ui@latest

Did I forget something?

[xzilja]

You should no longer be using controller pattern, all methods are now accessible on instance of web3modal. Nor using core package.

You are probably coming from an older version vanilla js, so want to start using new and simpler html package i.e. https://docs.walletconnect.com/2.0/web3modal/html-js/installation

[Droppix]

Ok, but would this explain the POST errors below? (this has been happening frequently for some time)

`
geturl.js?21de:48 POST https://rpc.walletconnect.com/v1/?chainId=eip155:97&projectId=962def0af1c680c26d6e0f8d4a24bd87 503 (Service Temporarily Unavailable)

geturl.js?21de:48 POST https://rpc.walletconnect.com/v1/?chainId=eip155:97&projectId=962def0af1c680c26d6e0f8d4a24bd87 503 (Service Temporarily Unavailable)
eval @ geturl.js?21de:48

geturl.js?21de:48 POST https://rpc.walletconnect.com/v1/?chainId=eip155:97&projectId=962def0af1c680c26d6e0f8d4a24bd87 503 (Service Temporarily Unavailable)

geturl.js?21de:48 POST https://rpc.walletconnect.com/v1/?chainId=eip155:97&projectId=962def0af1c680c26d6e0f8d4a24bd87 503 (Service Temporarily Unavailable)

[xzilja]

Just checked with bsc testnet, everything seems to be fine with rpc.
Are you by any chance using some sort of proxy / vpn / located in country that might be blocking this request?

For latter, we are working on exposing non .com endpoints to unlock our api's in countries that might be blocking them atm. You will be able to configure these i.e. .org domains for example. Associated issue #829

You can also remove wallet connect rpc in favour of using something else that works while we are working on above.

[Droppix]

No VPN, no proxy, we are in France, and we have no problems with the network... We see this error from time to time, but without really understanding...

I also tried with curl ( https://rpc.walletconnect.com/v1/?chainId=eip155:97&projectId=962def0af1c680c26d6e0f8d4a24bd87 ), same error ....

And there without touching the code, it works again!

[xzilja]

I will forward this to our infra team so they can check the logs / see what could be wrong 👍

[Droppix]

Thanks

[Droppix]

FYI: 503 Service Temporarily Unavailable (NGINX)
same with curl -X POST

[thisisandreww]

FYI: 503 Service Temporarily Unavailable (NGINX) same with curl -X POST

I am receiving this issue from time to time as well when connecting to bsc test net. It seems to occur intermittently when i'm trying to get the wallet balance.

[arein]

Hi. We strongly believe that this is not us but our BSC testnet RPC provider.
WalletConnect/blockchain-api#90 such that we can provide it and give you an according error message for when this happens in the future.

You are also welcome to add a BSC testnet provider you deem stable here: https://github.com/WalletConnect/rpc-proxy

Closing ticket. Please track the linked ticket and communicate there for more comments.

[Droppix]

@arein
It's still very strange, you must admit that it's your NGINX daemon that answers 503 and it's not us?

[arein]

We don't use nginx at WalletConnect so you're just getting the 503 from our RPC provider as described above
(we act as a proxy)

[Droppix]

sorry;) I didn't read your previous answer correctly "but our BSC testnet RPC provider."