2 years ago
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 ?
0 Replies
2 years ago
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
2 years ago
is it a shared static ip?
2 years ago
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
2 years ago
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
2 years ago
sounds like there could be yeah
2 years ago
like a 10 connection concurrent limit
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
2 years ago
sounds good!