You may see the IDPS/WAF of CrowdSec referred to as "Security Engine" and Bouncers referred to as "Remediation Components" within new documentation.
This is to better reflect the role of each component within the CrowdSec ecosystem.
Troubleshooting
We have extended our troubleshooting documentation to cover more common issues and questions.
If you have suggestions, please open an issue here.
Also, check our 🩺 Stack Health-Check page to verify that Detection, Community Sharing, and Remediation are working properly.
Console Health Check Issues
If you received a health check alert from the CrowdSec Console, check out the Console Health Check Issues page for a complete list of issues, their trigger conditions, and dedicated troubleshooting guides.
Troubleshooting by Topic
Community support
Please try to resolve your issue by reading the documentation. If you're unable to find a solution, don't hesitate to seek assistance in:
Enterprise plan
If you are on an Enterprise plan, you can use dedicated support via the Console:
Stack Health issues list
| Issue | Criticality | Summary | Resolution |
|---|---|---|---|
| Integration for Firewall Offline | 🔥 Critical | Firewall has not pulled from BLaaS endpoint for 24+ hours | Troubleshooting |
| Integration for Firewall Pulling Zero IPs | ⚠️ High | Firewall BLaaS integration is content is empty | Troubleshooting |
| Integration for RC Offline | 🔥 Critical | Remediation Component has not pulled from endpoint for 24+ hours | Troubleshooting |
| Log Processor No Alerts | ⚠️ High | Log Processor has not generated alerts in 48 hours | Troubleshooting |
| Log Processor No Logs Parsed | 🔥 Critical | Logs read but none parsed in the last 48 hours | Troubleshooting |
| Log Processor No Logs Read | 🔥 Critical | No logs acquired in the last 24 hours | Troubleshooting |
| Log Processor Offline | 🔥 Critical | Log Processor has not checked in with LAPI for 24+ hours | Troubleshooting |
| Security Engine No Alerts | ⚠️ High | No alerts generated in the last 48 hours | Troubleshooting |
| Security Engine No RC | 💡 Reco. | Security Engine has no Remediation Component registered | Troubleshooting |
| Security Engine No Active RC | 🔥 Critical | All registered Remediation Components have been inactive for 24+ hours | Troubleshooting |
| Security Engine Offline | 🔥 Critical | Security Engine has not reported to Console for 24+ hours | Troubleshooting |
| Security Engine Too Many Alerts | ⚠️ High | More than 250,000 alerts in 6 hours | Troubleshooting |