could not detect network

[ivands]

ethers.providers.getDefaultProvider('https://data-seed-prebsc-1-s1.binance.org:8545/')

For some reason, it's working when I'm testing this on my local machine.
But when I deploy to lambda it fails with the following error.

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

[alexnguyennz]

Am getting this error as well but with the main ethers.js - I'm trying to get ethers.js working with the Netlify Lambda plugin and Express.

Have tried all combinations of JsonRpcProvider, getDefaultProvider.

Everything works locally just fine but if I try to access the same route through Lambda, I get this error (along with WARNING: Missing strong random number source).

[ricmoo]

I’m not familiar with the lambda internals, but maybe it uses JavaScriptCore?

If so, you will need to shim in a secure random number generator, if you require a secure random source. If you are not creating new wallets though, you likely do not need to worry about this warning.

[alexnguyennz]

Hi there, yeah I'm just pulling read only data.

Interestingly this happens when I use RPC URLs in either getDefaultProvider or JsonRpcProvider:

E.g.

• https://rpc.ftm.tools/
• https://polygon-rpc.com/
• https://mainnet.infura.io/v3/
• https://eth.rpcgator.com/

These last two should be identical to getDefaultProvider() or getDefaultProvider('mainnet') ?

All of these give me "Error: could not detect network" in Lambda - but fine elsewhere.

But getDefaultProvider('mainnet' or 'ropsten') don't give me this error.

Think this is narrowed down a bit to the use of URLs. How do the hardcoded names like mainnet resolve?

[alexnguyennz]

Found a solution - eventually narrowed down the issue to an issue with fetch or lack of it with Lambda.

In infura-provider.js, after editing the host for "arbitrum-rinkeby" from "arbitrum-rinkeby.infura.io" to "rpc.ftm.tools", this got around the "could not detect network" error and eventually led to "fetch is not defined" (the first error message was just hiding the true error).

Installing node-fetch and putting

global.fetch = require('node-fetch').default;

in my functions/server.js (middleware) has "fixed" it.

So everything all working now.