Skip to main content
Version: 1.14.0

Troubleshooting

Connection​

No RPC configured​

Error: No RPC configured for chain ethereum-testnet-sepolia

Add an RPC endpoint:

Bash
.env
RPC_SEPOLIA=https://ethereum-sepolia-rpc.publicnode.com

RPC timeout​

Error: Request timeout after 30000ms
Error: connect ECONNREFUSED

Causes: RPC endpoint down, rate-limited, or network connectivity issue.

Solutions:

  1. Use a different RPC provider
  2. Test RPC connectivity:
    Bash
    curl -X POST https://your-rpc.com \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Transaction not found​

Error: Transaction not found

Causes: Wrong transaction hash, transaction on different network, or RPC using pruned node.

Solutions:

  1. Verify transaction hash on block explorer
  2. Ensure RPC is configured for source chain:
    Bash
    ccip-cli show 0x... --rpc https://source-chain-rpc.com
  3. Use archive node for old transactions

Chain not found​

error[CHAIN_NOT_FOUND]: Chain not found: 12922642891491394802

Cause: the chain id or selector is not in the bundled selector table. Typical for a local devnet, or for a network added to the chain-selectors registry after your CLI release.

Solutions:

  1. Update the CLI, if the chain is a public network
  2. Add the chain yourself:
    Bash
    ccip-cli show 0x... --chain-selectors 2337=12922642891491394802 --rpc http://localhost:8545 --no-api
  3. If the RPC is a fork served under a different chain id (Tenderly Virtual Environment, anvil --fork --chain-id), name the forked chain instead, so the fork keeps its selector. Otherwise the RPC is skipped, and the error's help: line names its chain id and the value to pass:
    Bash
    ccip-cli show 0x... --chain-selectors 735711155111=ethereum-testnet-sepolia --rpc $FORK_RPC --no-api

See Local Devnets and Forks.

Wallet​

Wallet not configured​

Error: Wallet required for this command

Commands send and manual-exec require a wallet.

Bash
.env
USER_KEY=0xYourPrivateKeyHere

Insufficient funds​

Error: insufficient funds for gas * price + value

Your wallet needs:

  • Gas for source transaction
  • CCIP fee (check with --only-get-fee)
  • Token amounts (if transferring)

Use --fee-token LINK to pay fees in LINK instead of native token.

Ledger connection failed​

Error: Cannot open device

Solutions:

  1. Unlock Ledger and open correct app (Ethereum for EVM)
  2. Enable blind signing in Ledger app settings
  3. On Linux, add udev rules:
    Bash
    sudo curl -o /etc/udev/rules.d/20-hw1.rules \
      https://raw.githubusercontent.com/LedgerHQ/udev-rules/master/20-hw1.rules
    sudo udevadm control --reload-rules

Message Tracking​

Message not found​

Error: No CCIP request found in transaction

Causes: Transaction is not a CCIP send, transaction pending, or wrong chain RPC.

Solutions:

  1. Verify transaction emitted CCIPSendRequested event on block explorer
  2. Wait for transaction confirmation
  3. Provide source chain RPC:
    Bash
    ccip-cli show 0x... --rpc https://source-chain-rpc.com

Commit not found​

Message not yet committed to destination chain.

Solutions:

  1. Wait for commit (timing varies by lane)
  2. Use --wait flag:
    Bash
    ccip-cli show 0x... --wait
  3. Verify destination RPC is configured:
    Bash
    ccip-cli show 0x... \
      --rpc https://source-chain-rpc.com \
      --rpc https://dest-chain-rpc.com

Execution​

Out of gas​

State: FAILURE
Return Data: 0x (empty or gas-related)

Receiver contract exceeded gas limit.

Use manual-exec with higher gas:

Bash
ccip-cli manual-exec 0x... --gas-limit 500000 --wallet ledger

Or auto-estimate:

Bash
ccip-cli manual-exec 0x... --estimate-gas-limit 20 --wallet ledger

Receiver reverted​

State: FAILURE
Return Data: 0x08c379a0...

Decode the error:

Bash
ccip-cli parse 0x08c379a0...

Fix the issue in receiver contract or adjust parameters.

Message stuck as UNTOUCHED​

Causes:

  • DON hasn't executed yet
  • Earlier message from same sender failed (ordering)
  • Rate limiter exhausted

Solutions:

  1. Wait for execution
  2. Check for ordering issues — execute each failed message individually in order:
    Bash
    ccip-cli manual-exec 0xFirstFailedTx... --wallet ledger
    ccip-cli manual-exec 0xSecondFailedTx... --wallet ledger
  3. Check rate limiter:
    Bash
    ccip-cli get-supported-tokens -n source -a router -t token

Already executed​

Error: Message already executed

Check status:

Bash
ccip-cli show 0x...

If state is SUCCESS, no action needed.

Chain-Specific​

Gas price too low​

Error: replacement transaction underpriced

Wait for pending transaction to confirm.

Nonce too low​

Error: nonce too low

Wait for pending transactions to confirm.

Tokens​

Token not supported​

Error: UnsupportedToken

Check supported tokens:

Bash
ccip-cli get-supported-tokens -n source -a router

Rate limiter depleted​

Transfer stuck or rejected due to rate limit.

Check rate limiter status:

Bash
ccip-cli get-supported-tokens -n source -a router -t token

Wait for bucket refill or reduce transfer amount.

Token approval failed​

Error: ERC20: insufficient allowance

The CLI handles approvals automatically. If approval fails:

  1. Approve manually on block explorer
  2. Use --approve-max:
    Bash
    ccip-cli send ... --approve-max

Output​

JSON parse error​

Piping --format json to jq fails due to mixed output.

Redirect stderr:

Bash
ccip-cli show 0x... --format json 2>/dev/null | jq '.'

If parsing succeeds but a chainSelector, amount, or fee looks wrong, see Reading JSON Output.

Interactive features not working​

Non-TTY environment (scripts, CI).

Use non-interactive options:

Bash
ccip-cli show 0x... --log-index 0
ccip-cli show 0x... --format json

Getting Help​

Enable verbose logging:

Bash
ccip-cli show 0x... --verbose

Check command help:

Bash
ccip-cli <command> --help

Report issues: github.com/smartcontractkit/ccip-tools-ts/issues