Recent content by zeeb0t

Woke up and my servers had updated themselves by policy already, and cycled all php processes to ensure the new version was running only. Automation is great.

Thank you for this bug report. I have prepared a fix into the next release.

I understand the concern, but this is a deliberate conservative default rather than an oversight. Bot Guard does include friendly defaults for widely expected search crawlers/fetchers where there is a strong verification path and broad site-owner expectation. Wayback/Internet Archive is a...

Thank you, that helps. The support bundle shows Bot Guard is healthy overall, and it also shows the ASN path is now populated: ASN range cache: 1 configured ASN(s) / 2 active ranges So the most likely explanation is timing. Adding 7941 is the right kind of network-level exception for Internet...

Thanks, that all makes sense. There are two separate things here: archive.org in Additional trusted crawler reverse DNS domains is not enough for this request. That option is not a plain rDNS allowlist. Bot Guard only uses it when the request also has a plausible crawler/fetcher user-agent...

Thanks, will look into this. Yes, it can help with that, but I would separate two cases. XF Bot Guard is appropriate when the problem is abusive or suspicious visitors repeatedly hitting expensive public routes, including XenForo search. If Protected areas is set to All public pages, then...

Thanks, that confirms setup has completed on the XF Bot Guard side. If Health now says: and the Overview page shows long IDs for both: Cloudflare Edge Enforcement IP list ID Managed Challenge rule ID then XF Bot Guard has created/found the Cloudflare resources through the API. You’re...

Thanks, that is actually progress. The two warnings you quoted are expected while Cloudflare Edge Enforcement dry run is still enabled: That means Observe-only is no longer forcing Cloudflare writes off. Dry run is a separate Cloudflare Edge safety setting, and it is normal to leave it...

Thanks for sending me the support bundle by DM. Replying here, as it may be helpful for others. Your install currently has Observe-only overlay enabled. While Observe-only is active, XF Bot Guard keeps sensing/logging/reporting, but it suppresses visitor-altering responses and live Cloudflare...

Thanks for the report, and sorry for the unclear wording there. In that section, managed setup means the Set up Cloudflare automatically button under ACP > XF Bot Guard > Cloudflare Edge Enforcement > Setup. It is not the top-right Setup button on the Overview page; that button just opens the...

It does sound like a FB browser/cloudflare turnstile type of issue..

Missing context: I am a firefighter. Hence the fire season relevance.

Each of the new features coming have been tested and are fine. However, it is start of fire season here in Australia, so I am just working up my schedule before releasing the new version. I just want to make sure I have the available time to support everyone who needs it quickly.

The next version includes a new type of quick setting: A new Capacity Fit Profile at the top of the existing XF Bot Guard Quick settings page. Starts from Balanced production, measures the current install using lightweight in-product capacity/readiness signals, assign known feature costs, and...

Thanks for the detailed report, that is useful. One important clarification first: the country pressure map/table is not a raw “all scraper countries seen in access.log” view. It is based on Bot Guard intervention pressure, mainly sessions that reached challenge/deny handling or...