Thanks for the kind words and for reporting this, @qerghgfjkgk !
You’re right — when a site is behind Cloudflare, the geolocation can resolve to the Cloudflare data center’s country instead of the visitor’s real country. We’ve identified the root cause and already scoped the fix (#150).
This is planned for the next release (v5.4.2), which will properly detect the real visitor IP via Cloudflare headers and use it for country detection. Stay tuned!
Wow! Thanks a lot for such quick fix!
Hi @qerghgfjkgk ,
Thanks for the kind words about the plugin!
This was a known issue — Slimstat was using the Cloudflare proxy IP for geolocation instead of the real visitor IP, which is why you were seeing the same country flag for everyone. We’ve fixed this in version 5.4.2, which is available now.
Please update to v5.4.2 through your WordPress dashboard and Slimstat will correctly use the originating visitor IP for both the country flag and all location data going forward.
Let us know if it works as expected!
Hi there,
Even with v5.4.4 the problem is still not fixed and actually got worse.
Before I could see original IP behind proxy, now it shows only proxy IP.
Any help??? @parhumm