Errors from POKTscan

The Pocket Portal is a tool run by the Pocket Foundation that allows applications to create accounts and get access relays on the Pocket Network. The Portal has an error API that can help node runner identify potential errors with their nodes. To see what errors the Portal might have in regards to your node, go to POKTscan, search for your node, and click eye on the right hand side to see your full node details. Scroll down to a section called "Errors" to see any errors from the Portal API.

NOTE: Many errors can be ignored as they have nothing to do with the performance of your node.

Error FAQ

Do I need to worry if there are errors with my node?

It depend on the error. Search for the error below to identify if it should be ignored or has relevance to your node.

Does the Chain Check or Sync Check only happen when a node is in a session, or does the gateway ping all validators all the time?

Currently they run only when sessions are active; every 5 minutes. In the future they will run continuously and separately from the sessions.

What is the difference between Chain Check and Sync Check?

  • Sync check makes sure that the node is within a certain allowance of the oracles we check. For fast chains like Harmony, the allowance is longer than slower chains like Ethereum.

  • Chain check ensures that the nodes are serving the correct chain ID. It is an edge case, but it is possible to get a session full of nodes serving the wrong chain but agreeing on blockheight, and therefore passing the sync check.

Relevant Errors

timeout of 4000ms exceeded

Importance: TAKE ACTION


  • Apps are sending larger requests than what your node is setup for. Not serving these requests can mean less rewards.

Possible Next Steps:

Increase your RPC timout variable in config.json with the following steps:

  1. Shut down Node Pilot (or just that Pocket node)

  2. Edit ~/.node-pilot/config/nodes/[NODE-ID]/root/config/config.json

    • (for non Node Pilot users, inside your node's folder: /root/config/config.json)

  3. Change "rpc_timeout": from 3000 to 15000

  4. Save changes

  5. Start Node Pilot (or start that Pocket node)

Server Timeout Handling Request



  • Your pocket node timed out

  • Your data node timed out

  • There was a blip in the internet service between the API and your pocket node

  • The pocket node was under stress due to block/session rollover and was unable to handle the RPC

Possible Next Steps:

  • Give your node more hardware resources so it can handle more stress.

  • Change node location or service provider if the interent is unreliable.

OUT OF SYNC: current block height on chain 0021: 13646961 altruist block height: 13646961 nodes height: 13641317 sync allowance: 3



  • Your data node is more than the allowance out of sync.

Possible Next Steps:

Check that chain node's current block height against the block height of a trusted explorer. If you node is at the current block height, it may have gotten behind temporarily. If it is behind, then try any of the following.

  • Restart that chain node

  • Give your node more hardware resources in-case the node is too stressed.

  • Delete the chain data and resync.

502 Bad Gateway

The load balancer in front of your node is unable to talk to the Pocket node due to the Pocket node timing out.

Same as Server Timeout Handling Request

certificate has expired

Importance: TAKE ACTION


  • Node runner has an expired TLS cert.

Possible Next Steps:

  • Renew TLS cert.

the blockchain in the relay request is not supported on this node

Importance: TAKE ACTION


  • It means that your POKT node is staked for a chain node but isn't able to connect with it.

Possible Next Steps:

  • Restart your node

    • If you have added or removed any connected chains, you need to restart your POKT node so the node accepts the changes.

Irrelevant Errors

Provided Node is not part of the current session for this application, check your PocketAAT

Importance: IGNORE


Due to differing blockheight between dispatch and your pocket nodes. It isn't something you can correct (other than making sure your pocket node is in sync) and this error isn't counted against your node. It is something the core team hopes to eliminate in the next major version release.

missing trie node

Importance: IGNORE


  • The app is querying your node for data that has been pruned

  • Likely to be an app error where the app should be using an archival endpoint and not a standard mainnet endpoint

Client network socket disconnected before secure TLS connection was established

Importance: UNKNOWN


the evidence is sealed, either max relays reached or claim already submitted

Importance: IGNORE


  • This is the result of an app using more relays that what is staked for them. This relates to app, not nodes.

execution reverted

Importance: IGNORE


  • An app error they receive when submitting incorrect transactions, failing gas wars, etc.

the blockchain in the relay request is not supported for this app

Same as execution reverted

Last updated