Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'No Response error' from web3_request_manager.js #7049

Open
dhayaprabhu opened this issue May 20, 2024 · 3 comments
Open

'No Response error' from web3_request_manager.js #7049

dhayaprabhu opened this issue May 20, 2024 · 3 comments
Labels
4.x 4.0 related

Comments

@dhayaprabhu
Copy link

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
Copy link

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

@mconnelly8 mconnelly8 added the 4.x 4.0 related label May 24, 2024
@luu-alex
Copy link
Contributor

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

@mconnelly8
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x 4.0 related
Projects
None yet
Development

No branches or pull requests

3 participants