Atualizamos o Discourse para a versão 2.2.5.
Isso se refere às limitações no número de postagens por usuário por dia.
Nossa configuração padrão é: DISCOURSE_MAX_REQS_PER_IP_PER_MINUTE: número de solicitações por IP por minuto (padrão é 200) DISCOURSE_MAX_REQS_PER_IP_PER_10_SECONDS: número de solicitações por IP a cada 10 segundos (padrão é 50)
Gostaríamos de aumentar para: DISCOURSE_MAX_REQS_PER_IP_PER_MINUTE: 1000 DISCOURSE_MAX_REQS_PER_IP_PER_10_SECONDS: 500
Você acha que isso terá impacto no servidor e no desempenho do Discourse?
Alguns usuários começaram a reclamar que atingiram o limite no número de postagens enviadas.
01:09:42 {"errors":["You’ve performed this action too many times. Please wait 19 seconds before trying again."],"error_type":"rate_limit","extras":{"wait_seconds":19}}
That is indeed the Nginx per-IP rate limits, are you sure you are not behind a reverse proxy which is incorrectly sending all client IP addresses as the same IP address?
Is it always the same users? Are they trying to use the API?
If it’s not and they aren’t then check the profiles of some affected users, do their IPs look accurate? Are they all the same or similar? If so it’s either a misconfigured reverse proxy or something like Cloudflare being used with the orange cloud enabled without the template specified in the YML.
Yes they are using the same user, to generate a lot of posts per minute (via user API key).
But they now complain they are limited in terms of number of posts allowed for that user.
Do you think it could help if I increase: DISCOURSE_MAX_REQS_PER_IP_PER_MINUTE : 1000 DISCOURSE_MAX_REQS_PER_IP_PER_10_SECONDS : 500
I want to be able to set the rate of a particular API for admin
I don’t know how to modify the global rate
I’d appreciate it if you could tell me where it is
I come from china,so My English is bad, very sorry.