Common Relayer Errors

List of commonly seen errors with their explanation and tips on how to fix them.

Insufficient funds for gas

ERROR tesseract_messaging: Failed to submit transaction to Evm(42161): Middleware error: (code: -32000, message: insufficient funds for gas * price + value: address <your-relayer-address> have 0 want 323200000000000, data: None

This error means your relayer account balance on the destination chain is insufficient to submit a transaction

Debug trace frame not found!

ERROR tesseract_evm::provider: Debug trace frame not found!

This error signifies that the debug_TraceCall call for a message failed, this could be that the message execution failed or the rpc does not provide debug trace logs

Please ensure the contract and method you're calling exist

ERROR tesseract_messaging: Error while handling POLKADOT-3367 on Evm(8453): Invalid name: please ensure the contract and method you're calling exist! failed to decode empty bytes. if you're using jsonrpc this is likely due to jsonrpc returning `0x` in case contract or method don't exist

This error signifies misconfiured rpc endpoints or ismp_host addresses.

Error encountered while querying state_machine_update_time

ERROR tesseract: Messaging task Evm(56)->Polkadot(3367) encountered an error: StreamError("Error encountered while querying state_machine_update_time Middleware error: (code: -32000, message: header not found, data: None)")

This error means the rpc endpoint failed to return a valid response for a block header query

Failed to submit unsigned extrinsic

ERROR tesseract_messaging: Failed to submit transaction to Polkadot(3367): Failed to submit unsigned extrinsic

This error means the relayer is trying to submit a duplicate transaction to hyperbridge

The method debug_traceCall does not exist

ERROR tesseract_messaging: Error while handling POLKADOT-3367 on Evm(56): Middleware error: (code: -32601, message: The method debug_traceCall does not exist/is not available, data: None)

This error means your rpc endpoint does not provide the debug_traceCall method

Error waiting for challenge period

ERROR tesseract: Error waiting for challenge period in Evm(56) - Polkadot(3367) update stream

This is usually caused by a network issue or invalid response from the rpc node

Failed to submit transaction to Evm(10): Transaction reverted

ERROR tesseract_messaging: Failed to submit transaction to Evm(10): Transaction reverted

This error means the relayer is tried to submit a duplicate transaction

API key is not allowed to access method

ERROR tesseract_messaging: Error while handling POLKADOT-3367 on Evm(100): Middleware error: (code: -32053, message: API key is not allowed to access method, data: None)

This means the your rpc provider limits access to some endpoints

Error fetching latest block height

ERROR tesseract: Messaging task Evm(56)->Polkadot(3367) encountered an error: StreamError("Error fetching latest block height on Evm(56) JsonRpcClientError(MiddlewareError(Middleware((code: -32603, message: request failed or timed out, data: None))))")

This is usually caused by a network issue or invalid response from the rpc node

Request failed or timed out

ERROR tesseract_evm::provider: Error while querying events in range 43812202..43812204 from Evm(56): Middleware error: (code: -32603, message: request failed or timed out, data: None)

This is usually caused by a network issue or invalid response from the rpc node

Internal server error

ERROR tesseract_evm::provider: Error while querying events in range 43816145..43816147 from Evm(56): Middleware error: (code: -32603, message: internal server error, data: None)

This is usually caused by a network issue or invalid response from the rpc node

Error accummulating some fees

ERROR tesseract_messaging: Error accummulating some fees, receipts have been stored in the db, you can try again manually

This error means the relayer encountered some error while accumulating fees on hyperbridge

Missing trie node

ERROR tesseract_messaging: Error while handling EVM-56 on Polkadot(3367): Middleware error: (code: -32000, message: missing trie node baf71a6410ba54b32b02056415efe6b22060c20aff9c399d9b6308d0a88c3d09 (path ) state 0xbaf71a6410ba54b32b02056415efe6b22060c20aff9c399d9b6308d0a88c3d09 is not available, data: None)

This error signifies that your rpc node is not archive

Disconnected from telemetry

ERROR tesseract::cli: Disconnected from telemetry with: Text(

This error can be safely ignored as telemetry is not a critical function of the relayer