hello i am using uptimerobot and a few times a week i get 429 for 1-5 minutes but thats what i see on the logs. Root cause HTTP 429 - Too Many Requests Incident started at 2026-08-23 10:42:58 Resolved at 2026-08-23 10:48:05 Duration 5 minutes and 7 seconds Location Ashburn, USA - IP 5.161.75.7 im self hosted and discourse is with reverse proxy from hestiacp log.txt (55.8 KB) here is the log id like to know if this 429 was for all users or just few ? im on standard install on docker with only port 80 and 4 workers. 8 gb ram and 8 cores update: did a test on my pc while opening 20/30 posts until i got 429 and on my phone with different network it worked fine. this confirms 429 gets one client and not all visitors ?

If I’m not wrong, yes, it only affects the client sending the flurry of requests.

should i ignore this or i should change something to increase the limit ?

If you want to adjust the thresholds, see: [изображение] Available settings for global rate limits and throttling Self-Hosting Discourse ships with 3 different global rate limits that can be configured by site admins. Global per-ip rate limits These limits apply to every unique IP address that hits the Discourse application. (files that are served directly from the filesystem or the CDN are excluded) By default this rate limit is enabled, you may disable it or set it to a reporting mode. DISCOURSE_MAX_REQS_PER_IP_MODE : default block, this rate limit applies out of the box. (other options are warn, warn+block, and n…

[изображение] aLinux: with reverse proxy from hestiacp that probably means that all requests appear to be coming from the same IP and lots of users are getting 429 errors. Go to admin/users and look at what IP address you see for yourself and another user. If they are the same then you need to configure things so that the real IP gets to Discourse.

just checked and i have the same internal ip as the other users ! :frowning: how can i fix this ?

Are you running behind cloudflare? I am going through this game as well :slight_smile:

yes, but the problem is that all users have the same ip.. added this to app.yml and im testing right now run: replace: filename: /etc/nginx/conf.d/discourse.conf from: “server {” to: | server { set_real_ip_from 192.168.1.250; real_ip_header X-Forwarded-For; real_ip_recursive on; exec: echo “Beginning of custom commands” exec: echo “End of custom commands” tested right now from desktop and mobile phone i get correct ip adresses :smiley:

If you’re using Cloudflare then you want the Cloudflare template. It seems to be impossible to find the canonical topic about that, so maybe try https://ask.discourse.com/ – I was able to get an AI-generated message about what to do, but not where to find the discussion about it. It makes me sad that AI finds the solution but search won’t. :crying_cat:

well.. yeah asked chatgpt , made a backup before and then did a test. so far so good :smiley:

I would always use https://ask.discourse.com/ rather than a generic AI (unless you’re actively coding and the AI has access to the Discourse code).

429 too many requests — это хорошо или плохо? (помогите)

Поддержка продукта Самостоятельное хостинг

NateDhaliwal (Nate Dhaliwal) 24.Август.2026 23:13:52 12

Имеется в виду эта часть?

Тема		Ответов	Просм.
429 too many requests Self-hosting	4	2904	13.09.2019
Best free option to protect discourse from many requests Self-hosting	28	2709	18.12.2019
429 error when opening multiple topics Product Support	10	3317	28.11.2020
Troubleshooting a 429 (rate limit) Self-hosting	19	6333	10.10.2018
Discourse API Generating 429 Product Support	6	768	28.03.2023

429 too many requests — это хорошо или плохо? (помогите)

Связанные темы