Support

If connecting fails with a blocked_by_… code, the request never reached the Sentro connector plugin: the host's security layer answered instead. These steps resolve it.

• Exclude the path /wp-json/crhub/v1/ from bot protection, caching and rate limiting. This is the safest fix and keeps the rest of the site protected.
• SiteGround: the Anti-Bot AI runs at server level and cannot be switched off per path from Site Tools. Ask SiteGround support to allow 185.166.188.64 for the site, or to exclude /wp-json/; see the SiteGround guide.
• Cloudflare: add an IP Access Rule allowing 185.166.188.64, or a WAF skip rule for URI Path starts with /wp-json/crhub/v1/ covering Bot Fight Mode, managed challenges and rate limiting.
• Wordfence: add 185.166.188.64 under Firewall, All Options, Allowlisted IP addresses. As the site administrator you can do this yourself in a couple of minutes. Allowlisting the REST path works too.
• Sucuri: in the firewall dashboard, add 185.166.188.64 under Access Control, Allowlist. Allowing the REST path works too.
• HTTP basic auth or maintenance mode: allow /wp-json/crhub/v1/ without a login, otherwise the API stays unreachable.
• If your firewall supports a bypass header, set it per site under the site's settings, Extra request header. We send it with every call and never log the value.

All our requests come from one fixed outbound IPv4 address: 185.166.188.64. Allowing that address in your firewall or security plugin is the simplest fix. Our requests also use the path /wp-json/crhub/v1/ and the user agent RootsWP/2.4.1 (+https://rootswp.com). Our outbound IP address