openai / openai/codex

Sites deployment fails with HTTP 409 when updating login callbacks

Open
#43,851 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app auth bug
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)?

26.901.51231 (build 8109)

What subscription do you have?

prolite (plan type reported by Codex)

What platform is your computer?

macOS — Darwin 25.5.0 arm64 arm

What issue are you seeing?

My Sites website was initially published successfully. After adding and activating a custom domain, subsequent deployments repeatedly failed while updating the Sign in with ChatGPT callback configuration.

Website: https://ielts.guolinhuan.com

Error:
HTTP 409 Conflict when updating the site's login callbacks.

Version 2 was saved successfully, but deployment fails and the live website continues to show the previous version. Multiple retries produced the same error.

The custom domain and HTTPS certificate are active. The exact cause of the callback conflict is unknown.

What steps can reproduce the bug?

Feedback ID: 01a08160-8886-7361-be4d-8e31c7fe56e6

What is the expected behavior?

Deploying a saved version should succeed while preserving the existing custom domain, owner-only access, and login configuration.

The live website should display the changes from version 2 after deployment.

Additional information

Project ID:
appgprj_6aa019d6a034819189d2356592588895

Saved version ID:
appgprj_6aa019d6a034819189d2356592588895~appgver_74bccd8b6018819197e83b4de8ac7298

Latest failed deployment ID:
appgdep_6aa03085626081918ccea9611d34239f

Failure time:
2026-09-08 15:58 UTC

The production build and TypeScript checks passed before publishing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the feedback ID 01a08160-8886-7361-be4d-8e31c7fe56e6 and inspect the failed deployment ID appgdep_6aa03085626081918ccea9611d34239f alongside the project and saved version IDs. The issue is resolved when a saved version deploys successfully, the custom domain and owner-only access remain intact, and the live site shows the new version.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, typescript
Domain
authentication, cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.