Hello all, new user here. I was not sure where to file this request, and I searched the forums exhaustively and could not find the answer seemingly.
My issue seems very simple, however I cannot determine the exact setting that causes it.
We use a WP plugin called Geo IP Detection which allows shortcode placement, and hides or shows content based on settings. Example, we only want a certain phone number to show to users in certain states.
Using the free version of Cloudflare, there did not seem to be an issue. Upon upgrading to Cloudflare Plus, the Geo IP detection from the plugin seems to be broken or very inconsistent.
The plugin uses something called: Maxmind GeoIP Lite City, which I believe is a downloaded database or something of the sort.
I can pinpoint the functionality breaking exactly to the day Cloudflare Plus was enabled.
In the last two days, I also had site speed optimizations made to the website where an expert also tweaked a bunch of the Cloudflare settings, but this is coincidence and I believe the issue occurred as a result of Cloudflare Plus simply being enabled (most likely with a setting NOT available on Cloudflare Free).
Anyone have any ideas as to what might cause this Geo Ip Plugin to be unable to get an accurate reading? Typically what now happens is that states that should be seeing a certain number, are not seeing the correct number. Occasionally the number is correct but as of right now it’s too inconsistent.
There is no such thing. That must be some paid package that your host is selling.
It is just a guess, but maybe your host is not rewriting IP addresses, hence it is always the IP addresses of the Cloudflare proxies which show up and not the clients’ ones. If that is the case you will need to contact your host, so that he reconfigures the server.
Assuming you are on partner setup (which that plus package would suggest) your host should be the first contact in any case.
I am going to test the setting “BETA: Enable AJAX endpoint to get the information for the current IP even on cached pages.” Perhaps cached pages were being too aggressively served without getting the IP each time. This might solve it.