Title: IniLerm's Replies | WordPress.org

---

# IniLerm

  [  ](https://wordpress.org/support/users/inilerm/)

 *   [Profile](https://wordpress.org/support/users/inilerm/)
 *   [Topics Started](https://wordpress.org/support/users/inilerm/topics/)
 *   [Replies Created](https://wordpress.org/support/users/inilerm/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/inilerm/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/inilerm/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/inilerm/engagements/)
 *   [Favorites](https://wordpress.org/support/users/inilerm/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 266 total)

1 [2](https://wordpress.org/support/users/inilerm/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/inilerm/replies/page/3/?output_format=md)…
[16](https://wordpress.org/support/users/inilerm/replies/page/16/?output_format=md)
[17](https://wordpress.org/support/users/inilerm/replies/page/17/?output_format=md)
[18](https://wordpress.org/support/users/inilerm/replies/page/18/?output_format=md)
[→](https://wordpress.org/support/users/inilerm/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] I see a message in my console: “…and Register the AIB Network Integration”](https://wordpress.org/support/topic/i-see-a-message-in-my-console-and-register-the-aib-network-integration/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 days, 3 hours ago](https://wordpress.org/support/topic/i-see-a-message-in-my-console-and-register-the-aib-network-integration/#post-19021435)
 * hi [@stippeltje404](https://wordpress.org/support/users/stippeltje404/)
 * If you have a spare moment, leaving a 5-star review would be amazing. It helps
   us grow and reach more people who need simple, powerful security.
 * [👉 Rate Advanced IP Blocker here](https://wordpress.org/support/plugin/advanced-ip-blocker/reviews/#new-post)
    -  This reply was modified 2 days, 2 hours ago by [IniLerm](https://wordpress.org/support/users/inilerm/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] I see a message in my console: “…and Register the AIB Network Integration”](https://wordpress.org/support/topic/i-see-a-message-in-my-console-and-register-the-aib-network-integration/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 days, 3 hours ago](https://wordpress.org/support/topic/i-see-a-message-in-my-console-and-register-the-aib-network-integration/#post-19021406)
 * Hi [@stippeltje404](https://wordpress.org/support/users/stippeltje404/),
 * Welcome to Advanced IP Blocker! I’m glad to hear you got the API key issue sorted
   out.
 * To answer your questions about monitoring and viewing the block details:
 * **1. Viewing Block Details & IPs:** To see exactly why those 6 requests from 
   your country were blocked and to find out their IP addresses, please navigate
   in your WordPress dashboard to **Advanced IP Blocker -> Security -> Logs & Sessions-
   > Security Log**. This tab provides a complete, timestamped history of all security
   events and blocks.
 * **2. Managing Blocked IPs (False Positives):** Since you mentioned you just cloned
   the website, it’s possible you triggered a strict security rule by accident. 
   You can go to **Threat Management -> Blocked IPs**. There, you will see a list
   of all currently active blocked IPs, and you can easily unblock them if they 
   are false positives.
 * **3. Live Traffic Monitoring:** Regarding live traffic, our plugin focuses strictly
   on monitoring and logging _security events, attacks, and blocks_. It doesn’t 
   log regular, safe visitor traffic (like Google Analytics would), as doing so 
   would unnecessarily consume your server’s database and slow down your site.
 * **A quick tip for new users:** Since you are just getting started, I highly recommend
   exploring the **Settings** tab. To ensure maximum compatibility and avoid accidentally
   blocking legitimate users, many of our most powerful advanced features are disabled
   by default. You can test and enable them gradually as you get comfortable with
   the plugin!
 * For example, if you consider yourself an advanced user and want to see the exact
   malicious code hackers are trying to send, you can turn on **“Enable Advanced
   Payload Logging (Opt-in)”** in the Settings. This will add deep forensic details(
   like captured payloads and challenge data) directly into your Security Logs.
 * Let us know if you have any other questions while you explore the plugin. We’re
   here to help!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] /page/xx scrapers?](https://wordpress.org/support/topic/page-xx-scrapers/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [1 week, 4 days ago](https://wordpress.org/support/topic/page-xx-scrapers/#post-19012984)
 * **Hello [@ambientblog](https://wordpress.org/support/users/ambientblog/),**
 * Dealing with aggressive scrapers and crawlers hitting pagination URLs (like `/
   page/xx/`) is a very common battle! Fortunately, Advanced IP Blocker has several
   built-in layers specifically designed to stop this kind of automated traffic 
   without hurting your real users.
 * Here is the recommended configuration to clean up your traffic:
 * **1. Enable the Community Defense Network** Go to **Settings > AIB Community 
   Defense Network** and turn on all the switches. Scrapers often use the same IP
   ranges across multiple sites; this feature will automatically block IPs that 
   have already been flagged as malicious by our community.
 * **2. Enable User-Agent Protection** Go to **Settings > User-Agent Protection**
   and make sure you activate:
    - Verify Known Bots
    - Verify AI Bots (CIDR)
    - Verify Monitoring Bots (IP List) This ensures that bots claiming to be legitimate
      search engines are actually real. It will drop fake bots and aggressive unverified
      crawlers immediately.
 * **3. Set up a JavaScript Challenge (The ultimate scraper killer)** If these scrapers
   are triggering your security rules, go to the **Attack Signature Engine** and
   configure the mitigation action to **JS automatic challenge / transparent** (
   or use Turnstile / hCaptcha if you have them configured). _Why this works:_ Most
   automated scrapers and dumb crawler scripts cannot execute JavaScript. They will
   fail the challenge and be blocked, while your real human visitors will pass the
   transparent challenge seamlessly without even noticing.
 * **4. Block Specific Scrapers Manually** If you’ve checked your analytics and 
   identified a specific unwanted scraper (for example, `Sogou web spider/4.0...`),
   you can block it directly. Go to **Blocking Rules > User Agents** and simply 
   add a keyword like `Sogou` to your blocked list.
 * **A quick reminder about your stats:** Please keep in mind that seeing some crawler
   traffic on your `/page/xx/` URLs in your stats is completely normal. Legitimate
   search engines (like Googlebot or Bingbot) _need_ to crawl your pagination to
   index your older posts properly. As long as you have “Verify Known Bots” enabled(
   Step 2), the good bots will do their job safely, and the malicious scrapers will
   be kept out.
 * Hope this helps you clean up your traffic! Let us know if you need any help setting
   this up.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Default blocked-UA list matches the Android platform blocking real users](https://wordpress.org/support/topic/default-blocked-ua-list-matches-the-android-platform-blocking-real-users/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 1 day ago](https://wordpress.org/support/topic/default-blocked-ua-list-matches-the-android-platform-blocking-real-users/#post-19010604)
 * **Hi Greg,**
 * Great news! We have just deployed version **8.13.4**, which addresses all the
   points we’ve been discussing in this thread. It usually takes around 6 hours 
   to propagate and appear as an available update in your WordPress dashboard, but
   if you want to test it right now, you can download the ZIP directly here: [https://downloads.wordpress.org/plugin/advanced-ip-blocker.8.13.4.zip](https://downloads.wordpress.org/plugin/advanced-ip-blocker.8.13.4.zip)
 * Here is a breakdown of what has been implemented based on your feedback:
 * **1. UI / Core List Synchronization (Fixed)** You were absolutely right about
   the discrepancy you spotted. The hardcoded list in the admin UI has been replaced
   and now dynamically syncs directly with the core engine. This guarantees that
   what you see is exactly what the firewall is actively blocking.
 * **2. New Feature: User-Agent URI Exclusions** We have added a new “User-Agent
   URI Exclusions” text box in the plugin’s Settings. You can now specify particular
   URIs that will completely bypass the User-Agent blocking engine. _**⚠️ Important
   Warning:**_ _Please use this feature with extreme caution. Any URI added to this
   box will bypass UA protections globally, meaning ALL configured blocked User-
   Agents will be allowed to hit that specific URI._
 * **3. Advanced Rules (The Recommended Approach for Complex Logic)** While the 
   new URI Exclusion box is convenient, for advanced requests we still highly recommend
   using the **Advanced Rules** engine. Because Advanced Rules run at an extremely
   early execution hook (`init` priority `-998`), they take absolute precedence 
   over the standard User-Agent engine. Using Advanced Rules allows you to write
   precise Regex conditions (e.g., allowing a _specific_ User-Agent ONLY on a _specific_
   URI) rather than exposing the URI globally to all blocked bots.
 * Thank you again for your meticulous debugging and for working closely with us
   to improve the plugin! Let us know how this new version works out for your setup.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Default blocked-UA list matches the Android platform blocking real users](https://wordpress.org/support/topic/default-blocked-ua-list-matches-the-android-platform-blocking-real-users/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 1 day ago](https://wordpress.org/support/topic/default-blocked-ua-list-matches-the-android-platform-blocking-real-users/#post-19010008)
 * **Hi Greg,**
 * First of all, thank you again for the incredibly detailed feedback and for taking
   the time to share your own traffic data regarding `Go-http-client`—that is exactly
   the kind of field intelligence that helps us improve the plugin for everyone!
 * Regarding your points, here is our breakdown:
 * **1. The Default UA Lists Divergence:** You were absolutely right. The hardcoded
   lists had diverged between `class-advaipbl-main.php` and `class-advaipbl-admin-
   pages.php`. Since version 8.13.3 was already pushed to the repository earlier
   today, this change isn’t in there just yet—but your catch was so good that we
   have immediately committed the fix for our upcoming **8.13.4** release. In 8.13.4,
   the UI page will dynamically call `ADVAIPBL_Main::get_instance()->get_default_user_agents()`,
   guaranteeing there is only one source of truth and the lists will never drift
   apart again.
 * **2. Targeting Go-http-client on specific paths:** Your reasoning is spot-on.
   Leaving it unblocked globally (to prevent breaking internal microservices) while
   blocking it on sensitive endpoints is the perfect approach. You can easily set
   this up right now using our **Advanced Rules** engine! Simply create a new rule
   with two conditions:
    - `User-Agent` -> `contains` -> `Go-http-client`
    - `URI` -> `contains` -> `/wp-json/wp/v2/users/` (You can also use regex to 
      include `/wp-login.php`). This keeps the protection exactly where it earns
      its place without the global false-positive risk.
 * **3. Whitelisted User-Agents and Spoofing:** Since we are on the topic of User
   Agents, please remember that the “Whitelisted User-Agents List” takes absolute
   precedence and allows all traffic if a match is found. Because UAs are trivially
   easy to spoof (attackers often impersonate Googlebot), we recommend using this
   whitelist very sparingly. Instead, to ensure official services aren’t blocked,
   we highly recommend keeping the verification options enabled under **Security-
   > Core Protections -> User-Agent Protection**:
    - Verify Known Bots
    - Verify AI Bots (CIDR)
    - Verify Monitoring Bots (IP List) These checks perform reverse DNS/IP lookups
      to cryptographically prove the bot is legitimate before allowing it through.
 * **4. New WAF Features in 8.13.3:** Since you are likely updating to 8.13.3 today,
   we want to gently remind you to check your **Security -> Core Protections -> 
   Web Application Firewall (WAF)** settings and ensure the newest engines are active:
    - Enable WAF
    - Intelligent Zero-Day Sync
    - Cloud Advanced Rules Sync These active syncs will automatically pull down 
      our latest JSON zero-day rules (like the recent critical Gravity Forms and
      Elementor Pro patches).
 * **5. Exclusion Box for UA Scoring:** This is a brilliant suggestion! We completely
   agree that a dedicated URI exclusion box for User-Agent scoring (similar to the
   404/403 exclusions) would be very useful for the exact platform endpoints you
   described. We have added this to our roadmap and will implement it alongside 
   the UA list fix in the upcoming **8.13.4** release.
 * Thank you once again for your fantastic collaboration!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Plugin initialization failed. The following required files are missing from the](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 2 days ago](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/#post-19009485)
 * Hi [@sawontheboss4](https://wordpress.org/support/users/sawontheboss4/),
   Have
   you managed to resolve the issue with the antivirus (CPGuard – from your hosting
   service) and get the `class-advaipbl-fim-engine.php` file out of quarantine?And
   have you tried reinstalling version 8.13.2 or 8.13.3 since then?We would appreciate
   your feedback so we can mark this case as resolved.If the problem persists, you
   should have received another email from your hosting provider with a new alert
   from the CPGuard antivirus…With the changes we mentioned earlier, the `class-
   advaipbl-fim-engine.php` file no longer contains the malware signatures (FIM);
   these are now managed via the cloud and the database to resolve this issue, so
   everything should work correctly.Since you are the only user who has reported
   this problem, we are keen to hear back from you so we can mark it as resolved.
 * Best regards,
   Advanced IP Blocker Support Team
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Default blocked-UA list matches the Android platform blocking real users](https://wordpress.org/support/topic/default-blocked-ua-list-matches-the-android-platform-blocking-real-users/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 2 days ago](https://wordpress.org/support/topic/default-blocked-ua-list-matches-the-android-platform-blocking-real-users/#post-19008840)
 * Hi Greg (@thewatchman3),
 * Thank you so much for this detailed and excellent bug report. You are absolutely
   right.
 * okhttp and Dalvik/ are legitimate Android platform signatures and should never
   have been active by default. While they can occasionally be spoofed by scrapers,
   the risk of blocking legitimate users (especially with automated background requests
   like App Links verification) is too high and goes against our core philosophy
   of avoiding false positives.
 * We have reviewed the entire default User-Agent list and made the following changes:
 * Commented out okhttp and Dalvik/ (they are now #okhttp and #Dalvik/ in the default
   list).
   We also took the opportunity to comment out Go-http-client and PostmanRuntime,
   as these are frequently used by legitimate microservices and developers.These
   changes are already committed and will be included in our upcoming 8.13.3 release.
 * As you correctly pointed out, if an administrator notices a specific malicious
   bot abusing okhttp against a specific endpoint (like a login page), they can 
   always create a targeted Advanced Rule just for that route rather than relying
   on a global UA block.
 * Thank you again for helping us make Advanced IP Blocker better!
    -  This reply was modified 2 weeks, 2 days ago by [IniLerm](https://wordpress.org/support/users/inilerm/).
    -  This reply was modified 2 weeks, 2 days ago by [IniLerm](https://wordpress.org/support/users/inilerm/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Plugin initialization failed. The following required files are missing from the](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 5 days ago](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/#post-19006394)
 * **Hi [@sawontheboss4](https://wordpress.org/support/users/sawontheboss4/)**,
 * Thank you for the screenshot and the follow-up. I know exactly what is happening
   here.
 * The error you are seeing (“file are missing from the initialization: class-advaipbl-
   fim-engine.php”) happens because your server’s antivirus (CPGuard) has quarantined
   that specific file from the previous version, and it has placed a **lock** on
   it.
 * Because of this lock, when you try to reinstall or update the plugin, WordPress
   is physically blocked by your hosting from writing the new class-advaipbl-fim-
   engine.php file to the disk. That is why the file is missing and the plugin fails
   to initialize.
 * As I mentioned before, in version 8.13.2 we have completely removed the signature
   dictionaries from the plugin files (they are now dynamically loaded into the 
   database). The new class-advaipbl-fim-engine.php is 100% clean and will not be
   flagged by CPGuard. However, you need to clear the previous quarantine lock first
   so WordPress is allowed to install the new file.
 * **How to fix this:**
    1. Log into your hosting control panel (e.g., cPanel).
    2.  Look for the Security section and open CPGuard (or your host’s Malware/Antivirus
       scanner).
    3. Go to the Quarantine section.
    4. Locate the class-advaipbl-fim-engine.php file and click Delete.
    5. Once the quarantine is cleared, go back to your WordPress Dashboard and reinstall
       version 8.13.2 manually (using the instructions from my previous message).
    6. If you do not have access to CPGuard or the Quarantine vault in your hosting
       panel, please reach out to your hosting provider’s support team. Tell them: “
       CPGuard has quarantined a file from a plugin, preventing me from updating to
       the new clean version. Could you please clear the quarantine for advanced-ip-
       blocker? and Please read this article [https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/#post-19006334](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/#post-19006334)“
 * Once the old lock is cleared, version 8.13.2 will install flawlessly and the 
   false positive will be gone forever.
 * Please let me know how it goes!
 * Best regards,
 * Inilerm
    -  This reply was modified 2 weeks, 5 days ago by [IniLerm](https://wordpress.org/support/users/inilerm/).
    -  This reply was modified 2 weeks, 5 days ago by [IniLerm](https://wordpress.org/support/users/inilerm/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Plugin initialization failed. The following required files are missing from the](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 5 days ago](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/#post-19006334)
 * **Hi [@sawontheboss4](https://wordpress.org/support/users/sawontheboss4/),**
 * First of all, I want to sincerely apologize for the inconvenience this issue 
   has caused you. We take this very seriously, and I really appreciate your patience
   and detailed feedback regarding the CPGuard block.
 * We have completely refactored the way the File Integrity Monitor stores and loads
   malware signatures. The dictionary is no longer hardcoded into the plugin files,
   but rather dynamically fetched and securely stored in your database. This architectural
   change ensures that aggressive server antiviruses like CPGuard will no longer
   falsely flag our plugin as a threat during installation or scanning.
 * We have just released **Version 8.13.2** with this hotfix. Although it might 
   take up to 6 hours to appear in your WordPress update dashboard, the direct package
   is already available on the official servers.
 * If you have a moment, it would be incredibly helpful if you could test it manually
   to confirm that CPGuard now allows the installation perfectly.
 * You can download the official package here: [https://downloads.wordpress.org/plugin/advanced-ip-blocker.8.13.2.zip](https://downloads.wordpress.org/plugin/advanced-ip-blocker.8.13.2.zip)
 * **How to install it manually:**
    1. Download the `.zip` file from the link above.
    2. Go to your WordPress Dashboard -> **Plugins** -> **Add New Plugin**.
    3. Click on the **Upload Plugin** button at the top.
    4. Choose the downloaded `.zip` file and click **Install Now**.
    5. WordPress will detect that the plugin is already installed and will ask you 
       if you want to replace it. Click on **“Replace current with uploaded”**.
    6. Once completed, make sure the plugin is activated.
 * Please let me know how the installation goes for you. If everything is green 
   on your end, we’ll consider this false positive issue permanently resolved.
 * Thank you again for helping us make the plugin better!
 * Best regards,
 * Inilerm
    -  This reply was modified 2 weeks, 5 days ago by [IniLerm](https://wordpress.org/support/users/inilerm/).
    -  This reply was modified 2 weeks, 5 days ago by [IniLerm](https://wordpress.org/support/users/inilerm/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Plugin initialization failed. The following required files are missing from the](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 6 days ago](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/#post-19005864)
 * Hello sawontheboss4,
 * **The Solution (Available Now):**
   We have just released a hotfix (version 8.13.1)
   that completely refactors how these signatures are stored (using ASCII arrays)
   so that server antiviruses will completely ignore them.
 * Since WordPress.org can take up to 6 hours to show the update in your dashboard,
   you can download the 8.13.1 patch directly right now from the official repository
   here:
   [https://downloads.wordpress.org/plugin/advanced-ip-blocker.8.13.1.zip](https://downloads.wordpress.org/plugin/advanced-ip-blocker.8.13.1.zip)
 * **How to update manually:**
    1. Download the .zip file from the link above.
    2. Go to your WordPress Dashboard -> Plugins -> Add New -> Upload Plugin.
    3. Upload the .zip file and click “Replace current with uploaded” (your settings
       will be perfectly preserved).
 * Could you please install this version and let us know if CPGuard stops flagging
   the file? Your feedback is incredibly valuable to ensure this is fixed for everyone!
 * Thank you so much for your patience and for reporting this so quickly.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Plugin initialization failed. The following required files are missing from the](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [2 weeks, 6 days ago](https://wordpress.org/support/topic/plugin-initialization-failed-the-following-required-files-are-missing-from-the/#post-19005823)
 * Hello sawontheboss4,
 * Thank you for providing the detailed CPGuard log! This is a known **False Positive**
   from your server’s antivirus software (CPGuard).
 * **What happened:**
 * In version 8.13.0, we introduced a highly advanced File Integrity and Malware
   Scanner. To detect hackers, the `class-advaipbl-fim-engine.php` file contains
   a dictionary of known malware signatures. CPGuard scanned our plugin, found this
   dictionary of bad words, and mistakenly thought our scanner was a virus.
 * **Immediate Solution:**
 * 1. Please whitelist the file `class-advaipbl-fim-engine.php` in CPGuard (or ask
   your hosting provider to do it for you).
 * 2. Restore the file from the CPGuard quarantine, or simply reinstall the Advanced
   IP Blocker plugin (your settings will not be lost).
 * We are already working on a patch (8.13.1) that uses a different encryption method
   for our malware dictionary so that server antiviruses will completely ignore 
   it.
 * Thank you for your patience and for reporting this!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] AIB Account Connection – Failed](https://wordpress.org/support/topic/aib-account-connection-failed/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [3 weeks ago](https://wordpress.org/support/topic/aib-account-connection-failed/#post-19005102)
 * Hi JWebber74,
 * Thank you so much for reporting this and for the great suggestion regarding the
   error message! We really appreciate it.
 * I’ve just tested the AIB Account Connection on a couple of different testing 
   sites, and the API key generated and connected successfully on my end. It sounds
   like what you experienced might have been a temporary JavaScript glitch in the
   browser or a hidden trailing space being caught by the validation. This is why
   a quick page refresh resolved the issue and correctly synchronized the state 
   to show as “Connected”.
 * Regarding the “Edit” button not responding, if you ever need to reset the connection
   in the future, the best approach is to:
 * 1. Click the Edit (pencil) icon.
 * 2. Completely delete the existing API key.
 * 3. Save the changes to clear the field.
 * 4. Generate and enter a brand new API key.
 * I have taken note of your suggestion to specify exactly which API is throwing
   the error in the prompt that is a fantastic idea and we will definitely look 
   into adding that clarity in an upcoming update.
 * I’m glad to hear it is showing as Connected now! Please let us know if you run
   into any other issues.
 * Best regards
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Is this a bug?](https://wordpress.org/support/topic/is-this-a-bug-15/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [3 weeks, 6 days ago](https://wordpress.org/support/topic/is-this-a-bug-15/#post-19000066)
 * **💡 Tip for users experiencing missing files after a failed auto-update:**
 * If your server times out or fails to extract all files during a WordPress plugin
   update, you might be left with an incomplete installation. Here are three ways
   to quickly fix this and restore your site:
 * **1. Reinstall via WordPress Admin (Easiest)** If you still have access to your
   WordPress dashboard, go to **Plugins -> Add New Plugin**, search for _Advanced
   IP Blocker_, and click **Install Now** again to force a fresh download.
 * **2. Reinstall via ZIP Upload** If the first method doesn’t work, you can manually
   overwrite the broken files:
    - Download the latest version of the plugin as a `.zip` file from the [official repository here](https://downloads.wordpress.org/plugin/advanced-ip-blocker.latest-stable.zip).
    - Go to your WordPress dashboard: **Plugins -> Add New Plugin -> Upload Plugin**.
    - Upload the `.zip` file. WordPress will detect the existing folder and ask 
      if you want to replace it. Click **Replace current with uploaded**.
 * **3. Upload the Missing File Manually (Advanced Users)** If your site is completely
   locked out (Fatal Error / White Screen of Death) and you can’t access `wp-admin`,
   you can use FTP/SFTP or your Hosting’s File Manager:
    - You can find the raw source code for any specific version (e.g., `8.12.2`)
      in the SVN repository: `https://plugins.svn.wordpress.org/advanced-ip-blocker/
      tags/8.12.2/includes/`
    - Download the specific file mentioned in your error log (for example, `class-
      advaipbl-ajax-handler.php`).
    - Upload it directly to the corresponding folder on your server: `/wp-content/
      plugins/advanced-ip-blocker/includes/`.
 * _(Note: Starting from our next release, we have completely redesigned our file
   loader. If a file is missing in the future due to a server glitch, the plugin
   will gracefully deactivate itself instead of causing a Fatal Error, keeping your
   site online)._
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Is this a bug?](https://wordpress.org/support/topic/is-this-a-bug-15/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [3 weeks, 6 days ago](https://wordpress.org/support/topic/is-this-a-bug-15/#post-19000051)
 * Hi [@nwjeff](https://wordpress.org/support/users/nwjeff/),
 * Thank you for reporting this issue and sharing the error logs!
 * You are completely right. Looking at the logs, it appears that during the automatic
   update process (Automatic updates starting…), your server timed out or failed
   to extract/copy all the files from the new version package, leaving your installation
   with missing files (in this case, class-advaipbl-ajax-handler.php).
 * To fix this immediately on your site, please completely delete the Advanced IP
   Blocker folder via FTP or your hosting File Manager and upload a fresh copy of
   version 8.12.2. All your settings and blocked IPs are safely stored in the database,
   so you won’t lose any data.
 * Good news: Based on your report, we have completely refactored the plugin’s file
   loader for the upcoming version. If a file goes missing during an update in the
   future, the plugin will now gracefully disable itself and show an admin notice
   rather than throwing a Fatal Error and taking the site down.
 * Let me know if a manual reinstallation gets you back up and running!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced IP Blocker] Is 404 error blocking not working?](https://wordpress.org/support/topic/is-404-error-blocking-not-working/)
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [4 weeks ago](https://wordpress.org/support/topic/is-404-error-blocking-not-working/#post-18998878)
 * Hi Oleg,
 * Thank you very much for taking the time to report this issue in detail and for
   your patience. We have thoroughly investigated the case and successfully identified
   and fixed the bug affecting the threshold blocking system (404/403/Login).
 * We will be releasing update 8.12.2 within the next 24 to 48 hours (possibly sooner),
   which includes this fix. With this update, the blocking system will work perfectly
   and be much more robust.
 * We greatly appreciate your help. Thanks to reports like yours, we can keep improving
   the plugin for everyone!
 * Best regards, The Advanced IP Blocker Team

Viewing 15 replies - 1 through 15 (of 266 total)

1 [2](https://wordpress.org/support/users/inilerm/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/inilerm/replies/page/3/?output_format=md)…
[16](https://wordpress.org/support/users/inilerm/replies/page/16/?output_format=md)
[17](https://wordpress.org/support/users/inilerm/replies/page/17/?output_format=md)
[18](https://wordpress.org/support/users/inilerm/replies/page/18/?output_format=md)
[→](https://wordpress.org/support/users/inilerm/replies/page/2/?output_format=md)