Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`header not found` error when starting ganache forking with infura RPC endpoint

See original GitHub issue

I’m not sure if this is specific to forking or infura, but periodically on v6.10.1 I receive the following error immediately on startup:

Ganache CLI v6.10.1 (ganache-core: 2.11.2)
Error: Returned error: header not found
    at Object.ErrorResponse (/home/mike/.nvm/versions/node/v12.18.3/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:39:2207407)
    at /home/mike/.nvm/versions/node/v12.18.3/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:39:2206279
    at /home/mike/.nvm/versions/node/v12.18.3/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:39:2193803
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Restarting will fix the issue fairly quickly. I’m wondering if this is related to #579 🤔 (doubt it though)

Your Environment

Version used: Ganache CLI v6.10.1 (ganache-core: 2.11.2)

Issue Analytics

State:
Created 3 years ago
Reactions:4
Comments:13 (6 by maintainers)

Top GitHub Comments

4reactions

rishanbcommented, Oct 6, 2020

Apologies for the delay, ran into some weirdness and wanted to collect it all rather than creating confusion.

I received the original error above (header not found) when trying to run ganache-cli while forking from Cloudflare: ganache-cli -f https://cloudflare-eth.com

Gave:

Ganache CLI v6.11.0 (ganache-core: 2.12.1)
Error: The fork provider errored when checking the nonce for account 0xcfd0f9c9dbb310707ab1ea60151e96b03daf1d32: Returned error: header not found
    at /usr/local/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:48:1994078
    at Object._fireError (/usr/local/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:4:75947)
    at s (/usr/local/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:4:119479)
    at n (/usr/local/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:48:2007203)
    at /usr/local/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:48:1993001
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  data: null
}

Retrying the same command provided the same error. I then uninstalled and reinstalled ganache-cli and got the same error with a different account address at the top.

If I leave out the “-f …” part I get the callback error which made me aware that I need to revert my node version. I’m currently in the process of figuring out nvm and will report back if this error persists from node 12.

3reactions

seesemichaeljcommented, Oct 31, 2020

@dexcell That’s correct! At the current time, you can use your free sandbox to fork with archival data. Check out our docs to see how to make a sandbox