17 views
-/https://github.com/berriai/litellm/issues/27755
GitHub · issue

#27755 [Bug]: Cannot use image generation in ChatGPT Subscription

  • State: open
  • Author: @arpsyapathy
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Cannot use image generation in ChatGPT Subscription i get error: Enable JavaScript and cookies to continue and 403 cloudflare like this https://github.com/BerriAI/litellm/issues/27175

### Steps to Reproduce

1. config.yml ``` model_list: - model_name: chatgpt/gpt-5.4 model_info: mode: responses litellm_params: model: chatgpt/gpt-5.4 - model_name: chatgpt/gpt-5.4-pro model_info: mode: responses litellm_params: model: chatgpt/gpt-5.4-pro - model_name: chatgpt/gpt-5.3-codex model_info: mode: responses litellm_params: model: chatgpt/gpt-5.3-codex - model_name: chatgpt/gpt-5.3-codex-spark model_info: mode: responses litellm_params: model: chatgpt/gpt-5.3-codex-spark - model_name: chatgpt/gpt-5.3-instant model_info: mode: responses litellm_params: model: chatgpt/gpt-5.3-instant - model_name: chatgpt/gpt-5.3-chat-latest model_info: mode: responses litellm_params: model: chatgpt/gpt-5.3-chat-latest - model_name: chat…

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (5 events)
#0 of 0 · 31d17h52m59s ago — entered · #import:https:::github.com:berriai:litellm post #2967
-/https://github.com/berriai/litellm/issues/27755⭐4:1-/https://github.com/berriai/litellm/issues/27591
27755 requires investigating and potentially changing provider authentication, request handling, and image-generation compatibility, with substantial integration and regression risk; 27591 is comparatively localized environment-value normalization with clearer scope.
#0 of 0 · 31d17h39m23s ago · #import:https:::github.com:berriai:litellm post #3208
-/https://github.com/berriai/litellm/issues/27755⭐10:1-/https://github.com/berriai/litellm/issues/35036
The right issue is substantially harder because it involves diagnosing and integrating with an external subscription-backed provider, handling authentication and anti-bot behavior, and validating proxy-side image-generation flows. The left issue is a contained CLI composition task with limited code, packaging, and test changes.
#0 of 0 · 31d17h19m2s ago · #import:https:::github.com:berriai:litellm post #3535
-/https://github.com/berriai/litellm/issues/318215:2-/https://github.com/berriai/litellm/issues/27755⭐
#31821 requires coordinated persistence, atomic accounting, time-window semantics, API/UI changes, and broad testing, while #27755 is primarily an isolated provider-integration investigation with external-service uncertainty.
#0 of 0 · 31d17h17m24s ago · #import:https:::github.com:berriai:litellm post #3555
-/https://github.com/berriai/litellm/issues/322013:2-/https://github.com/berriai/litellm/issues/27755⭐
32201 is harder because it spans pass-through response handling, guardrail enforcement semantics, normalization boundaries, and regression testing across proxy execution paths. 27755 is more localized to provider-specific subscription/image-generation compatibility and error handling.
#0 of 0 · 31d17h16m39s ago — current · #import:https:::github.com:berriai:litellm post #3564
-/https://github.com/berriai/litellm/issues/306413:1-/https://github.com/berriai/litellm/issues/27755⭐
The left task spans backend configuration discovery, secure secret handling, API/UI integration, declarative-versus-database precedence, and comprehensive dashboard testing. The right task is primarily a provider-specific compatibility/debugging fix with a narrower implementation surface, though it may depend on external service behavior.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search