Troubleshooting

What This Page Is For

Use this page when the dashboard loads but data, jobs, reports, or integrations are not working as expected.

Check Logs First

Most issues are visible in container logs:

docker compose logs -f dashboard
docker compose logs -f jobs_runner

Use dashboard logs for UI errors and jobs_runner logs for scheduled jobs, backtests, and Monte Carlo jobs.

Live OHLCV warnings are grouped once per trading cycle. An insufficient-history warning means the market does not yet have enough closed candles for the active strategy; a transient public-data warning means the exchange remained unavailable after safe retries. In both cases, BEC skips the affected symbols before making an order decision.

Missing Credentials

If Binance, Telegram, or AI features fail, check .env.

Required for trading and market data:

• binance_api
• binance_secret

Required for Telegram alerts:

• telegram_chat_id
• Telegram token values

Required only for AI analysis:

• OPENAI_API_KEY

No Backtesting Results

Check that jobs are enabled and running. Then open Backtesting > Backtesting Results and inspect the Backtesting Queue.

If jobs are stuck, restart the services:

docker compose restart

Missing Reports

Backtesting and Monte Carlo reports are stored under the persistent backtest results folder. In Docker, BEC links this path into:

/app/static/backtest_results

If a report is missing, rerun the selected backtest or Monte Carlo job and check the job log.

SQLite Web

SQLite web is available at:

http://localhost:8081

Docker Compose requires a non-empty SQLITE_WEB_PASSWORD in .env. Generate a strong value with openssl rand -base64 32 if the service fails to start because the variable is missing.

The port is bound only to 127.0.0.1 on the Docker host. For remote access, create an SSH tunnel:

ssh -L 8081:127.0.0.1:8081 user@your-server

Keep the tunnel open and browse to http://127.0.0.1:8081 locally.