web3 / web3.js

Collection of comprehensive TypeScript libraries for Interaction with the Ethereum JSON RPC API and utility functions.
https://web3js.org/
Other
19.21k stars 4.92k forks source link

'No Response error' from web3_request_manager.js #7049

Closed dhayaprabhu closed 2 weeks ago

dhayaprabhu commented 4 months ago

InvalidResponseError: Returned error: no response at Web3RequestManager._processJsonRpcResponse (file:///../node_modules/web3-core/lib/esm/web3_request_manager.js:252:23) at Web3RequestManager. (file:///../node_modules/web3-core/lib/esm/web3_request_manager.js:150:29) at Generator.next () at fulfilled (file:///../node_modules/web3-core/lib/esm/web3_request_manager.js:20:58) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Emitted 'error' event on Client instance at: at emitUnhandledRejectionOrErr (node:events:401:10) at process.processTicksAndRejections (node:internal/process/task_queues:84:21) { innerError: { message: 'no response', code: -32603 }, code: 101, data: undefined, request: { jsonrpc: '2.0', id: '5cc619f1-6fcb-4380-8dc7-05181368fd4c', method: 'eth_call', params: [ { to: '0xXXXXXXXXXXXXXXXXXXXXXXXXXXXX', from: '0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', input: '0xXXXXXXX' }, 'latest' ] } } what could be the possible reason for the 'No Response' error ? Can anybody help?

mconnelly8 commented 4 months ago

Hey @dhayaprabhu, the team will review this soon and get back with you.

luu-alex commented 4 months ago

Hi there, what provider url were u using? this doesn't seem to be a web3.js issue but your providers

mconnelly8 commented 3 months ago

Hey @dhayaprabhu, what provider URL were you using? As Alex mentioned, this doesn't seem to be a web3.js issue, but we'd like to double check.

mconnelly8 commented 2 weeks ago

Hey @dhayaprabhu, since we didn't get a response, I'll be closing this issue. If you are still experiencing an issue, please open the issue and send over the provider URL you were using.