Platform errors
Method not found / not supported
The gateway only accepts methods registered for the network family. Unregistered methods fail at parse time with JSON-RPC -32601 (method not found) and never hit upstream.
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: eth_subscribe"
}
}Causes
- Calling a method that RpcNode does not expose for this network (e.g. wallet admin RPCs, subscriptions over HTTP).
- Wrong network family (Bitcoin method on an EVM endpoint, or TRON path on a Solana endpoint).
- Typo in the method name or TRON HTTP path after the UUID.
How to fix
- Open the network page in docs and pick a listed method.
- Use the family troubleshooting pages for EVM, Solana, Bitcoin, and TRON quirks.
- RpcNode is a managed full node over HTTPS — WebSocket subscriptions are not available on the HTTP gateway.