Cloudflare integration

Edition: Premium.

Selecting the card enables Cloudflare integration. When a request comes through a recognised Cloudflare edge, WPf2b can use the visitor address from X-Forwarded-For. Without that recognition, a request may be attributed to the edge or, when another non-empty trust list is active, rejected as an unknown proxy. A later fail2ban ban on an attributed edge can make traffic fail intermittently across Cloudflare’s address pool. Trusting the forwarded address depends on the immediate peer being a recognised Cloudflare address; see Trusted proxies and Remote address resolution.

Bundle settings

Setting

Value applied

WP_FAIL2BAN_EX_PROXY_CLOUDFLARE

true

The individual control is on the Remote IPs tab in Advanced settings.

Note

How QuickStart settings take effect

Constants always take priority, and a conflicting constant prevents a card’s bundle from applying; Site Health can report the conflict.

In Premium, a later Advanced edit takes effect even while the card remains selected. Changing a card’s state makes that change the latest UI action, and explicitly saving QuickStart reapplies selected cards. Deselecting a card restores only values that card changed and owns.

In Free, Advanced settings is read-only. Deselecting a card stops it supplying its values, after which constants or defaults determine the effective settings.

See QuickStart for the full explanation of priority, compatible values, card ownership, and restoration.

This card configures: