Common Issues

Browse through this section to see if your issue has been addressed.

NotArb Common Issues

🏗️ Under Construction

"Rate limit exceeded. Limit: 5 per second for txn requests"

Description

You keep getting the messages of being rate limited even though your settings are configured to only send 5 requests.

UNKNOWN RESPONSE: 429

Rate limit exceeded. Limit: 5 per second for txn requests

Cause

Either your have:

• Multiple instances of the bot running on your machine

• Multiple same zones configured

• gRPC and http enabled in the same zone

Solution

• Confirm you are not running more than one instance of the bot by executing:

  ps aux | grep java

• Verify in your configuration settings that you don't have duplicate zones for your Jito settings

"bundle contains an expired blockhash"

Description

No transactions are happening and you receive the following debug messages in your NotArb screen:

UNKNOWN RESPONSE: 400

bundle contains an expired blockhash

Example

~sendJitoDynamicTransaction (https://tokyo.mainnet.block-engine.jito.wtf/) queueMs=7396, sendMs=181, bundleId=null -> UNKNOWN RESPONSE: 400 - {"jsonrpc":"2.0","error":{"code":-32602,"message":"bundle contains an expired blockhash","data":null},"id":104656154383352}

Cause

Your RPC provider is lagging.

Solution

First check your RPC provider's announcement pages to see if there are any updates or issues with their services. If there are no announcements, speak with your provider about the issues you're having.

Jupiter Common Issues

🏗️ Under Construction

Not Able to Find Your Issue?

Please reach out to the Support chat on the NotArb Discord.