# Rate Limiting w/ Reverse Proxy

**URL:** <https://meta.discourse.org/t/rate-limiting-w-reverse-proxy/209354>\
**Category:** Self-hosting\
**Created:** [November 16, 2021, 8:26pm UTC](https://meta.discourse.org/t/rate-limiting-w-reverse-proxy/209354 "2021-11-16T20:26:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![forkythetoy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/forkythetoy/32/199298_2.png) [@forkythetoy](https://meta.discourse.org/u/forkythetoy)\
**Post date:** [November 16, 2021, 10:45pm UTC](https://meta.discourse.org/t/rate-limiting-w-reverse-proxy/209354/3 "2021-11-16T22:45:12Z")

</div>

Those stanzas are in the current nginx.conf instead our container under conf.d/discourse.conf.

For the app.yml portion did you mean

```plaintext
run:
  - replace:
      filename: /etc/nginx/conf.d/discourse.conf
      from: "types {"
      to: |
        set_real_ip_from 172.17.0.0/24;
        real_ip_header X-Forwarded-For;
        real_ip_recursive on;
        types {

```

We don’t have HAProxy on the outside of the containers, we have a DNS provider that does some pre-processing for us so the real\_ip\_header is in another header value, and we actually have a list of IP addresses that need to be replaced.

We actually also have see a list of X-Forwarded-For, I’m wondering if that’s the cause for the wrong IP’s to show up.

For example, I think we see 111.11.11.111 in the production logs, but not 55.555.55.55 which is what we want (as it’s set in x-real-ip)

```plaintext
HTTP_X_FORWARDED_FOR	111.11.11.111, 22.22.22.222, 333.33.33.333, 55.555.55.55
HTTP_X_REAL_IP	55.555.55.55

```

---

_[View the full topic](https://meta.discourse.org/t/rate-limiting-w-reverse-proxy/209354)._