Troubleshooting
Common issues and solutions
Agent Connection Issues
Dashboard shows "Agent Offline"
-
Check agent is running:
docker ps | grep traefik-agent -
Verify agent health:
curl http://localhost:5000/api/logs/status -
Check token match: Ensure
TRAEFIK_LOG_DASHBOARD_AUTH_TOKENon the agent matchesAGENT_API_TOKENon the dashboard. -
Network connectivity: If using Docker, ensure both containers are on the same network.
Cannot connect to remote agents
The dashboard requires direct HTTP connectivity to agents. Options:
- VPN/Tunnel: Use Tailscale, WireGuard, or similar to connect networks securely.
- Reverse Proxy: Put the agent behind Traefik with authentication and use the proxied URL.
- Expose Port: Only recommended for testing, not production.
Log Parsing Issues
No logs appearing in dashboard
-
Verify log path: Check
TRAEFIK_LOG_DASHBOARD_ACCESS_PATHpoints to the correct file.docker exec traefik-agent ls -la /logs/ -
Check log format: Ensure
TRAEFIK_LOG_DASHBOARD_LOG_FORMATmatches your Traefik configuration (json or common). -
Verify permissions: The agent needs read access to log files.
Logs show but metrics are wrong
- Check time range: The dashboard defaults to showing recent data. Adjust the time range filter.
- Clear position file: Delete
/data/.positionin the agent container to re-read logs from the beginning.
GeoIP Issues
Geographic data not showing
GeoIP is handled automatically by the dashboard using geolite2-redist. No configuration needed.
- Check dashboard logs: Look for GeoIP initialization errors.
- Verify IPs are public: Private IPs (10.x.x.x, 192.168.x.x, etc.) cannot be geolocated.
- Container restart: Restart the dashboard container to re-initialize GeoIP databases.
All IPs show as "Unknown" location
- Private IP ranges cannot be geolocated
- The 11.0.0.0/8 range is reserved and shows as "Unknown"
- Check if requests are coming through a proxy that masks real IPs
Environment Agent
Cannot delete agent from UI
The agent configured via AGENT_API_URL and AGENT_API_TOKEN environment variables is protected and cannot be deleted from the UI.
This is by design to ensure you always have a primary agent connection. To change it:
- Update the environment variables in
docker-compose.yml - Restart the dashboard container
Multiple agents with same name
Each agent should have a unique name. If adding agents manually, use descriptive names like:
Production-DC1Staging-CloudEdge-Server-1
Alerting Issues
Discord notifications not sending
- Verify webhook URL: Test the webhook from Settings > Alerts > Webhooks.
- Check background scheduler: Ensure
ENABLE_BACKGROUND_SCHEDULER=true. - Dashboard must be running: Alerts are processed server-side but require the dashboard to be up.
Alerts firing too frequently
- Adjust threshold values in alert rules
- Increase the check interval (minimum 5 minutes)
- Use the "cooldown" period to prevent repeated alerts
Performance Issues
Dashboard is slow
- Reduce log display limit: Lower
NEXT_PUBLIC_MAX_LOGS_DISPLAY(default: 500). - Check agent performance: Monitor agent CPU/memory usage.
- Narrow time range: Use shorter time ranges for faster queries.
Agent consuming too much memory
- Check log file size: Very large log files can cause memory issues.
- Enable position tracking: Ensure the agent is only reading new entries.
- Use log rotation: Configure Traefik to rotate logs regularly.
Docker Issues
Permission denied on data volume
The dashboard runs as user 1001:1001 by default. Fix permissions:
mkdir -p ./data/dashboard
chown -R 1001:1001 ./data/dashboardContainer keeps restarting
Check container logs:
docker logs traefik-log-dashboard
docker logs traefik-log-dashboard-agentCommon causes:
- Missing required environment variables
- Invalid log file paths
- Database permission issues
Getting Help
- Documentation: Check the full documentation
- Discord: Join our community
- GitHub Issues: Report bugs