Show real visitor IP addresses instead of CloudFlare IPs

When using CloudFlare CDN in front of your LiteSpeed Web Server, you may see a proxy IP instead of the real IP addresses of visitors.

To restore real visitor IPs simply set the Use Client IP in Header option to “Trusted IP Only” in the General Settings section of the Configuration page in your LiteSpeed Web Admin Console and add CloudFlare IPs/Subnets to the trusted list. If “Use Client IP in Header” is set to “Yes” instead of “Trusted IP only”, clients can spoof IPs with the “X-Forwarded-For” header sent to CloudFlare. As a result, this is not recommended.

The following snapshot shows the “Use Client IP in Header” setting:

The following snapshot shows how to add CloudFlare to trusted list. Please refer to this wiki for setup details.

the list of cloudflare IP subnet is available at https://www.cloudflare.com/ips/ Your litespeed configuration ACL allowed configuration should looks like

ALL, 103.21.244.0/22T, 103.22.200.0/22T, 103.31.4.0/22T, 104.16.0.0/12T, 108.162.192.0/18T, 131.0.72.0/22T, 141.101.64.0/18T, 162.158.0.0/15T, 172.64.0.0/13T, 173.245.48.0/20T, 188.114.96.0/20T, 190.93.240.0/20T, 197.234.240.0/22T, 198.41.128.0/17T, 199.27.128.0/21T

If there is another layer of proxy setup in front of LiteSpeed Web Server on the same server box, such as CloudFlare Railgun, Nginx, or Varnish, you also need to add that server IP to the trusted list.

Once enabled, your access logs will show the correct IP addresses and even PHP's $_SERVER['REMOTE_ADDR'] variable will contain your visitors' real IP addresses instead of a CloudFlare IP address. This will resolve most problems that might occur when enabling CloudFlare on PHP-enabled web sites (like WordPress or vBulletin installations).

Please be aware that only access log shows real visitor IPs, but error log still shows IPs of CloudFlare node. We may improve the logging a little to error_log to include real IPs for a future release.