What this error means

Enable JavaScript and cookies to continue — 403 Cloudflare challenge on image generation is a LiteLLM failure pattern reported for developers trying to fix litellm image generation failing with cloudflare 403 challenge for chatgpt subscriptions. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

LiteLLM users with ChatGPT subscription get 403 Cloudflare challenge when attempting image generation. Error message: 'Enable JavaScript and cookies to continue'. Related issue #27175 confirms this is a recurring pattern. The LiteLLM proxy cannot solve JS-based Cloudflare challenges.

Common causes

  • Developers using LiteLLM proxy with ChatGPT subscription for image generation receive Cloudflare 403 challenges ('Enable JavaScript and cookies to continue'). The LiteLLM proxy cannot handle browser-based JS challenges, blocking image generation entirely.
  • LiteLLM users with ChatGPT subscription get 403 Cloudflare challenge when attempting image generation. Error message: 'Enable JavaScript and cookies to continue'. Related issue #27175 confirms this is a recurring pattern. The LiteLLM proxy cannot solve JS-based Cloudflare challenges.

Quick fixes

  1. Confirm the exact error signature matches Enable JavaScript and cookies to continue — 403 Cloudflare challenge on image generation.
  2. Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
  3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.