This page describes some common Blockchain Node Engine errors and how to fix them.
Could not resolve host
The following error occurs when you try and use the blockchain node while it is still being created:
Could not resolve host: json-rpc.abc1234.blockchainnodeengine.com
To resolve this issue, wait for the node to reach a RUNNING state. You can see the status as described in List blockchain nodes.
400 error: Method doesn't allow unregistered callers
The following error occurs when you try and use the blockchain node without an API key:
400 error: Method doesn't allow unregistered callers (callers without
established identity). Please use API Key or other form of API consumer
identity to call this API.
To resolve this issue, see: Create an API key
I don't know if my node has finished syncing
To resolve this issue, do one of the following:
Full nodes: Make a call to
eth_syncing
and if you get afalse
response, then it is done.curl -H POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":2586,"method":"eth_syncing","params":[]}]}' https://<executionClientJsonRpcEndpoint>?key=<API_KEY>
{"jsonrpc":"2.0","id":2586,"result":false}
Archive nodes: Query the metrics endpoint
executionClientPrometheusMetricsApiEndpoint
:curl -H "Content-Type: application/json" 'http://<executionClientPrometheusMetricsApiEndpoint>/debug/metrics/prometheus?key=<API_KEY>'
Look for the
block_hashes
value in the response.