Error: Failed to make request with networkConnector: "undefined" at MiniRpcProvider.request

Moralis General
#1

Error: Failed to make “eth_getTransactionCount” request with networkConnector: “undefined” at MiniRpcProvider.request (node_modules/moralis/lib/node/Web3Connector/NetworkWeb3Connector.js:85:15)
throw new Error(`Failed to make “${method}” request with networkConnector: “${error.message}”`);

web3.js functions are not working using moralisSecret on serverside

const Moralis = require('moralis/node');
const web3 = require('web3');

await Moralis.start({
  moralisSecret: 'xxxxxx',
});

await Moralis.enableWeb3({
  chainId: '0x4'
});

const web3Provider = new web3(Moralis.provider);

const count = await web3Provider.eth.getTransactionCount('anyaddress');
console.log(count);

I am using “moralis”: “1.5.8”.
The above code with appropriate values was working fine before the recent "speedy node removal change". I am using free account. I just want to know is this process also deprecated or it is a bug generated form the recent update. If deprecated then what will be the alternative process for using web3.js with Moralis on server-side

#2

Looks like an issue due to speedy nodes retired.

1 Like
#3

Yes, speedy nodes are removed, but will this issue be fixed, can we be able to use Moralis with web3.js from serverside any longer or not?

#4

In such case, you can use a custom RPC url with an web3 provider. You can check here https://moralis.io/largenodes

1 Like
#5

Okay, thanks for chainstack alternative. But i just want to know, if this issue will be fixed or not, if it will not be fixed then i have to think about something else, or if it will be fixed then i will stick to moralis. I hope i will get an appropriate answer.

#6

Yes if you use an RPC URL from another provider then you will be able to keep using Moralis with web3.js (same with ethers.js).