Docs
PricingDashboard

Network family

Solana errors

Solana endpoints speak standard Solana JSON-RPC over HTTPS POST. The gateway only forwards methods registered for the solana family. Path suffixes after the UUID are rejected; use the endpoint root.

-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: invalidMethod"
  }
}

Causes

  • Method not in the RpcNode Solana catalog (or typo in camelCase name).
  • Non-POST HTTP verb → method not allowed.
  • Websocket / subscription style usage against the HTTPS gateway.
  • Heavy getProgramAccounts / large range scans timing out upstream (-32002).

How to fix

  • Use methods from the Solana section in the docs sidebar.
  • POST JSON-RPC 2.0 to https://solana-{env}.{domain}/{uuid}.
  • Tighten filters and commitment levels; retry -32002 with backoff.
  • Remember full-node retention — very old slots may be unavailable.

Related