Recommended private RPC

[felipe1]

Do you guys recommend any private RPC to use? I’ve been receiving an error (Internal JSON-RPC error) no matter what public RPC I use ( https://mainnet.infura.io/v3/${infuraToken} , https://eth-mainnet.g.alchemy.com/v2/${infuraToken} and https://rpc.ankr.com/eth)

[w3abot]

Hi Felipe,

Thanks for reaching out! It sounds like you are having trouble with private RPC endpoints causing an Internal JSON-RPC error. Let’s address your concern:

SDK Details:

• SDK: Web3Auth Plug n Play

RPC Endpoints Tried:

• Infura: https://mainnet.infura.io/v3/${infuraToken}
• Alchemy: https://eth-mainnet.g.alchemy.com/v2/${infuraToken}
• Ankr: https://rpc.ankr.com/eth

Issue:

• Internal JSON-RPC error

A few quick recommendations:

1. Check your infuraToken and ensure it is correctly set. A common cause for JSON-RPC errors is an invalid or expired Infura token.

2. Ensure Your RPC Providers Are Correct: Verify that your projects with Infura, Alchemy, and Ankr have the necessary permissions and do not exceed the rate limits. Sometimes, free plans may get throttled or temporarily blocked, leading to errors.

3. Alternative Providers: If you are open to trying other private RPC providers, here are a few recommended services with strong reputations:

   • QuickNode: Known for high performance and reliability.
   • Moralis: Offers easy integration with various decentralized protocols.
   • Pocket Network: Decentralized infrastructure and redundant network.

4. Debugging: Please share:

   • A snippet of your Web3Auth initialization and login process.
   • Any relevant browser console screenshots showcasing the error.

This additional information will help us narrow down the issue and provide a more accurate solution.

This response was generated by the Web3Auth Bot, and a member of our Web3Auth team will also review this and provide further assistance.

Thanks!

[Ayush]

Hey @felipe1 do you get the error when you are using the private RPC as well? What action do you perform, when you get the Internal JSON-RPC error? It can happen for various reasons.

[felipe1]

I get the error on all the RPCs mentioned. Sometimes it works, sometimes it doesn’t. I’m just trying to call the estimateGas function.

I’ve mentioned it here as well:

Error: insufficient funds for gas * price + value

I’m using JWT login with OpenLogin. Also, is there a way to fallback the RPC with Web3Auth?

estimateGas error

Thanks for the explanation. To your points: I do have sufficient ETH balance Everything works when I call the contract methods on Etherscan. The problem is that when using our app, without specifying the gas fees, I get an error saying I don’t have enough ETH for the gas. And when I try to call the estimateGas function, I get the Internal JSON-RPC error. But sometimes it does work (mainly on Arbitrum). So I don’t think there’s an issue with the contract/ABI, otherwise it would never work. T…

[Ayush]

Hey @felipe1 can you please join our community call tomorrow, we’ll go through the code, and debug it.

Office Hours Link: Web3Auth

[felipe1]

Will join it. Thanks

[Ayush]

Hey @felipe1 did you have update after we debugged in Office hours?

[felipe1]

Hi @Ayush . We made a fix in the code according to the validation we are doing in the smartcontract, and it seems to be working fine so far. We’ll continue watching it. Thank you so much for your help!