Docs
PricingDashboard

Network family

TRON errors

TRON is special on RpcNode: you can call registered Full Node HTTP methods as path suffixes after the endpoint UUID (e.g. /{uuid}/wallet/getnowblock), and you can also POST eth_* JSON-RPC at the endpoint root. Unknown paths or eth methods return -32601.

-32601-32600-32002

← All errors

Example response

Example

HTTP/1.1 404 Not Found
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32601,
    "message": "method not found: wallet/unknown"
  }
}

Causes

  • Wrong Full Node path (typo or method not registered).
  • HTTP verb not allowed for that TRON method (some paths are GET, many are POST).
  • Sending JSON-RPC to a path suffix, or a TRON HTTP body to the root without eth_*.
  • Upstream Full Node errors proxied through, or -32002 on total failure.

How to fix

  • Copy the exact path and verb from the TRON method page in docs.
  • For eth_* compatibility methods, POST JSON-RPC to the endpoint root with no extra path.
  • Check Content-Type and body shape expected by the Full Node HTTP API.

URL patterns

JSON-RPC: POST https://tron-{env}.{domain}/{uuid} with eth_* methods.

Full Node HTTP: https://tron-{env}.{domain}/{uuid}/{wallet-or-walletshell-path} with the verb from the catalog.

Related