Quick Diagnosis
Start here. Find your symptom, get to the solution fast.| What You’re Seeing | Likely Cause | Jump To |
|---|---|---|
| Scans always return “safe” | Rules not loaded or L1 disabled | No Detections |
| High latency (>100ms) | L2 model loading on each scan | Performance Issues |
ModuleNotFoundError | Missing optional dependency | Installation Issues |
| Too many false positives | Confidence threshold too low | False Positives |
| ”API key invalid” | Key not set or expired | API Key Issues |
| Import errors | Wrong Python version or missing deps | Dependency Issues |
| SIEM not receiving events | Webhook misconfigured | SIEM Integration |
| MCP gateway not starting | Configuration or upstream issues | MCP Gateway |
raxe: command not found | PATH not configured | CLI Issues |
| Database locked errors | Multiple processes or crash | Database Issues |
Quick Diagnostics
Run the health check first - it catches most issues:No Detections
Symptoms:raxe scan "Ignore all previous instructions"returns no threats- All scans show
has_threats: false - Known attack prompts pass through
- Always run
raxe doctorafter installation - Include health check in deployment scripts
- Monitor for
total_detections: 0in telemetry
Performance Issues
Symptoms:- Scans taking >100ms consistently
- First scan is slow, subsequent scans faster
- High CPU usage during scans
- Warm up RAXE at application startup
- Use L1-only for real-time paths, L2 for batch/async
- Monitor p95 latency in production
False Positives
For systematic false positive management, see Suppressions.
- Legitimate business text flagged as threats
- High detection rate on normal content
- Users complaining about blocked prompts
- Start with
on_threat="log"mode to gather data before blocking - Set confidence threshold based on your traffic patterns
- Create allowlists for known business terminology
- Review detection logs weekly to tune thresholds
API Key Issues
Symptoms:RAXE-AUTH-001: Invalid API key formatRAXE-AUTH-002: API key expiredAuthentication failederrors
- Use environment variables, not hardcoded keys
- Rotate keys periodically
- Set up key expiration alerts
Installation Issues
Symptoms:pip install raxefailsModuleNotFoundError: No module named 'raxe'- Dependency conflicts
pip install fails
Python version error
ML dependencies fail
- Always use virtual environments
- Pin Python version in
pyproject.tomlor.python-version - Test installation in CI before deploying
Dependency Issues
Symptoms:ImportErrorwhen using integrationsModuleNotFoundError: No module named 'langchain'- Version conflicts between packages
- Use
pip install raxe[integration_name]for integrations - Lock dependencies with
pip freeze > requirements.txt - Test imports in CI
SIEM Integration
Symptoms:- Events not appearing in Splunk/CrowdStrike/Sentinel
RAXE-WEBHOOK-001: Connection refused- Webhook timeout errors
Splunk HEC
CrowdStrike Falcon LogScale
Microsoft Sentinel
Common fixes
- Test SIEM connectivity before deploying
- Set up alerts for webhook failures
- Use retry logic for transient failures
MCP Gateway
Symptoms:raxe mcp gatewayfails to start- Gateway starts but Claude can’t connect
- Upstream MCP server not proxied
Gateway won’t start
Claude Desktop configuration
Testing the MCP server directly
- Test MCP configuration before deploying
- Use
raxe doctorto verify installation health - Use absolute paths in config if PATH issues occur
CLI Issues
Command not found
Symptom:raxe: command not found
Solutions:
Colors not displaying
Symptom: Output shows escape codes instead of colors Solutions:Database Issues
Database locked
Symptom:RAXE-DB-002: Database locked
Solutions:
Database corrupted
Symptom:RAXE-DB-003: Database corrupted
Solution:
Configuration Issues
Config file not found
Symptom:RAXE-CONFIG-001: Configuration file not found
Solution:
Network Issues
Telemetry fails
Symptom:RAXE-NET-001: Connection refused for telemetry
Note: Telemetry failures are silent by default and don’t affect scanning.
Check connectivity:
Behind corporate proxy
Solution:ML Issues
ML model not loading
Symptom:RAXE-ML-002: Model load failed
Solutions:
ML too slow
Symptom: L2 scans taking >100ms See Performance Issues above.Getting More Help
Enable debug logging
Generate diagnostic report
Contact support
- GitHub Issues: raxe-ai/raxe-ce
- Slack: RAXE Community
- Twitter/X: @raxeai
