Hello @martje65,
Thank you for reporting this. We have identified the issue; it is a minor PHP Warning caused by a variable ($block_reason_code) being accessed before initialization in the logging function.
It does not affect the security or functionality of the plugin, but we understand it can clutter your logs.
We have already patched this in our development branch, and the fix will be included in the upcoming version 8.6.10, which we plan to release very soon (today).
In the meantime, you can safely ignore this warning.
Best regards, The Advanced IP Blocker Team
Thanks for the update @inilerm
Version 8.6.10 is now available and fixed.
Thank you.
Regarding your comment in the support post https://wordpress.org/support/topic/how-to-detect-and-report-ip-addresses/
Hi @martje65,
Thank you for sharing that ASN!
A word of caution regarding Cloud ASNs (Google Cloud, AWS, etc.):
You are correct that AS396982 belongs to Google Cloud and is used by services like Mollie. However, please be careful when whitelisting it globally.
Since Google Cloud is a public hosting provider, anyone can rent a server there, including bad actors running bots or scrapers. If you whitelist the entire ASN AS396982, you are allowing Mollie, but also potentially allowing malicious traffic hosted on Google’s infrastructure to bypass your firewall rules.
Better approach for Payment Providers:
For sensitive services hosted on public clouds (like Mollie on GCP), it is safer to whitelist their specific IP ranges (if they provide them) in the “Whitelist” tab, rather than whitelisting the entire ASN.
If Mollie does not provide specific IPs and you must whitelist the ASN, just be aware that you are slightly lowering your shields against other traffic coming from Google Cloud.
Best regards,
The Advanced IP Blocker Team
