This seems to work just fine on, for example, our Amsterdam servers. We get the real client IP’s there. However on the Frankfurt servers we do not get the real IP.
So our servers run the exact same setup on server level. The only difference could be to how they are set up within the management portals of the data centers. What settings should we look for?
What feature, service or problem is this related to?
I mainly see 145.102.247.21 whenever someone visits from the Frankfurt data center. On our Amsterdam servers, for example, we see the correct real IP’s.
That’s correct. However, I do want to point out that we still do not run with proxy enabled (you gave me some good guidance in another post about this). Also this IP is not known to us either. It seems to be owned by some Dutch company.
Do you have any guesses as to why it shows this IP?
In that case, the above configuration does nothing. You don’t need to replace Cloudflare’s IPs if requests aren’t coming from Cloudflare’s IPs in the first place.
I would guess that someone is making requests to your server from that IP.
Thanks for your clarification. We’ll be enabling the proxy next week once we migrate al the hostnames.
This IP is logged each time a user comes into our system through the Frankfurt datacenter. It shows this IP for me as well when I come from the Frankfurt datacenter. So I think we need to find out where this IP is coming from.