Codex desktop and CLI return 404 from /backend-api/codex/responses in TPE region
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
codex-cli 0.153.0-alpha.5
What subscription do you have?
Pro
What platform is your computer?
Mac
What issue are you seeing?
After updating the ChatGPT/Codex desktop app, Codex stopped working on both of my Macs.
The bundled Codex version is:
codex-cli 0.153.0-alpha.5
The same issue also occurs through an independently installed Codex CLI. The WebSocket connection fails and falls back to HTTPS, but both transports return 404:
unexpected status 404 Not Found: Unknown error
Endpoint: https://chatgpt.com/backend-api/codex/responses
Cloudflare Ray IDs:
a355ae93ab9c8092-TPE
a355aec39e48ed1d-TPE
codex doctor reports:
18 ok
1 idle
5 notes
4 warnings
0 failures
Overall status: degraded
The official CLI installer endpoint also returned HTTP 404 from my network. Regular ChatGPT web access continues to work.
Because the same problem occurs on two Macs and through both the desktop app and CLI, this appears to be a Codex backend routing or account provisioning issue rather than a local installation problem.
Please investigate the /backend-api/codex/responses route for my account or the TPE region.
What steps can reproduce the bug?
nothing else just open up the app and as soon you input any question then you will see error message
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the 404 from https://chatgpt.com/backend-api/codex/responses with both the bundled and independently installed Codex CLI, and review the reported codex doctor status. Investigate whether routing or account provisioning affects the TPE region; done means Codex requests work through both WebSocket fallback and HTTPS without the 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100