# 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:** 5

<div class="post-metadata">

### Author: ![Roi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/roi/32/130587_2.png) [@Roi](https://meta.discourse.org/u/Roi)
#### Post date: [April 30, 2024, 2:34pm UTC](https://meta.discourse.org/t/problem-error-429-with-reverse-proxy/171858/5 "2024-04-30T14:34:50Z")

</div>

Ehm… :see_no_evil: I forgot the [Nginx (Discourse)](https://meta.discourse.org/t/set-up-discourse-on-a-server-with-existing-apache-sites/30013#configure-nginx-discourse-7) part. :see_no_evil: Thank you! :slight_smile:

I just edited app.yml and ran a rebuild on the container. The bot came back almost instantly after the container came back up. I do not see any 429 errors, yet. Hopefully it stays that way for “normal” users.

> [@pfaffman](#):
>
> or do all users appear to be coming from the proxy?

That’s the thing… When I check the admin page of the users, I always saw different “last IP” entries. So somehow Discourse saw the real IPs of the users, even without mod\_remoteip and also without the Nginx config change. :man_shrugging:

Anyway, I am curious to see if the Nginx config change brought the solution to this problem! :slight_smile:

---

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