429 troppe richieste

Supporto Installazione
1

Ciao a tutti, so che ci sono già argomenti sui “too many requests”, ma questo sembra non rientrare esattamente in quella categoria.

Sto ricevendo errori 429 intermittenti su Discourse (e tutto è piuttosto lento in generale) con questo backtrace:

Error: Too Many Requests
    at s (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:9:9188)
    at a (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:9:9045)
    at o (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:9:8936)
    at Object.trigger (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:18:7223)
    at https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:18:9212
    at t.invoke (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:16:9729)
    at e.t.flush (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:16:8732)
    at e.t.flush (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:16:10782)
    at e.n._end (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:16:15440)
    at e.n.end (https://discourse.looker.com/assets/ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:16:12110)

È sempre quel link .js, un blocco di JS piuttosto imponente che per me non significa granché. L’istanza che esegue Discourse sembra essere sotto un carico minimo: il 10% della CPU, tutto il resto sembra piuttosto normale, quindi è un po’ confuso per me ricevere errori 429.

Ci sono impostazioni che posso aumentare da qualche parte per modificare il limite di velocità globale? L’istanza può gestire molto più carico di quanto Discourse sembri pensare, oppure mi sto perdendo qualcosa di più grande causato da un plugin o da un bug.

Grazie!

2 Mi Piace
2

Is your site behind a reverse proxy or anything else that would mess with real incoming IP addresses?

1 Mi Piace
3

No, I don’t believe so (and the logs capture IP addresses normally) but it does sit behind an ELB. It definitely did correlate with a significant increase in traffic (looks kind of like a DDOS attack or something)
image

But if my understanding of rate limiting is correct, that shouldn’t have affected every user— Only the user trying to visit a million times, right?

I’ll verify re: the network architecture. Thanks!

4

I believe the nginx inside the Discourse container is using the ELB IP for the rate limiting bucket instead of the original client IP.

1 Mi Piace
5

That sounds quite possible. Just verified that we do have an ELB setup in aws with nothing particularly special about it— Is is the result of something that I have misconfigured on my end?

Not 100% sure what next steps would be. If you point me in the right direction, I can probably work with my ops team to figure it out. Thanks much!

1 Mi Piace