Abuse protection is rejecting API traffic from our servers
Requests to api.trigger.dev are getting blocked by a “worker” rate limiter rule with 429 responses and the code 1015. These requests are coming from our Digital Ocean cluster and shouldn’t be getting blocked.
We have a Cloudflare worker for api.trigger.dev, but the traffic that's getting blocked is just passed through to the original URL.
What we’d like to have happen:
Prevent the rate limiting rule to block traffic from ASN 14061 which is our DigitalOcean cluster, or maybe just turn off the rate limiter altogether (we have our own rate limiter). Alternatively, if you want to be more restrictive, we could turn off blocking for requests with the header x-trigger-worker (which all requests will have if they are inside a task)
Here’s some sample events that are getting blocked that shouldn’t:
Note that it’s not all from 1 IP. We run a lot of servers in this cluster that each have a different public IP address in quite a broad range.
We have a Cloudflare worker for api.trigger.dev, but the traffic that's getting blocked is just passed through to the original URL.
What we’d like to have happen:
Prevent the rate limiting rule to block traffic from ASN 14061 which is our DigitalOcean cluster, or maybe just turn off the rate limiter altogether (we have our own rate limiter). Alternatively, if you want to be more restrictive, we could turn off blocking for requests with the header x-trigger-worker (which all requests will have if they are inside a task)
Here’s some sample events that are getting blocked that shouldn’t:
Note that it’s not all from 1 IP. We run a lot of servers in this cluster that each have a different public IP address in quite a broad range.
