IniLerm
Forum Replies Created
-
Forum: Plugins
In reply to: [Advanced IP Blocker] Search Blocked IPsHi @martje65,
Version 8.7.3 is now available.
- FEATURE: Added search functionality to the “Blocked IPs” list, allowing admins to quickly find specific IPs or ranges.
- FIX: Resolved “Table doesn’t exist” error in the Audit Log when the feature is inactive.
- FIX: Corrected “Array to string conversion” warning in Community Blocklist updates due to complex whitelist formats.
- IMPROVEMENT: Enhanced robustness of IP whitelisting logic during community feed synchronization.
Thank you.
Forum: Plugins
In reply to: [Advanced IP Blocker] .htaccess Require vs DenyHi @martje65,
As mentioned, we use both mod_authz_core (Apache 2.4+) and !mod_authz_core (Apache 2.2) to ensure the plugin works on any hosting environment without crashing.
Even though Apache 2.4 is the standard today, many legacy hosting providers still run older configurations or hybrid setups. If we only used the modern syntax (Require not ip), sites on older servers would instantly crash with a “500 Internal Server Error” upon activation.
By wrapping the rules in IfModule, we guarantee safety: the server ignores the block it doesn’t understand and executes the one it does. It’s a “safety first” approach.
Best regards,IniLerm
Forum: Plugins
In reply to: [Advanced IP Blocker] Search Blocked IPsHi @martje65,
You are absolutely right. As the blocklist grows, finding a specific IP becomes difficult without a search bar.
I have added this to our roadmap for the next release (v8.7.3). We will include a search field in the “Blocked IPs” tab so you can instantly check if an IP is already listed.
Thank you for the suggestion!Forum: Plugins
In reply to: [Advanced IP Blocker] .htaccess Require vs DenyHi @martje65,
That is an excellent observation!
We include both syntaxes intentionally to ensure 100% compatibility with all server environments, regardless of their age or configuration.
Require not ip is the modern syntax for Apache 2.4.
Deny from is the older syntax for Apache 2.2.
By wrapping them in (for modern servers) and (for older ones), we ensure that the plugin works perfectly everywhere without causing “500 Internal Server Errors” on older hosting platforms that don’t understand the new commands.
The server only executes the block that matches its version, so there is no performance penalty for having both.
Best regards,Advanced IP Blocker Team
- This reply was modified 8 months ago by IniLerm.
Hi @martje65,
Thank you so much for the detailed bug report and the stack trace! You are absolutely right; the plugin was attempting to query the logging table (wp_advaipbl_activity_log) on that specific admin tab even when the feature was inactive or the table hadn’t been created yet.
I have just implemented a fix in our development branch to check for the table’s existence before running any queries, which will prevent these errors entirely. This patch will be included in the next release (v8.7.3), which I plan to push within the next 24-48 hours after final testing.
Temporary Workaround: In the meantime, you can stop these errors from filling up your logs by temporarily enabling the “Activity Audit Log” option in the Settings tab. Enabling it triggers the table creation, which satisfies the query requirements even if you disable it afterward (since the table structure will remain in the database).
Thanks again for helping us improve Advanced IP Blocker!
Best regards,
IniLerm
Forum: Plugins
In reply to: [Advanced IP Blocker] Undefined variable $typeHi @martje65,
Version 8.7.2 is now available and fixed.
Thank you.
Forum: Plugins
In reply to: [Advanced IP Blocker] Bug Report: PHP Deprecated warning in PHP 8.1+Forum: Plugins
In reply to: [Advanced IP Blocker] Bug Report: PHP Deprecated warning in PHP 8.1+Hi @xemita,
You nailed it! Thank you so much for the detailed report.
After a deep code review following your lead, we identified that our hook on status_header was indeed registered as an add_action (which returns void/null) instead of an add_filter (which expects a return value). This was causing the chain break in PHP 8.1+ environments.
Status:
We have already fixed this in our development branch. The patch will be included in version 8.7.2, which is scheduled for release within the next 24 hours after final testing.Thanks again for your expert contribution to the project!
Best regards,
Advanced IP Blocker Team
Forum: Plugins
In reply to: [Advanced IP Blocker] Bug Report: PHP Deprecated warning in PHP 8.1+Hi @xemita,
Thank you for reporting this.
We would like to clarify that Advanced IP Blocker is fully compatible with PHP 8.1+. However, for the best security and performance standards, we always recommend keeping your server updated to the latest stable versions (currently PHP 8.3 or 8.4).
We have double-checked our codebase regarding header handling and have not identified any direct function calls that would pass a
nullvalue in a standard environment. This suggests the warning might be triggered by a conflict with another active plugin, your current theme, or a specific server configuration interacting with the request.
Unfortunately, without seeing the full context, it is difficult to pinpoint the exact source of this conflict. Important: Since this is a public forum, we strongly advise against posting your full stack trace or error log here, as it may contain sensitive information about your server structure.
If you are able to isolate the specific filename and line number where the warning originates (without sharing the full path), please let us know, and we will be happy to investigate further.
Best regards,
Advanced IP Blocker Team
Forum: Reviews
In reply to: [Advanced IP Blocker] Great plugin and great support.Hi @martje65,
Thank you so much for the 5-star rating! ⭐⭐⭐⭐⭐
We truly appreciate your feedback and your help in reporting the warning earlier. Proactive users like you help us make the plugin better for everyone.
If you ever need anything else, just let us know!
Forum: Plugins
In reply to: [Advanced IP Blocker] Undefined variable $typeHi @martje65,
Thank you very much for reporting this.
We have reviewed your log and can confirm this is a minor PHP Warning related to the notification display logic in the admin area.
Is this dangerous? Absolutely not. This is strictly a cosmetic notice that occurs after a whitelist action and does not affect the security functionality, the blocking engine, or the integrity of your site in any way.
Resolution: We have already patched this in our development version. Since it is a low-severity notice (not an error), we will include the fix in our next scheduled maintenance release (v8.7.2), which we expect to deploy within the next 24-48 hours.
We appreciate you helping us keep the plugin clear of warnings!
Best regards,
Advanced IP Blocker Team
Forum: Plugins
In reply to: [Advanced IP Blocker] WordPress REST API is returning a 404 pageHi @cousineddie,
Thank you for reaching out!
Based on the error (“REST API returning 404”), this is highly unlikely to be caused by Advanced IP Blocker.
If our plugin were blocking the connection, you would see a 403 Forbidden or a “Challenge” screen, not a 404 (Not Found).
A 404 error on the API usually means WordPress has “forgotten” how to route the URL.
Quick Fix (Permalinks):
This solves 90% of Elementor/API 404 issues:
Go to Settings > Permalinks in your WordPress dashboard.
Do NOT change anything.
Just click the “Save Changes” button at the bottom.
This forces WordPress to regenerate its internal rewrite rules and often fixes the API.
To verify it’s not AIB:
You can temporarily enable “Global URL Exclusions” for the Elementor API to be 100% sure.
Go to Security > Settings > General.
Add /wp-json/elementor/ to the “Global URL Exclusions” list.
Save.
If the error persists after saving permalinks and excluding the URL, then it is definitely a server/hosting configuration issue, not the firewall.
Best regards,Advanced Ip Blocker Team
Forum: Plugins
In reply to: [Advanced IP Blocker] Suggestion for improvement – automatic DeepScansHi @wassi007,
That is a very insightful observation!
Security scanners often differ slightly in their vulnerability databases (WPScan vs. Wordfence vs. CVE). In this specific case, the difference between version 4.1.21 and 4.1.22 is likely a minor patch that one database considers “fixed” and another “still risky.”
However, here is the key takeaway to give you peace of mind:
A vulnerability report is just a warning, not a hack. For a hacker to actually exploit that vulnerability (like the “Missing Authorization” one you linked), they need to send a very specific, malicious request to your site.
This is where Advanced IP Blocker protects you:
Even if a plugin has a vulnerability, our WAF (Web Application Firewall) and Advanced Rules are designed to block the malicious requests trying to exploit it.
The scanner tells you “The door lock is weak”.
The firewall acts as a security guard standing in front of the door, stopping anyone from even touching the lock.
So, while updating is always the best practice, you don’t need to panic over every yellow warning. Your active defenses (WAF, Rate Limiting, AIB Network) are shielding you from the exploitation attempts.
Switching to our DeepScan (powered by AIB Intelligence – vulnerabilities.production.json standard compatibility) is a great idea because it integrates directly with your active defenses!
Best regards,Advanced IP Blocker Team
Forum: Plugins
In reply to: [Advanced IP Blocker] Suggestion for improvement – automatic DeepScansHello @wassi007,
Thank you so much for your donation and your kind words! We really appreciate your support.
regarding your suggestions:
- DeepScan Email Notifications: That is an excellent idea. We agree that receiving “empty” reports can be redundant. We have added this to our roadmap and will implement an option in the upcoming version 8.7.1 to only send the automatic scan report email if a vulnerability or issue is actually detected. The manual scan button will continue to send the report regardless, as you suggested.
- Google XML Sitemaps Vulnerability: We have checked our database and the CVE-2025-64632 record. This vulnerability affects XML Sitemap Generator for Google in versions <= 4.1.21.
The latest version is 4.1.22 (released recently), which patches this issue. If DeepScan is not showing it as vulnerable, it is likely because you have successfully updated to version 4.1.22. DeepScan checks the exact installed version against the vulnerability database to avoid false positives. If you were still on 4.1.21, it would definitely trigger the alert.
Thanks again for your feedback!
Best regards,
Advanced Ip Blocker Team