Hi @cousineddie,
Thanks for reaching out! That is unusual, as we test extensively with Site Kit, but valid requests can sometimes be flagged depending on strictness levels and server variables.
If disabling the plugin fixes the connection instantly, it confirms that one of our security modules (likely the WAF, Bot Protection, or REST API hardening) is blocking the background requests Site Kit makes to Google.
The Solution (Safe & Quick): Instead of disabling security checks globally, the best practice is to create a specific “Allow” rule for Site Kit traffic. This keeps your site secure while letting Google do its job.
Go to Security > Blocking Rules > Advanced Rules.
Click Add New Rule.
Configure it as follows:
Name: Allow Site Kit
Condition 1: Request URI CONTAINS google-site-kit
Condition 2: ASN EQUALS AS15169 (This is Google’s unique network identifier)
Action: Allow (Bypass Security)
Click Save Rule.
This tells the firewall: “If a request comes from Google’s network AND is specifically for Site Kit, let it pass.”
Diagnosis (Optional): If you want to know exactly what triggered the block:
Re-enable Advanced IP Blocker.
Trigger the Site Kit error again.
Go to Security > Logs & Sessions > Security Log.
Look for a “Blocked” entry at that exact time. The “Reason” column (e.g., WAF: SQL Injection, Fake Crawler, Protocol Violation) will reveal exactly why the plugin stopped the request.
Let us know if the Advanced Rule solves it for you!
Best regards,
Advanced IP Blocker Team
Done and working fine, thanks!
