ScreenerBot
DocsReferenceTroubleshooting
ScreenerBot
ScreenerBot

Need Help?

Join our community for support, updates, and trading discussions.

Telegram CommunityFollow on X (Twitter)Contact Support

Troubleshooting

Solutions to common issues and problems you may encounter while using ScreenerBot.

Quick Diagnostics

First Steps

1. Check Dashboard

Visit localhost:8080 - service status shows health

2. Check Logs

Run grep ERROR logs/*.log

3. Restart Bot

Kill and restart: pkill -f screenerbot && ./screenerbot

Connection Issues

RPC Connection Fails

Symptoms:

  • Timeout errors in logs
  • 429 rate limit errors
  • Missing price data

Solutions:

  • Check RPC URL in config
  • Add backup RPC endpoints
  • Upgrade to premium RPC

WebSocket Disconnect

Symptoms:

  • Transaction stream stops
  • No new entries detected
  • "WS disconnected" logs

Solutions:

  • Wait for auto-reconnect (30s)
  • Check internet connection
  • Restart bot if persistent

Trading Issues

Swap Fails

Common Causes:

  • Slippage too low
  • Insufficient SOL balance
  • Pool liquidity drained
  • Price moved too fast

Solutions:

  • Increase slippage to 3-5%
  • Keep min 0.1 SOL for fees
  • Enable auto priority fees

No Entries Detected

Check These:

  • Auto-trading enabled?
  • Max positions reached?
  • Filters too strict?
  • All tokens blacklisted?

Solutions:

  • Check Filtering page stats
  • Review rejected tokens
  • Relax filters gradually

Performance Issues

High Resource Usage

Normal Ranges:

  • •CPU: 5-20% idle, 40-60% active
  • •RAM Usage: 200-500 MB typical

If Excessive:

  • Reduce max positions
  • Reduce OHLCV intervals
  • Restart bot daily

Dashboard Slow/Unresponsive

Common Causes:

  • Large database files
  • Too many open positions
  • Browser cache full

Solutions:

  • Clear browser cache
  • Use Chrome/Firefox
  • Reduce polling interval

Network & Firewall Issues

API Connection Blocked

Symptoms:

  • "Could not connect to API" errors
  • Token data not updating
  • Security analysis unavailable
  • Swaps failing at quote stage

Solutions:

  • Whitelist API domains in firewall
  • Check corporate proxy settings
  • Disable VPN temporarily to test
  • See Network Requirements for full list

Token Images Not Loading

Why It Happens:

  • Images from external CDNs/IPFS
  • Firewall blocking image hosts
  • Token project server offline
  • IPFS gateway rate limited

Solutions:

  • Allow cdn.dexscreener.com
  • Allow IPFS gateways (ipfs.io)
  • Images are cosmetic—trading works

Quick Firewall Whitelist

Minimum domains to whitelist for basic functionality:

Your RPC Provider

Blockchain access

api.jup.ag

Swap routing

api.dexscreener.com

Market data

For the complete list of endpoints, see our Network Requirements documentation.

Database Issues

Database Corruption / Lock

Symptoms:

  • "database is locked" error
  • Missing historical data
  • Positions not saving

Solutions:

  • Stop bot completely first
  • Backup data/*.db files
  • Delete -wal/-shm files
  • Run VACUUM if still slow

Warning: Never manually edit .db files while bot is running. Always stop first.

Security Issues

Rugpull / Scam Exposure

If You Got Rugged:

  • 1.Close position immediately (manual)
  • 2.Add token to blacklist
  • 3.Review filter settings
  • 4.Check why filters passed it

Prevention:

  • Enable all Rugcheck filters
  • Set higher liquidity minimum
  • Use strict security mode
  • Check token age filter

Useful Debug Commands

View Recent Errors

grep ERROR logs/screenerbot*.log | tail -20

Debug RPC Issues

./screenerbot --debug-rpc

Debug Trading

./screenerbot --debug-trader

Check Database Size

du -sh data/*.db

Monitor Live Logs

tail -f logs/screenerbot*.log

Reset Bot

pkill -f screenerbot && ./screenerbot

Events System (Debug Logs)

Built-in Events Recording

ScreenerBot includes an events recording system for detailed troubleshooting. This is disabled by default and can be enabled in the configuration.

What it records:

  • Token discoveries and filtering
  • Swap attempts and results
  • Position opens/closes
  • System errors and warnings
  • Pool and transaction data

What it NEVER records:

  • Private keys or seed phrases
  • Passwords or encrypted data
  • RPC authentication tokens

Sharing with Support: If you need help, you can export and share event logs. We recommend reviewing the data before sharing. Event logs contain wallet addresses (public), token mints, and swap response data in JSON format—nothing private. This helps us debug issues on your behalf.

Still Need Help?

Contact Support

When reporting an issue, please include:

  • •Bot version (check Dashboard footer)
  • •Relevant log excerpts
  • •Steps to reproduce the issue
  • •Your config.toml (redact sensitive info)

Related Topics

Network Requirements
Reference

Full API endpoints and firewall whitelist

Best Practices
Guide

Recommended settings and strategies

Configuration
Reference

All config file options