Cloudflare Workers, running the site's own code at the edge.
Cloudflare error 1101 — Worker threw exception
A Cloudflare Worker — the site's own JavaScript, running at the edge — threw an unhandled exception while serving your request. The origin was probably never reached, and the error is in code the site deployed.
A proxy does not fix this. Someone else's code threw an exception. Your address is not an input to it, so no pool, geo or rotation changes the outcome — the fix belongs to whoever deployed the Worker.
Why it happens
A bug in the site's edge code, sometimes triggered by an unusual path or header.
The Worker hit a CPU or memory limit.
A downstream call the Worker depends on failed and the error was not handled.
How to fix it
- Retry; some Worker exceptions are load-dependent.
- Try a simpler request — if a specific parameter triggers it, that is the site's bug and worth reporting.
FAQ
What does 1101 mean?›
A Cloudflare Worker — the site's own JavaScript, running at the edge — threw an unhandled exception while serving your request. The origin was probably never reached, and the error is in code the site deployed. Cloudflare Workers, running the site's own code at the edge.
Why am I getting 1101?›
A bug in the site's edge code, sometimes triggered by an unusual path or header. The Worker hit a CPU or memory limit. A downstream call the Worker depends on failed and the error was not handled.
How do I fix 1101?›
Retry; some Worker exceptions are load-dependent. Try a simpler request — if a specific parameter triggers it, that is the site's bug and worth reporting.
Will a proxy fix 1101?›
Someone else's code threw an exception. Your address is not an input to it, so no pool, geo or rotation changes the outcome — the fix belongs to whoever deployed the Worker.