Allow Chat4U on your Cloudflare-protected website

If someone else manages your website

In Chat4U's website-access dialog, open Request details → Copy instructions for my administrator. Send that report and this guide to your developer, agency or host. Ask them to identify the Service and rule for the matching request, and tell you when the change is saved. Keep the source so you can test again. If you need content now, use a file or trusted text.

Find the blocked request

1. Open the site's security eventsUse the affected hostname and the attempt's timezone.

   Select the website in your Cloudflare dashboard. Open Security → Analytics → Events. Select a time range containing the failed attempt. Narrow the results using the affected host/path or Ray ID when shown. Open the matching event and read its Service, action and rule details. A Chat4U diagnostic reference is not automatically a Cloudflare Ray ID. Cloudflare's current events navigation.

2. Choose the matching branchUse the event's protection name, not the site's Cloudflare logo.

   Match the observed protection to the table below. If no event matches, check the hostname, time conversion and available logs; repeat one Chat4U access check to obtain a fresh attempt if needed. Ask the administrator to correlate hosting/origin logs before changing a rule. Missing sampled events do not establish that Cloudflare allowed the request.

Super Bot Fight Mode

Follow this branch only when the matching event identifies Super Bot Fight Mode.

1. Create a named exceptionSave it as a scoped custom rule for this site's intended content.

   Open Security rules → Create rule → Custom rules. Name it Chat4U website import. In When incoming requests match, use the conditions for your selected access method. The examples below use a fictional hostname and help-content path; replace them with the hostname/path you intend to import. Cloudflare's rule-creation procedure.

2. Select the matching identity methodA public crawler name and a private token are different.

   For public help/product pages, a named-crawler exception can match Chat4UBot/. Anyone can copy this identifier. If your administrator requires stronger verification and custom-token access is available, use the private-header example instead and configure the same secret in Chat4U. Include only necessary entry, content and sitemap paths; rendering assets receive no private token and must be publicly readable; a help-only rule cannot make an unrelated sitemap path readable.

3. Choose the action and deploySkip the responsible bot protection; keep other protections.

   Under Then take action, choose Skip. Select All Super Bot Fight Mode rules and leave unrelated skip options unselected. Keep Log matching requests enabled so you can diagnose the next check, then select Deploy. Confirm the rule is enabled. An earlier custom rule may still stop the request before this rule runs. Skip options and logging.

(http.host eq "www.example.com"
 and http.request.method in {"GET" "HEAD"}
 and starts_with(http.request.uri.path, "/help/")
 and starts_with(http.user_agent, "Chat4UBot/"))

(http.host eq "www.example.com"
 and http.request.method in {"GET" "HEAD"}
 and starts_with(http.request.uri.path, "/help/")
 and any(http.request.headers["x-chat4u-import-token"][*]
         eq "YOUR_PRIVATE_TOKEN"))

Bot Fight Mode

Ordinary Bot Fight Mode cannot be skipped by the custom WAF rule above. Stop here rather than create an SBFM rule for BFM. Cloudflare's BFM limitations.

Choose an available route with your administrator:

• Direct content: upload a file or paste text; this needs no Cloudflare exception.
• A protection with scoped exceptions: if you choose a provider product that supports them, confirm its actual availability/settings and follow its procedure. This is a website-provider choice, not a Chat4U upgrade requirement.
• Verified-IP exception: open your source's Website access settings → Access method → Allow verified importer IP addresses and select Copy IP addresses. Consider this only when Chat4U displays a verified current list. A matching IP Access Allow rule can prevent BFM from running, but also bypasses several other protections. Your administrator must evaluate that broader effect; never substitute temporary task IPs or an entire cloud-provider range. IP Access scope.

Open Chat4U

If verified addresses are unavailable, use one of the other routes. Turning off protection for the whole site is not the default recovery instruction.

Another rule or access wall

For a custom rule, open the identified rule and have the administrator narrow its match to exclude your approved Chat4U requests. For Managed rules, create an exception for the identified managed rule/ruleset and matching intended requests; use Cloudflare's exception procedure. An SBFM Skip does not solve those refusals.

For another protection or a website/account login, give the administrator the matching evidence. Only use a supported automation method; otherwise supply intended public content or authorized file/text. If Cloudflare allows the request but hosting still refuses it, investigate the origin's matching log entry. Do not keep broadening the Cloudflare exception without identifying the remaining refusal.

Verify the change in Chat4U

Return to the same source and select Test access and retry import. After Access check passed. Your import is queued or already running, wait for completed processing, then inspect Pages, remaining affected pages and representative assistant answers. A successful check samples content; it does not guarantee every page in a sitemap/crawl. The complete verification steps.

Remove access when you no longer need it

Remove the named exception you created, or revoke its dedicated token and remove it from the Chat4U source. If you used an IP Access rule, remove that specific rule. This stops future website access; it does not by itself delete previously imported knowledge. Manage content removal separately in Chat4U.

Last updated on