# 保护 Discourse 免受大量请求的最佳免费方案

**URL:** <https://meta.discourse.org/t/best-free-option-to-protect-discourse-from-many-requests/113350>\
**Category:** Self-hosting\
**Created:** [2019 年4 月 3 日 14:35 UTC](https://meta.discourse.org/t/best-free-option-to-protect-discourse-from-many-requests/113350 "2019-04-03T14:35:11Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

作者： ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
发布日期： [2019 年4 月 3 日 18:28 UTC](https://meta.discourse.org/t/best-free-option-to-protect-discourse-from-many-requests/113350/12 "2019-04-03T18:28:31Z")

</div>

> [@Corsterix](#):
>
> I use cloudflare with multiple Discourse installs, it works perfectly fine.

You can use Cloudflare as DNS and a cache for /uploads, but if any of their caching or “optimisation” features are touching the page then you’re completely unsupported here.

There are a long list of Cloudflare tweaks which break discourse in new and interesting ways.

Either way Cloudflare is a tangent, as indicated above the error being discussed is very likely due to nginx not receiving origin IPs. Let’s deal with the root cause rather than slap a bandage on a symptom.

---

_[View the full topic](https://meta.discourse.org/t/best-free-option-to-protect-discourse-from-many-requests/113350)._