JsonRpcProvider failed to detect network and cannot start up

[mikenevermindng]

Ethers Version

6.7.1

Search Terms

react native, ethers

Describe the Problem

I encountered the error 'JsonRpcProvider failed to detect the network and cannot start up; retry in 1s.' This may be due to an incorrect URL or the Ethereum node not being started when using JsonRpcProvider in my React Native app with version 0.71.5.

Code Snippet

getProvider(): ethers.JsonRpcProvider {
    if (this.#provider) {
      return this.#provider;
    }
    const config = ETH_NETWORK_CONFIG[this.#currentNetwork];
      if (!config) {
          return null;
      }
    this.#provider = new ethers.JsonRpcProvider(config.rpc);
      this.#provider.send("eth_chainId", []).then(number => {
          console.log(number)
      })
    return this.#provider;
  }

Contract ABI

No response

Errors

LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)
 LOG  JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)

Environment

No response

Environment (Other)

No response

[dev-svikrant406]

@mikenevermindng I am also facing the same issue from long time, interestingly some time its working fine, but after sometime getting the same error with ethers v6 in my React Native app with version 0.71.3.

I also downgraded to ethers version 5.7.2 but still same issue on ethers v5 as well.

Error: could not detect network (event="noNetwork", code=NETWORK_ERROR, version=providers/5.7.2)

[rahmaniali-ir]

Any update on this?
I'm getting the same error with this:

const provider = new ethers.BrowserProvider(
   ethereum,
   chainId
);

const contract = new ethers.Contract(address, abi, provider);

Error:

JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)

[formysister]

@mikenevermindng
maybe you should try with the other RPC urls when initialize provider.

you can get the RPC url of network you want here: https://chainlist.org

hope this can be help for you.

[josechifflet]

Same issue here.

[gkirat]

I was having the same issue , i was making voting Dapp , I made frontend and when it was ready I made a copy of the frontend and saved it. Now I edited and installed and uninstalled to many packages in my full stack project but so at the end , I deleted all the packages except ether.js package , even if i tried to make a simple "Connect Wallet" button using ether.js it was not working it was giving me this error in the console" JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)" ,
Now my copy was untouched that i made of frontend , there i only installed ether.js using "npm i --save -ethers" in my client folder and when I made "Connect wallet" button using ether.js it was working , in short i think that some of the packages before were clashing or maybe there is something in cache in the folder which was giving an error but when i started clean only installing the package i need it did work .

This was my connectWallet function that was called by button "Connect Wallet " in both the cases which was same for both the cases

 const connectWallet = async ()=>{
      if(typeof window != "undefined" && typeof window.ethereum != "undefined"){

        const provider =  new ethers.BrowserProvider(window.ethereum)
        await provider.send("eth_requestAccounts", []);
        const signer  =  await provider.getSigner()
        // const contract =  new ethers.Contract(contractAdd,Abi.abi,signer) 
        //Uncomment above if you are using contract or making a dapp
        console.log(signer.address)
        alert("Metamask connected");
        setWalletConnected(true)
      }
      else{
        console.log("Please install metamask")
      }

    
}

[gkirat]

I would suggest if you have copy of code than try in that , from the beginning , just install ethers by running command "npm i --save ethers", then make the code., the above code will work for both provider which is read only and for signers.

[AuroraLantean]

I have solved this with Ethers.js 6.8.0 and Infura:

network = "sepolia"
infuraApiKey = '1234...'
provider = new ethers.InfuraProvider(network, infuraApiKey); 
// InfuraProvider() does not behave the same way as JsonRpcProvider()
// JsonRpcProvider() is used for Ganache/Hardhat/Foundry

Not all Json RPC providers are created equally. Try to use different ways to make the new jsonPrcProvider:
https://docs.ethers.org/v6/api/providers/thirdparty/

An old example of using Infura with Ethers.js: https://community.infura.io/t/react-js-ethers-js-demo-of-using-the-infuraprovider-vs-the-metamask-wallet-web3provider/6108

This one is still actual! 🆙

[imaksp]

same issue with JsonRpcProvider with alchemy url,
@ricmoo is it necessary to use alchemy provider instead of JsonRpc with valid alchemy url like https://polygon-mumbai.g.alchemy.com/v2/{apiKey}

[imaksp]

Actually getting this error only with arb or arb sepolia network its not related to alchemy provider or json rpc provider usage.

[ricmoo]

It could be that your API key is out of capacity. Basically this happens when it queries for the network and some unrecoverable error occurs.

if you use the ApchemyProvider, it knows (based on the URL) which network to use and won’t query it, but even in that case, if the API key is empty, it just means the next thing will fail.

[imaksp]

It could be that your API key is out of capacity. Basically this happens when it queries for the network and some unrecoverable error occurs.

if you use the ApchemyProvider, it knows (based on the URL) which network to use and won’t query it, but even in that case, if the API key is empty, it just means the next thing will fail.

Not sure because we are on Alchemy paid plan & capacity is not an issue API key is only used on server, but it may be Alchemy issue as only Arb is having issue as of now, also ethers Alchemy provider doesn't support arb sepolia, so using json rpc url directly.