Title: Same IP for All Users
Last modified: August 31, 2016

---

# Same IP for All Users

 *  Resolved [Freddy](https://wordpress.org/support/users/feddymaurano/)
 * (@feddymaurano)
 * [10 years ago](https://wordpress.org/support/topic/same-ip-for-all-users/)
 * Hi,
    According to your Documentation ([https://kb.sucuri.net/cloudproxy/Troubleshooting/same-user-ip](https://kb.sucuri.net/cloudproxy/Troubleshooting/same-user-ip))
   in order to solve this issue for Apache 2.4 we should use this config:
 *     ```
       RemoteIPHeader HTTP_X_SUCURI_CLIENTIP
       RemoteIPHeader HTTP_X_FORWARDED_FOR
       RemoteIPHeader HTTP_X_REAL_IP
       RemoteIPTrustedProxy 2a02:fe80::/29
       RemoteIPTrustedProxy 192.88.134.0/23
       RemoteIPTrustedProxy 185.93.228.0/22
       RemoteIPTrustedProxy 192.124.249.0/24
       ```
   
 * For NGinx this config:
 *     ```
       real_ip_header X-Forwarded-For;
       set_real_ip_from 192.88.134.0/23;
       set_real_ip_from 185.93.228.0/22;
       set_real_ip_from 66.248.200.0/22;
       set_real_ip_from 2a02:fe80::/29;
       ```
   
 * Could you please explain why there are different trusted ranges for each configuration?
 *     ```
       Apache: RemoteIPTrustedProxy 192.124.249.0/24
       NGinx : set_real_ip_from 66.248.200.0/22;
       ```
   
 * Are those just examples?
    Can we rely on those trusted ranges and white list 
   them on firewalls?
 * Thank you,
    Freddy
 * [https://wordpress.org/plugins/sucuri-scanner/](https://wordpress.org/plugins/sucuri-scanner/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [yorman](https://wordpress.org/support/users/yorman/)
 * (@yorman)
 * [10 years ago](https://wordpress.org/support/topic/same-ip-for-all-users/#post-7424288)
 * There are different ranges because CloudProxy is a distributed service. If your
   website is receiving traffic from different continents the firewall will redirect
   the requests to the nearest cluster. If you only whitelist the Asian cluster,
   for example, the requests coming from Europe will be blocked; you have to whitelist
   them all in order to allow access to all your public _(if that is what you want)_.
 * Regarding the information available in that page, yes it as safe as the IP addresses
   listed by CloudFlare in the same way [2]. One of my co-workers from the CloudProxy
   team is tasked to keep that page updated.
 * [1] [https://kb.sucuri.net/cloudproxy/Troubleshooting/same-user-ip](https://kb.sucuri.net/cloudproxy/Troubleshooting/same-user-ip)
   [
   2] [https://www.cloudflare.com/ips/](https://www.cloudflare.com/ips/)
 *  Thread Starter [Freddy](https://wordpress.org/support/users/feddymaurano/)
 * (@feddymaurano)
 * [10 years ago](https://wordpress.org/support/topic/same-ip-for-all-users/#post-7424299)
 * Hi Yorman,
    Thanks for your prompt response which totally makes sense but I am
   still confused here with my first question. To be more clear:
 * For Apache you recommend to whitelist:
 *     ```
       2a02:fe80::/29
       192.88.134.0/23
       185.93.228.0/22
       192.124.249.0/24
       ```
   
 * For Nginx you recommend to whitelist:
 *     ```
       192.88.134.0/23;
       185.93.228.0/22;
       66.248.200.0/22;
       2a02:fe80::/29;
       ```
   
 * My question is: Why there are different ranges for different web servers?
    As
   I can see the range **192.124.249.0/24** must be whitelisted ONLY for Apache 
   and the range **66.248.200.0/22** must be whitelisted ONLY for NGinx.
 *  [yorman](https://wordpress.org/support/users/yorman/)
 * (@yorman)
 * [10 years ago](https://wordpress.org/support/topic/same-ip-for-all-users/#post-7424368)
 * I passed this ticket to one of my co-workers and he told me that as you noticed
   there is a typo in the block associated to Apache. The correct IPs are the ones
   listed in the Nginx section, so for Apache it must be like this:
 *     ```
       RemoteIPHeader HTTP_X_SUCURI_CLIENTIP
       RemoteIPHeader HTTP_X_FORWARDED_FOR
       RemoteIPHeader HTTP_X_REAL_IP
   
       RemoteIPTrustedProxy 192.88.134.0/23;
       RemoteIPTrustedProxy 185.93.228.0/22;
       RemoteIPTrustedProxy 66.248.200.0/22;
       RemoteIPTrustedProxy 2a02:fe80::/29;
       ```
   
 * I will update the KB article as soon as possible.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Same IP for All Users’ is closed to new replies.

 * ![](https://ps.w.org/sucuri-scanner/assets/icon-256x256.png?rev=2875755)
 * [Sucuri Security - Auditing, Malware Scanner and Security Hardening](https://wordpress.org/plugins/sucuri-scanner/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/sucuri-scanner/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/sucuri-scanner/)
 * [Active Topics](https://wordpress.org/support/plugin/sucuri-scanner/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/sucuri-scanner/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/sucuri-scanner/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [yorman](https://wordpress.org/support/users/yorman/)
 * Last activity: [10 years ago](https://wordpress.org/support/topic/same-ip-for-all-users/#post-7424368)
 * Status: resolved