I have no rate limits set in the nginx I use as a reverse proxy, and I will try what you suggest to see what the container is doing.
I am loading Leaderboard, Top Producers and Events in Right Sidebar Blocks.
I will report back, thx
I bet you are correct, so what are good but more lax values for these settings in /var/discourse/templates/web.ratelimited.template.yml? Is it simply trial and error?
params:
reqs_per_second: 12
burst_per_second: 12
reqs_per_minute: 200
burst_per_minute: 100
conn_per_ip: 20
run:
- replace:
filename: “/etc/nginx/conf.d/discourse.conf”
from: /server.+{/
to: |
limit_req_zone $binary_remote_addr zone=flood:10m rate=$reqs_per_secondr/s;
limit_req_zone $binary_remote_addr zone=bot:10m rate=$reqs_per_minuter/m;
limit_req_status 429;
limit_conn_zone $binary_remote_addr zone=connperip:10m;
limit_conn_status 429;
I bumped it to:
reqs_per_second: 18
burst_per_second: 18
reqs_per_minute: 400
burst_per_minute: 200
conn_per_ip: 20
Still get the “429 Too Many Requests”
I removed Leaderboard, still get the issue.
I remove Right Sidebar Blocks, no more issue
Very annoying!
Not that I do not have this issue with the Top Contributers Sidebar.