Title: No support for reverse-proxy?
Last modified: August 22, 2016

---

# No support for reverse-proxy?

 *  Resolved [ramon fincken](https://wordpress.org/support/users/ramon-fincken/)
 * (@ramon-fincken)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/no-support-for-reverse-proxy/)
 * I am using a reverse proxy server, so all requests come from the reverse proxy.
 * The problem is that all attacks seem to come from my proxy, instead of the real
   forwarded IP (which is present in PHP SERVER var).
 * Any chance of taking this into account?
 * [https://wordpress.org/plugins/sucuri-scanner/](https://wordpress.org/plugins/sucuri-scanner/)

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

 *  [yorman](https://wordpress.org/support/users/yorman/)
 * (@yorman)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/no-support-for-reverse-proxy/#post-5681014)
 * I added an option in the _“General Settings”_ panel located in the plugin’ settings
   page to enable support for reverse proxies. Note that the option is disabled 
   by default to avoid conflicts with CloudProxy [1] which is our in-house firewall.
 * Also, for people that do not know how a reverse proxy works, it reports the IP
   address of the server as the _“REMOTE\_ADDR”_ and creates a new HTTP header that
   generally _(but not always)_ is named _“X-Forwarded”_, every header that has 
   HTTP as its prefix can modified before the request is sent, so a malicious person
   may use this to hide his original IP address and execute attacks with less fingerprints.
 * This is why I did not added support for reverse proxies before, but OP wants 
   to have that so here you go [2].
 * [1] [http://cloudproxy.sucuri.net/](http://cloudproxy.sucuri.net/)
    [2] [https://plugins.trac.wordpress.org/changeset/1077710](https://plugins.trac.wordpress.org/changeset/1077710)
 *  [daleunknowninkdesign](https://wordpress.org/support/users/daleunknowninkdesign/)
 * (@daleunknowninkdesign)
 * [11 years ago](https://wordpress.org/support/topic/no-support-for-reverse-proxy/#post-5681068)
 * Curious…so how does it take into account an Nginx server?

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

The topic ‘No support for reverse-proxy?’ 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/)

## Tags

 * [forwarded`](https://wordpress.org/support/topic-tag/forwarded/)
 * [proxy](https://wordpress.org/support/topic-tag/proxy/)
 * [real](https://wordpress.org/support/topic-tag/real/)
 * [reverse](https://wordpress.org/support/topic-tag/reverse/)

 * 2 replies
 * 3 participants
 * Last reply from: [daleunknowninkdesign](https://wordpress.org/support/users/daleunknowninkdesign/)
 * Last activity: [11 years ago](https://wordpress.org/support/topic/no-support-for-reverse-proxy/#post-5681068)
 * Status: resolved