Cloudflare IP Header

Dear @kuldipzorem

I had set in Cloudflare – Rules -> Page Rules – rule to:
Domain: https://mydomain.com/
Cache level: cache everithing
Edge cache TTL: 2 hours
I removed that rule.

And in Caching – Configuration – Cache Level I have set to Standard

Did I forget something? Thats ok?
Thank you

Hi @kuldipzorem

Thanks for your response earlier. I wanted to give you a full update on what we’ve tried so far, hoping this gives better insight.

✅ Context:
I use your plugin to hide certain products for visitors from specific countries (e.g. UAE). It worked fine until I activated Cloudflare (free plan) to mitigate bot attacks. After activating Cloudflare, users from restricted countries started seeing the hidden products again. 🔍 What we’ve done so far:

• Cloudflare proxy is active (orange cloud).
• Cloudflare correctly sends CF-Connecting-IP and CF-IPCountry headers.
• My server (Websupport) uses Apache with mod_remoteip enabled, so REMOTE_ADDR is correctly populated with the visitor’s real IP.
• Verified that:
  • $_SERVER['REMOTE_ADDR'] = real client IP (e.g. UAE test IP).
  • WC_Geolocation::geolocate_ip() returns correct country (e.g. AE).
• Added this to functions.php:

add_filter('woocommerce_geolocation_ip', function($ip) { return $_SERVER['HTTP_CF_CONNECTING_IP'] ?? $ip; }); add_filter('option_wpcbr_force_geo_location', '__return_true'); 🧪 What works and what doesn’t:

• ✅ When Cloudflare is paused, everything works fine — user in UAE sees no restricted products.
• ❌ When Cloudflare is active, and the correct IP is passed, the user sees the restricted products again.

🧼 Cache cleared:

• Cloudflare cache was purged completely.
• Development Mode enabled.
• Browsers tested in incognito with no cookies.
• Page rules and Cache Rules were temporarily removed.

🤔 My assumption:

It seems your plugin is possibly caching the country in a cookie or not re-evaluating the IP if one was cached previously — or it may not respect the woocommerce_geolocation_ip filter when using Cloudflare. 👉 Question:

Can you confirm:

1. Does your plugin rely on WC_Geolocation::geolocate_ip() directly?
2. Does it cache the result (e.g. from cookie)?
3. Can we force it to always re-check based on real IP or override with a hook?

Thank you for your time — we’ve come very far in debugging this and appreciate any input you might have to make it work reliably with Cloudflare.

Best regards,

• This reply was modified 1 year, 1 month ago by fill64.