NotArb - Solana Arbitrage Bot
  • Getting Started
    • Welcome
    • Changelog
    • The Basics
  • Setup
    • Start Here!
    • Prerequisites
      • Recommended Apps
      • RPC Providers
      • Linux Machines
    • Logging in Using SSH
    • Securing Your Machine
      • User Management
      • SSH Key-Based Authentication
      • Setting up UFW
      • Setting up fail2ban
      • Securing Wallet Private Key
    • Setting up for FTP
    • Initial Setup of NotArb
    • Using Screens
    • Making a Solana Wallet
  • Configurations
    • Using Nano
    • Config Basics
    • bot-config.toml
      • General Bot Settings
      • WSOL Unwrapper
      • JITO Strategy Settings
      • Spam Strategy Settings
      • Token Lists Settings
      • Swap Settings
    • jupiter-config.toml
      • Manager Settings
      • Env Settings
      • Mint Filters
    • Shell Scripts
      • run-bot.sh
      • run-jupiter.sh
      • run-screens.sh
  • Usage
    • Strategies
      • Jito Strategy
      • Spam Strategy
    • Updating
  • EXPERIMENTAL FEATURES
    • Overview & Caution
    • New Setup Configurations
  • New Mint Configurations
  • Default Strategy Fields
  • Jito Example
  • Spam Example
  • Extra Features
  • Support
    • FAQ
    • Common Issues
    • Troubleshooting
    • NotArb Docs Tracker
    • Contact
Powered by GitBook
On this page
  • NotArb Common Issues
  • "Rate limit exceeded. Limit: 5 per second for txn requests"
  • "bundle contains an expired blockhash"
  • Jupiter Common Issues
  • Not Able to Find Your Issue?
  1. Support

Common Issues

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

PreviousFAQNextTroubleshooting

Last updated 5 months ago

NotArb Common Issues

Under Construction

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

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

Either your have:

  • Multiple instances of the bot running on your machine

  • Multiple same zones configured

  • gRPC and http enabled in the same zone

  • 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"

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

UNKNOWN RESPONSE: 400

bundle contains an expired blockhash

~sendJitoDynamicTransaction () 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}

Your RPC provider is lagging.

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 .

🏗️
🏗️
https://tokyo.mainnet.block-engine.jito.wtf/
NotArb Discord