You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: crowdsec-docs/unversioned/getting_started/post_installation/health_check.mdx
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,13 +160,13 @@ If not, check the troubleshooting section below
160
160
<detailsid="troubleshooting_service">
161
161
<summary>CrowdSec Service Troubleshooting: is the CrowdSec service running?</summary>
162
162
163
-
164
-
165
163
</details>
166
164
</details>
167
165
168
166
## 🔌 CrowdSec Connectivity checks
169
167
168
+
### *List the community-blocked IPs*
169
+
170
170
Let's check that your Security Engine can communicate with the CrowdSec Central API (CAPI). This connection is essential for participating in the community and protecting your setup with the collective intelligence of the network.
171
171
The CAPI allows your instance to receive a curated blocklist of malicious IP addresses identified and verified by the entire CrowdSec network. This proactive defense, known as the Community Blocklist, protects you from aggressors before they even target your services. It also allows your Security Engine to report the malicious IPs it detects, contributing to the strength of the community.
172
172
@@ -182,6 +182,8 @@ The CAPI allows your instance to receive a curated blocklist of malicious IP add
182
182
2️⃣ If you see decisions listed, it means your Security Engine is successfully connected to the CAPI and receiving decisions.
183
183
</details>
184
184
185
+
### Were all the tests successful ?
186
+
185
187
<details>
186
188
<summary>🚨 Connectivity Troubleshooting</summary>
187
189
@@ -201,6 +203,8 @@ The CAPI allows your instance to receive a curated blocklist of malicious IP add
201
203
202
204
## ✋🏻 Remediation checks
203
205
206
+
### *Validate Blocks or Captchas*
207
+
204
208
Now that we've confirmed that the Security Engine can detect threats, let's verify that your bouncers are correctly applying decisions and blocking malicious IPs.
205
209
206
210
::info A note on future improvements
@@ -235,6 +239,7 @@ or
235
239
### Were all the tests successful ?
236
240
237
241
If you were successfully blocked, congratulations! Your remediation setup is working correctly. 🎉
242
+
238
243
You might want to continue to the next recommended steps:
239
244
- Enroll your Security Engine to the [CrowdSec Console](/u/getting_started/post_installation/console/)
240
245
- Then subscribe to more blocklists to benefit from additionnl proactive prevention
0 commit comments