API Ban
Hello, I played around with terraform and railway and find out that I've been shadow ban (sort of) like the Retry-After header in my request response is set to 86400 (24 hours).
I'm pretty sure I was under the 1000 request / hour.
In case that I've hit the limit the Retry After header should not be of 3600 ?
13 Replies
Project ID:
0101bec0-b2b4-4d32-a503-437b1843470d0101bec0-b2b4-4d32-a503-437b1843470d
can you renew your IP?
I dit it and it work but i got a static one so I'm afraid that it would happn again
I don't find anything about flooding, only rule about 1k/h
is it a shared static ip?
nop my ISP provide me a personal static IP
well can't renew that
using VPN did the track but I'm afraid that in a github action it will fail for this reason
I deal with this on my side but I'm thinking about use that in an action so I would like to understand what cause the "ban" to maybe avoid it
guess whatever you where doing with the terraform provider caused it
Yes i test like a number of requests under rate limiting and I still get the problem, I suppose there is a a delay to respect between each (or a certain number) request
sounds like there could be yeah
like a 10 connection concurrent limit
seems not enough for IAC solutions
Anyway will try to deal with it with templateDeploy, reducing api call will supress the error for now but for consequent project it will certainly be a point of failure
sounds good!