8 views
-/https://github.com/berriai/litellm/issues/25394
GitHub · issue

#25394 [Bug]: chagpt pro returns 403 on /v1/chat/completions and 400 on /health

  • State: open
  • Author: @afoninsky
  • Labels: bug, ui-dashboard

### Check for existing issues

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

### What happened?

### What happened When using the ChatGPT provider through LiteLLM, I am seeing two related failures: 1. POST /v1/chat/completions for chatgpt/* returns 403 Forbidden and asks to approve identity. 2. Health checks for the same models fail with BadRequestError: 400

This appears to be LiteLLM-specific, not an account/IP issue: - the same ChatGPT account works from the same IP through Codex CLI - the same ChatGPT account works from the same IP through VS Code Kilo / ChatGPT Pro provider

I reproduced this on both: - ghcr.io/berriai/litellm:v1.82.3 - ghcr.io/berriai/litellm:v1.83.3.rc.1

### Observed behavior:

- LiteLLM routes chatgpt/gpt-5.4 to https://chatgpt.com/backend-api/codex/chat/completions - that returns a Cloudflare challenge page and surfaces as 403 Forbidden - health checks for mode: responses send a plain string input, and the ChatGPT Responses endpoint rejects that with 400 {"detail":"Input must be a list"}

### Expected behavior: - chatgpt/gpt-5.4 should be routed through the ChatGPT Responses path and work via /v1/chat/completio…

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d18h11m50s ago — entered · #import:https:::github.com:berriai:litellm post #2869
Model omitted braces; inferred difficulty from issue scope and surface area.
Distributed counter correctness requires tracing cross-pod concurrency, Redis transaction buffering, timeout/retry semantics, reconciliation, and regression testing across deployment configurations; the other issue is narrower provider request-shape and endpoint-routing work.
The right issue is harder because it spans provider routing, authentication/endpoint compatibility, request-shape handling, and health-check behavior across shared proxy paths. The left issue is narrower: extending an existing provider-specific image-edit translation to carry one additional input, with focused multipart and regression-test changes.
#0 of 0 · 31d17h36m48s ago — current · #import:https:::github.com:berriai:litellm post #3467
The left issue requires coordinated changes to asynchronous streaming state, exception propagation, terminal event semantics, and regression coverage across multiple failure paths. The right issue is comparatively localized to provider routing and health-check input handling.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search