The visitor ip address the server is getting is not the real one

What is the name of the domain?

What is the error number?

wrong ip address

What is the issue you’re encountering

We are trying to get the real IP address from the visitor, but we are getting Cloudflare IP

What steps have you taken to resolve the issue?

We are using Wordpress and gravity form. When the customer fill out a form, we collect the IP address.
However, the ip address server is getting is not the real one.

IF we turn off the “proxied” than we can see the real IP address, however, we are not able to track visits or statistics .
If we turn proxied on, then we have statistic of the visits, but no real IP address.
We have had Plesk support setting up and changing everything they could do to get but they said now it is on CF settings.

You need to restore original visitor IPs, see here…

1 Like

We have done that, domain only, the in the whole server.
Still not working. Even PLESK development team after 10 days working on it could not make it work.

This was plesk support answer:

hank you for your patience.

I’ve just heard back from our development team, and they’ve done a thorough check on everything within our control. We’ve fixed everything that was possible on our end. After our investigation, it appears that the issue with the Cloudflare IPs seems to be related to “bogon” IPs, which are internal IPs used by the proxy and aren’t connected to our server or Plesk in any way.

Since we aren’t in charge of Cloudflare’s proxy settings, we’d recommend reaching out to Cloudflare directly to clarify why these internal IPs are showing up. It’s something within their environment rather than the server. From what I can see, the address is displayed normally when I’m accessing the website directly.

Can you give an example?

Which method from the link shared above did you use to restore the original visitor IP address?

1 Like

I am not sure exactly which one they used. We have Almalinux and they had done changes on Apache and NGINX.

These I can see:

They have added to Additional directives for HTTP and HTTPS
RemoteIPHeader CF-connecting-IP
RemoteIPHeader X-Forwarded-For

Additional nginx directives
real_ip_header CF-Connecting-IP;

But I have asked them what else they have done. Once I get it, I will share here.

Thank you


Plesk also did this into the server.

Bogon IPs would be related to the Pseudo IPv4 setting

So your visitors are accessing the site over IPv6 but are getting fake IPv4 addresses with this feature enabled to improve compatibility with old systems that don’t support IPv6.

1 Like

This is what plesk said about Pseudo IPv4

Hello Sandro,

Thank you for the update and for your patience.

Yes, what they meant is how Cloudflare is handling website traffic when visitors are using the newer IPv6. The Pseudo IPv4 is a Cloudflare feature that creates a “fake” IPv4 address (something like 254.144.4.44) for visitors that are using IPv6 (something like 2400:cb00:f00d:dead:beef:1111:2222:3333). This is a feature that they have that helps maintain compatibility for systems or websites that do not fully support IPv6 addresses yet. It makes so that even if a visitor is on IPv6, the communication still works smoothly with older systems by giving them a translated IPv4 address.

In simpler terms, Cloudflare support is saying that your visitors are using the new IPv6 and are giving them temporary (pseudo)/bogon IPv4 addresses.

So, my question is: How can I get the real IP, no matter if it is IPv4 or IPv4. The reason we need that is to run on IP Qualityscore to check for possible fraud, so we need the real ip address.

Thank you

IPQS Fraud Prevention appears to have IPv6 support. Have you tried disabling Pseduo IPv4?

I have turned off and I will monitor tomorrow. Thank you

1 Like

Hello, thank you. By turning off the Pseudo IPv4 the real ip from visitor, even ipv6, is coming correctly. The solution worked. Thank you

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.