Cloudflare does not acknowledge WAF rules

What is the name of the domain?

biwillzcomputers.com, techyfi.cloud

What is the error number?

403

What is the error message?

Encountering a Cloudflare challenge page (403 Forbidden)

What is the issue you’re encountering

I have configured WAF custom rules to bypass specific bots, Cloudflare does not ack

What steps have you taken to resolve the issue?

I have used my server IP address, defined specific bot

curl -A “facebookexternalhit/1.1” https://techyfi.cloud/fb-data-deletion/ -v

  • Trying 2606:4700:3030::6815:2001:443…
  • Connected to techyfi.cloud (2606:4700:3030::6815:2001) port 443 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: /etc/ssl/certs
  • TLSv1.0 (OUT), TLS header, Certificate Status (22):
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.2 (IN), TLS header, Finished (20):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.2 (OUT), TLS header, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
  • ALPN, server accepted to use h2
  • Server certificate:
  • subject: CN=techyfi.cloud
  • start date: Feb 24 14:10:57 2025 GMT
  • expire date: May 25 15:00:56 2025 GMT
  • subjectAltName: host “techyfi.cloud” matched cert’s “techyfi.cloud”
  • issuer: C=US; O=Google Trust Services; CN=WE1
  • SSL certificate verify ok.
  • Using HTTP2, server supports multiplexing
  • Connection state changed (HTTP/2 confirmed)
  • Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • Using Stream ID: 1 (easy handle 0x55809fd20b80)
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):

GET /fb-data-deletion/ HTTP/2
Host: techyfi.cloud
user-agent: facebookexternalhit/1.1
accept: /

  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • old SSL session ID is stale, removing
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
    < HTTP/2 403
    < date: Sun, 09 Mar 2025 21:37:43 GMT
    < content-type: text/html; charset=UTF-8
    < accept-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
    < cf-mitigated: challenge
    < critical-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

curl -A “facebookexternalhit/1.1” https://techyfi.cloud/fb-data-deletion/ -v

Check the reason the request is blocked in your security event log here…
https://dash.cloudflare.com/?to=/:account/:zone/security/events

If you are on a free plan and using Bot Fight Mode, that cannot be bypassed with WAF custom rules. You will either need to disable BFM, use IP access rules, or use Super Bot Fight Mode on a paid plan which can be skipped by WAF custom rules.

2 Likes

Thank you sir.

​currently my facebook crawler agent is working but whatsapp in not working, can you please assit with the specific IPV6 that allows this.

You’ll need to show a screenshot of the detail of a request that was blocked from the security event log to see why the request was blocked.

Please find the attached

(attachments)

Fixed Boss.

​thanks

1 Like