Troubleshooting

Jupiter Connection Stuck

Problem: Bot hangs on "Connecting to Jupiter..."

Solution: Ensure port 18080 is free and the Jupiter binary has execute permissions:

chmod +x jupiter
lsof -i :18080  # Check if port is in use

Rate Limits (429 Errors)

Problem: Getting HTTP 429 responses from RPC.

Solution: Use a higher-tier RPC plan or add more RPC endpoints to distribute load.

price_tracker Errors

Problem: Errors related to price_tracker in logs.

Solution: Usually a transient RPC issue. The bot should auto-recover. If persistent, restart the bot.

Port Already in Use

Problem: Jupiter API can't start because port 18080 is occupied.

Solution:

kill $(lsof -t -i:18080)

Transaction Too Large

Problem: Transactions exceed size limits.

Solution: Reduce the number of accounts per trade by adjusting MAX_ACCOUNTS in the Jupiter config.

No Opportunities Found

Possible causes:

• Low-volume intermediary mints
• Market is too efficient (no price discrepancies)
• RPC too slow

Nothing Lands (Jito)

Possible causes:

• Tip too low — increase TIP_LAMPORTS
• Competition from other bots
• Stale quotes by the time the bundle is processed

Nothing Lands (Spam)

Possible causes:

• Priority fee too low
• Sending RPCs too slow
• Transaction expires before processing

libssl Error

Problem: libssl.so not found.

Solution:

sudo apt install libssl-dev

High Quote Time

Problem: Quoting takes too long (>2 seconds).

Solution: Reduce MAX_ACCOUNTS, use faster RPC, or reduce intermediary mint count.

Error Codes

• 6001: Program error — usually means the trade was no longer profitable at execution time
• 1771: Computational budget exceeded — increase compute unit limit

SOL Balance Discrepancy

Problem: SOL balance seems lower than expected.

Explanation: Token accounts require rent (~0.002 SOL each). When you create new token accounts for intermediary mints, rent is deducted from your SOL balance.