> For the complete documentation index, see [llms.txt](https://docs.getblock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getblock.io/getting-started/testing-rpc-connection/errors-and-troubleshooting.md).

# Errors and troubleshooting

This page provides a guide to common JSON-RPC and HTTP errors when testing your connection with GetBlock's API.

### Connection issues

| Code                 | Error Message                               | Solution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| -------------------- | ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 401                  | Missing token-id                            | The token segment of the URL is empty, malformed, or has stray characters (including a trailing space, or a missing token entirely). Copy the endpoint URL from your GetBlock Dashboard exactly as issued.                                                                                                                                                                                                                                                                                                                       |
| 401                  | Unknown token                               | The token isn't recognized on this host. This covers several causes: the token is simply wrong (typo), it was rolled or deleted, it was never issued, or — since access tokens are region-bound — it's a completely valid token, just issued for a different region than the host you're calling (`eu-central-1`, `us-east-1`, or `ap-southeast-1`). If you're sure the token is current and correct, check it matches the region shown for that endpoint in your Dashboard; if it might have been rolled, generate a fresh one. |
| — (no HTTP response) | Could not resolve host / DNS lookup failure | Your request never reached GetBlock. Check the host segment of the URL is spelled correctly, e.g. `<service>.<region>.getblock.io`, and matches one of the regions shown in your Dashboard.                                                                                                                                                                                                                                                                                                                                      |
| 429                  | Too many requests                           | Check your GetBlock account for usage limits. Upgrade your plan if necessary                                                                                                                                                                                                                                                                                                                                                                                                                                                     |

### JSON-RPC errors

<table><thead><tr><th width="205">Code</th><th width="158">Error message</th><th>Solution</th></tr></thead><tbody><tr><td>-32600</td><td>Invalid Request ("method must be POST")</td><td>JSON-RPC requests must be sent as <code>POST</code> with a JSON body. This is what you'll see if you open the endpoint URL directly in a browser or send a <code>GET</code> request.</td></tr><tr><td>-32601</td><td>The method does not exist/is not available</td><td>Verify the method name (<code>eth_blockNumber</code>, <code>eth_getBalance</code>, etc.) against the blockchain's JSON-RPC <a href="/api-reference/overview.md">specifications</a>.</td></tr><tr><td>-32602</td><td>Invalid argument</td><td>Ensure the parameters in the <code>params</code> array match the expected format for the method.</td></tr><tr><td>-32700</td><td>Parse error (invalid JSON format)</td><td>Double-check your JSON syntax. Ensure your request is properly formatted.</td></tr></tbody></table>