Skip to main content

Troubleshooting BozoBot

This guide helps you diagnose and resolve common issues you might encounter when using BozoBot.

Connection Issues​

RPC Connection Problems​

Symptoms:

  • Error messages about unable to connect to RPC
  • Transactions timing out
  • Bot failing to start with RPC-related errors

Solutions:

  1. Check if your RPC endpoints are correct in the .env file
  2. Try adding multiple RPC endpoints for redundancy: 
    RPC_ENDPOINTS=https://rpc1.example.com,https://rpc2.example.com
  3. Verify your internet connection
  4. Check if the RPC provider is experiencing downtime
  5. Consider switching to a premium RPC provider for better reliability

WebSocket Connection Issues​

Symptoms:

  • "WebSocket connection failed" errors
  • Copy trading or price monitoring not working
  • Events not being detected properly

Solutions:

  1. Ensure your RPC_WEBSOCKET_ENDPOINT is correctly configured
  2. Verify the endpoint supports WebSocket connections (should start with wss://)
  3. Check if your firewall allows WebSocket connections
  4. Try an alternative WebSocket provider

Wallet Issues​

Insufficient Funds​

Symptoms:

  • "Insufficient funds" error messages
  • Failed transactions
  • Bot unable to execute trades

Solutions:

  1. Ensure your wallet has enough SOL for:
    • The trade amount (QUOTE_AMOUNT)
    • Transaction fees (typically 0.000005-0.001 SOL per transaction)
    • MEV protection fees if enabled
  2. Reduce your QUOTE_AMOUNT or MAX_OPEN_POSITIONS
  3. Transfer more SOL to your trading wallet

Private Key Issues​

Symptoms:

  • "Invalid private key" errors
  • Authentication failures
  • Unable to sign transactions

Solutions:

  1. Verify your private key is correctly formatted in the .env file
  2. Ensure there are no spaces or line breaks in the private key
  3. Consider generating a new wallet for trading if issues persist
  4. Never share your private key or .env file with anyone

Transaction Issues​

Failed Transactions​

Symptoms:

  • "Transaction failed" errors
  • "Blockhash not found" messages
  • Timeout errors when buying or selling

Solutions:

  1. Increase slippage tolerance: 
    BUY_SLIPPAGE=25
    SELL_SLIPPAGE=35
  2. Increase priority fees: 
    BUY_PRIORITY_FEE=0.000250
    SELL_PRIORITY_FEE=0.000250
  3. Try enabling MEV protection: 
    BUY_TRANSACTION_DISPATCHER=jito
  4. Increase transaction timeout: 
    CONFIRM_TRANSACTION_TIMEOUT_SECONDS=180

Transaction Timeouts​

Symptoms:

  • "Transaction confirmation timeout" errors
  • Transactions getting stuck
  • Long delays in trade execution

Solutions:

  1. Check network congestion on Solana Explorer
  2. Increase your priority fees to push your transactions through faster: 
    BUY_PRIORITY_FEE=0.000500
    SELL_PRIORITY_FEE=0.000500
  3. Consider using a more responsive RPC endpoint
  4. Try enabling SKIP_PREFLIGHT=true for faster submissions

Mode-Specific Issues​

Sniffer Mode Problems​

Symptoms:

  • Not detecting tokens in channels
  • Authentication issues with Telegram
  • Error accessing Telegram channels

Solutions:

  1. Verify your Telegram session is valid
  2. Ensure you're subscribed to the channels you're monitoring
  3. Check channel IDs are correct in TELEGRAM_IDS_TO_SNIFF
  4. Increase check interval if rate-limited: 
    TELEGRAM_CHECK_INTERVAL_MS=3000
  5. For Discord, verify your authentication token is valid

Copy Trading Issues​

Symptoms:

  • Not detecting trades from target wallets
  • Delayed copying of transactions
  • Missed transactions

Solutions:

  1. Verify wallet addresses in COPY_TRADE_WALLETS are correct
  2. Set up gRPC for faster detection: 
    GRPC_ENDPOINT=your_grpc_endpoint
    GRPC_KEY=your_grpc_key
  3. Ensure COPY_TRADE_PROCESS_SAME_TOKEN_EVERY_SECONDS isn't too high
  4. Check if the target wallets are still active

Liquidity Sniping Issues​

Symptoms:

  • Missing token launches
  • Errors about pool not found
  • Buying tokens that don't meet criteria

Solutions:

  1. Verify your filter settings aren't too restrictive
  2. Increase priority fees for faster execution: 
    BUY_PRIORITY_FEE=0.000350
  3. If using snipe list, check addresses are correct
  4. Try lowering SKIP_IF_MINTED_SECONDS_AGO to catch newer tokens

Filter Issues​

Token Filtering Too Strict​

Symptoms:

  • Bot not buying any tokens despite available opportunities
  • "Token doesn't meet criteria" messages

Solutions:

  1. Loosen social filter requirements: 
    HAS_ANY_SOCIAL=false
    HAS_TELEGRAM=false
    HAS_TWITTER=false
    HAS_WEBSITE=false
  2. Reduce minimum liquidity requirements: 
    MIN_SOL_IN_POOL=3
  3. Disable security checks temporarily to test: 
    CHECK_RENOUNCED_AND_FREEZABLE=false

Token Filtering Too Loose​

Symptoms:

  • Buying too many low-quality tokens
  • High rate of losses
  • Buying obvious scam tokens

Solutions:

  1. Increase social requirements: 
    HAS_ANY_SOCIAL=true
  2. Increase minimum liquidity: 
    MIN_SOL_IN_POOL=10
  3. Enable all security checks: 
    CHECK_RENOUNCED_AND_FREEZABLE=true
    CHECK_MUTABLE=true

System Issues​

High CPU/Memory Usage​

Symptoms:

  • System becoming unresponsive
  • Bot crashing due to resource limits
  • Slow performance

Solutions:

  1. Reduce the number of monitored channels or wallets
  2. Increase check intervals to reduce frequency of operations
  3. Close other resource-intensive applications
  4. Consider running on a dedicated server or VPS

Log File Growing Too Large​

Symptoms:

  • Disk space warnings
  • Slow file operations
  • System performance degradation

Solutions:

  1. Set up log rotation (see Running 24/7 AFK guide)
  2. Reduce log verbosity: 
    LOG_LEVEL=info
  3. Periodically clear old log files
  4. Redirect output to /dev/null if logs aren't needed: 
    ./bozobot > /dev/null 2>&1

Feature-Specific Issues​

Stop Loss/Take Profit Not Triggering​

Symptoms:

  • Positions not being sold at configured levels
  • Trading levels appear to be ignored

Solutions:

  1. Verify your TRADING_LEVELS format is correct: 
    TRADING_LEVELS=-30%:100%,40%:100%
  2. Ensure your CHECK_PRICE_INTERVAL_SECONDS isn't too high
  3. Check logs to see if levels are being detected but transactions are failing
  4. Verify there's enough liquidity for the token to execute sells

MEV Protection Not Working​

Symptoms:

  • Still experiencing front-running
  • No indication of protected transactions in logs
  • Errors about MEV services

Solutions:

  1. Check if your BUY_PRIORITY_FEE and SELL_PRIORITY_FEE are sufficient
  2. Verify you're using the correct dispatcher: 
    BUY_TRANSACTION_DISPATCHER=jito
    SELL_TRANSACTION_DISPATCHER=jito
  3. For Bloxroute, verify your API key is correct
  4. Try an alternative MEV protection service

Recovering from Crashes​

If BozoBot crashes or stops unexpectedly:

  1. Check the log files for error messages
  2. Fix any configuration issues identified in the logs
  3. Restart the bot: ./bozobot
  4. Consider setting up auto-restart mechanisms (see Running 24/7 AFK)

Getting Help​

If you're still experiencing issues after following this troubleshooting guide:

  1. Review your log files for specific error messages
  2. Check for recent updates or known issues
  3. Reach out to the community on our Discord server
  4. Provide detailed information about your issue, including:
    • Error messages
    • Your configuration (with private keys removed)
    • Steps to reproduce the problem
    • System specifications