openai / openai/codex

[Sites] Public site is blocked by Cloudflare for external visitors

Open
#42,950 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Powered by Codex & OWL 版本 26.901.31953

What subscription do you have?

Unknown — ChatGPT desktop app

What platform is your computer?

Windows

What issue are you seeing?

A Site created with Codex Sites is configured as public and active, but external visitors are blocked by Cloudflare before reaching the website.

Site URL:
https://seller-knowledge-assistant.jiantingjia11.chatgpt.site/

Error:
Sorry, you have been blocked.
You are unable to access chatgpt.site.

Cloudflare Ray IDs:

  • a35e9ef17f332de4
  • a36389b729050f27-LAX

Codex feedback ID:
01a06c68-fd5d-7420-a284-2fea38c3e0a6

The site owner can access the website, and the Sites management interface reports that the site is active with public access. Some application requests return HTTP 200, but external and anonymous visitors still receive the Cloudflare block page.

Expected behavior:
Anyone with the public URL should be able to open the homepage. Website login should only be required for account features.

What steps can reproduce the bug?

Feedback ID: 01a06c68-fd5d-7420-a284-2fea38c3e0a6

What is the expected behavior?
  1. Configure the Codex Site access mode as public.
  2. Deploy the Site successfully.
  3. Open the public URL in a signed-out browser or from another visitor's computer:
    https://seller-knowledge-assistant.jiantingjia11.chatgpt.site/
  4. Observe the Cloudflare “Sorry, you have been blocked” page instead of the website homepage.
Additional information

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

No repository file, test, or entry point is identified. Start by reproducing the public URL in a signed-out browser and reviewing the Codex feedback ID and Cloudflare Ray IDs; done means external visitors reach the homepage while account features can still require login.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.