# Problem Error 429 with Reverse proxy

**URL:** <https://meta.discourse.org/t/problem-error-429-with-reverse-proxy/171858>\
**Category:** Self-hosting\
**Created:** [December 1, 2020, 10:30am UTC](https://meta.discourse.org/t/problem-error-429-with-reverse-proxy/171858 "2020-12-01T10:30:02Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![barto\_95](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barto_95/32/199996_2.png) [@barto\_95](https://meta.discourse.org/u/barto_95)\
**Post date:** [December 1, 2020, 10:30am UTC](https://meta.discourse.org/t/problem-error-429-with-reverse-proxy/171858/1 "2020-12-01T10:30:02Z")

</div>

Hi, My Discourse is run with reverse proxy (NPM)

the discourse don’t it does not support the x-forwarded field and therefore shows me all the time the ip address of my reverse proxy when we look for example from which ip the user is registering etc …

I sniff the request on discourse and the X-forwarder is present but in access.log the IP view is the reverse proxy

I view on interne il necessary to change the configuration template or de configuration file nginx for Discourse (not nginx on NPM)

do you help me for this ? because the discourse activate de tempalte web.ratelimite and send most error 429

☹  
Thank you for you help

---

_[View the full topic](https://meta.discourse.org/t/problem-error-429-with-reverse-proxy/171858)._