Searchable fixes for technical failures.
Paste an error and jump to the closest safe fix, or browse curated troubleshooting pages. Raw URLs, payloads, tokens, secrets and PII are not published.
API connection failed
The endpoint could not be reached before an HTTP response was received.
APIAPI request timed out
The endpoint did not complete the bounded health request within the diagnostic timeout.
APIAPI returns HTTP 500
The endpoint is reachable, but the application reports an internal server error.
APIAPI returns HTTP 502 Bad Gateway
A proxy or gateway reached the request path but could not obtain a valid upstream response.
APIAPI returns HTTP 503 Service Unavailable
The service path is reachable but currently unavailable to serve the request.
APIAPI returns HTTP 401
The endpoint is reachable but requires authentication that the health request did not provide.
APIAPI returns HTTP 403
The server understood the request but refused access.
APIAPI returns HTTP 404
The host is reachable but the requested route was not found.
APIAPI returns an unexpected redirect
The endpoint redirects instead of returning the expected API response.
APIAPI is reachable but slow
The endpoint responds successfully, but response latency is high enough to affect clients or chained workflows.
RPCEVM RPC request timed out
The JSON-RPC endpoint did not complete the bounded chainId/blockNumber diagnostic in time.
RPCEVM RPC request failed
The RPC request failed before a usable JSON-RPC result was obtained.
RPCRPC returned an invalid or restricted response
The endpoint responded, but the expected chainId and blockNumber results were not both available.
RPCEVM RPC is responding slowly
The node answers basic chain queries but with high latency that may degrade wallets, bots or backend flows.
RPCRPC response is missing eth_chainId
The endpoint does not return the expected chain identifier in the diagnostic response.
RPCRPC response is missing eth_blockNumber
The endpoint cannot provide the current block height in the expected JSON-RPC result.
WEBHOOKWebhook payload is not valid JSON
The payload cannot be parsed as JSON, so downstream webhook processing is likely to fail before business logic runs.
WEBHOOKWebhook JSON has no top-level fields
The body is valid JSON but does not expose top-level fields useful for routing or event identification.
WEBHOOKWebhook payload has no obvious event field
The payload parses correctly but lacks a common event discriminator such as type or event.
WEBHOOKWebhook sample has no obvious signature field
The JSON sample does not include a top-level signature field; verification may instead rely on headers or a provider-specific scheme.