# 排查 429（速率限制）问题

**URL:** https://meta.discourse.org/t/troubleshooting-a-429-rate-limit/81060
**Category:** Self-hosting
**Created:** [2018年二月20日 18:20 UTC](https://meta.discourse.org/t/troubleshooting-a-429-rate-limit/81060 "2018-02-20T18:20:41Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![AstonJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/astonj/32/215041_2.png) [@AstonJ](https://meta.discourse.org/u/AstonJ)
#### Post date: [2018年十月9日 22:54 UTC](https://meta.discourse.org/t/troubleshooting-a-429-rate-limit/81060/16 "2018-10-09T22:54:29Z")

</div>

There’s HAProxy on the front, set up as per this guide:

> [@Set up Discourse on a server with existing Apache sites](https://meta.discourse.org/t/how-to-set-up-discourse-on-a-server-with-existing-apache-sites/30013):
>
> It’s not as daunting as it sounds! While this may sound a bit intimidating at first, it’s really not all that bad. You basically need to do two things: Install HAProxy (or an alternative) which will take over port 80 and then divert your Discourse traffic to your docker container, and all your other sites to your usual Apache set-up. Let Apache know which port to listen for. While this is only a rough guide, it should do a good job of pointing you in the right direction. Let’s get star…

When looking in the admin control panel, all user’s IPs are showing correctly (which I believe is because `option forwardfor` is set in HAProxy).

Other than that there is no cloudfare - however the datcentre does offer DDOS protection as standard (but don’t think that would make any difference) : /

---

_[View the full topic](https://meta.discourse.org/t/troubleshooting-a-429-rate-limit/81060)._