Skip to content

Commit 478609f

Browse files
author
jdv
committed
mini clean and content+
1 parent 383034d commit 478609f

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

crowdsec-docs/unversioned/getting_started/post_installation/health_check.mdx

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,13 +160,13 @@ If not, check the troubleshooting section below
160160
<details id="troubleshooting_service">
161161
<summary>CrowdSec Service Troubleshooting: is the CrowdSec service running?</summary>
162162

163-
164-
165163
</details>
166164
</details>
167165

168166
## 🔌 CrowdSec Connectivity checks
169167

168+
### *List the community-blocked IPs*
169+
170170
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.
171171
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.
172172

@@ -182,6 +182,8 @@ The CAPI allows your instance to receive a curated blocklist of malicious IP add
182182
2️⃣ If you see decisions listed, it means your Security Engine is successfully connected to the CAPI and receiving decisions.
183183
</details>
184184

185+
### Were all the tests successful ?
186+
185187
<details>
186188
<summary>🚨 Connectivity Troubleshooting</summary>
187189

@@ -201,6 +203,8 @@ The CAPI allows your instance to receive a curated blocklist of malicious IP add
201203

202204
## ✋🏻 Remediation checks
203205

206+
### *Validate Blocks or Captchas*
207+
204208
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.
205209

206210
::info A note on future improvements
@@ -235,6 +239,7 @@ or
235239
### Were all the tests successful ?
236240

237241
If you were successfully blocked, congratulations! Your remediation setup is working correctly. 🎉
242+
238243
You might want to continue to the next recommended steps:
239244
- Enroll your Security Engine to the [CrowdSec Console](/u/getting_started/post_installation/console/)
240245
- Then subscribe to more blocklists to benefit from additionnl proactive prevention

0 commit comments

Comments
 (0)