API showing rate limit reached

[ishaanxgupta]

@alfaarghya,
the api is showing:
Too many request from this IP, try again in 1 hour

I tried on postman, is the service down or I am doing something wrong

I checked the rate limit in header showing this,

ratelimit	limit=60, remaining=0, reset=1173
ratelimit-policy	60;w=3600

[alfaarghya]

Is it still showing the same?

[raghav4]

Is it still showing the same?

Yes, it is.

[nur-shuvo]

I am facing the issue too @alfaarghya

[PushKaf]

+1. I tried after essentially a whole day later as well and it's still rate limiting me. Any updates on this?

ratelimit: limit=120, remaining=0, reset=1494
ratelimit-policy: 120;w=3600
retry-after: 1494

[alfaarghya]

Thanks everyone for bringing this issue.

I noticed Some time this issue occurred out of nowhere and to fix this I just clean up the server and restart it.

But It's not the optimal solution. If you guys have any suggestions on how to fix this issue let's discuss here.

[PushKaf]

I believe the current way it's handling IP addresses is incorrect. I tested the following:

Request 1 (Network A):

ratelimit: limit=120, remaining=116

Request 2 (Network B):

ratelimit: limit=120, remaining=115

Both requests hit different edge servers (per the cf-ray), but the remaining limit still went down. So it seems to be shared globally and not per IP. I believe the request sees the Proxy's IP every time and not the user. The fix should be a simple trust proxy set (something like app.set('trust proxy', 2);) so it trusts 2 proxy hops.