IniLerm

Advanced Ip Blocker version 8.7 is now available.

Go to Settings -> Notifications and enable Site Scanner Automation.

Enable Scheduled Scans -> Scan Frequency (Daily/Weekly) ->add Notification Email

Save changes.

Best regards,

Advanced IP Blocker Team

Hi @wassi007,

That is an excellent suggestion! You are thinking exactly along the same lines as our development roadmap.

Why it’s manual right now:
Since the Deep Scan relies on our central API to check thousands of plugin versions against the vulnerability database, we kept it manual in the initial release to ensure our infrastructure scales smoothly without overload.

Future Plan:
We absolutely plan to introduce Automatic Scheduled Scans (daily/weekly) with Email Alerts for critical vulnerabilities in a future update (aiming for v8.7 or v8.8). It is the next logical step to make the security completely “hands-off.”

Thank you for the feature request! It confirms we are moving in the right direction.

Best regards,

Advanced Ip Blocker Team

Hi @cousineddie,

That is an interesting error. The good news is that the HTTP status is 200 OK (with a data error 400), which usually means the request reached WordPress successfully and wasn’t hard-blocked by our firewall (which would return a 403 Forbidden).

However, it is possible that a security rule (like the WAF) might be interfering with the data payload being sent to that endpoint.

How to fix it (Whitelist the Endpoint):

To ensure Advanced IP Blocker allows full access to this specific service, you should add its URL to the exclusion list.

1. Go to Security > Settings > General Settings.
2. Find the “Global URL Exclusions” field.
3. Add this part of the URL on a new line:
   /optimization-detective/v1/url-metrics:store
4. Click Save.

This tells our plugin to completely ignore requests to that specific API endpoint, letting “Optimization Detective” handle them without interference.

Let me know if that clears the error!

Best regards,

The Advanced IP Blocker Team

Bonus Tip for Proactive Security:
Since you are configuring advanced blocking, I highly recommend checking your ASN Whitelist (Blocking Rules > ASN Blocking).
Adding the ASNs of critical services ensures they are never accidentally blocked by strict WAF rules or rate limiting. Here is a starter list you can copy:codeText

# Essential Crawlers and Services
AS15169 # Google LLC
AS8075 # Microsoft Corporation
AS2635 # Automattic Inc. (Jetpack)
AS32934 # Facebook, Inc.
AS5091 # Stripe, Inc.
AS17012 # PayPal, Inc.

This acts as a “safety net” for your essential integrations.

Hi @cousineddie,
That is an excellent question and I love your proactive mindset!

1. How you are already helping (Automatic Reporting):
   You are actually already helping the community! If you have enabled “Join Community Defense Network” in Settings > Threat Intelligence, your plugin automatically reports verified attacks (WAF blocks, Brute force, etc.) to our central server.
   Thanks to users like you, we have gathered over 50,000 malicious IPs in just one month, which are then distributed back to everyone via the “Community Blocklist”. So, by just using the plugin, you are actively protecting others.
2. Reporting to AbuseIPDB:
   We are currently developing a feature to allow direct reporting to AbuseIPDB. However, we are being very cautious with this implementation. Automated reporting carries a risk of “False Positives” (e.g., accidentally reporting a legitimate user who forgot their password). We are refining our validation logic to ensure we only report 100% confirmed threats to AbuseIPDB to maintain high data quality.
   Expect to see a “Report to AbuseIPDB” button in the Security Log in a future update (v8.7+)!
   Thanks again for your support and for helping build a safer web.
   Best regards,

The Advanced IP Blocker Team

HOW TO SETUP CLOUD EDGE DEFENSE (CLOUDFLARE)

Recommendation to prevent JavaScript challenges from being stored in the Cloudflare cache and to ensure they function correctly:

In your domain dashboard: Caching > Cache Rules

Create a new rule, eg. :

Rule name (required) -> ADVAIPBL – Challenge – Cookie

Field: Cookie -> Operator: equals -> Value: advaipbl_js_verified

Expression Preview -> (http.cookie eq “advaipbl_js_verified”)

and select Bypass cache

Hi @cousineddie,

This error usually happens when the API Token is valid (so the “Verify” button turns green) but it lacks the specific permission to modify the Firewall rules for your Zone.

Please try regenerating the token with these exact steps to ensure it has the “Write” capability:

1. Go to Cloudflare Dashboard > My Profile > API Tokens.
2. Click Create Token > Create Custom Token (at the bottom).
3. Permissions: (This is the critical part)
   • Zone > Firewall Services > Edit
   • (Optional): Zone > Zone > Read
4. Zone Resources:
   • Include > Specific zone > Select your domain.

If you used a pre-made template (like “Edit Zone DNS” or “WordPress”), it might not have the “Firewall Services” permission enabled by default.

Also, please double-check that the Zone ID you pasted matches exactly the one on your Cloudflare Overview page for that specific domain (sometimes users with multiple domains mix them up).

Let me know if a fresh Custom Token solves it!

Best regards,