Worker has stopped working from a specific IP

Hi. I have been using a worker for serverless stuff.

This worker is it called from a server which has an IP. The worker has been working without any issues for weeks.

However, today has stopped working when the petition is from this IP. If you call the worker from other network, it works as expected.

The error is:

Please enable cookies
        <h1>

          <span class="cf-error-type" data-translate="error">Error</span>
          <span class="cf-error-code">1102</span>
          <small class="heading-ray-id">Ray ID: XXXXX

 <h2 data-translate="what_happened">What happened?</h2>
You've requested a page on a website (myworker-example.workers.dev) that is on the www.cloudflare.com/5xx-error-landing?utm_source=error_100x.k. An unknown error occurred while rendering the page.

From what I could find 1102 is a CPU/Memory-limit error, you might only see these errors when you have enough load on the workers. I’d suggest doing load-testing to find these issues.

Yeah, I saw that code first on docs, but I doesn’t have sense.
As I mentioned, it seems like the worker has banned this IP, because calling from other networks it works like usual.
Any ideas how to disable abuse protection or something like that?

There’s no setting like that I think, you’d better raise a ticket with Cloudflare about the issue.

Taking a wild guess that responses are cached, so other IPs get a cached version but this IP doesn’t get the cache and hits the resource limit.

How many requests does that IP in a timeframe?

Not too much. I think less than a few hundreds (~300) per hour