My Link OpenAI account fails in less than 5 seconds, and I am unable to register.

[jskorlol]

What could be the reason?

I wish there was a copy button on the link.

[masterkain]

try this: https://docs.codex-pooler.com/operators/invites/#openai-device-code-setup

yeah i'm looking at the whole wizard ui tomorrow

[jskorlol]

✅ Goal: Identify why OpenAI account linking fails almost immediately in codex-pooler.

  📝 Findings:

  - Traefik’s internal@file middleware is not responsible.
  - The middleware only controls inbound traffic to codex-pooler.
  - Device polling and /oauth/token requests are outbound connections from the Pod directly to auth.openai.com, so they do not pass through Traefik.
  - The actual cause is a device authorization polling bug in codex-pooler.
  - OpenAI returns a 403 pending response using a nested error:
    deviceauth_authorization_pending.

  - codex-pooler correctly converts this to a pending result, but omits retry_after_seconds.
  - The next stage only recognizes pending results containing that field. Without it, the normal pending state is incorrectly converted into the
    generic message:
    OAuth token exchange failed.

  - This explains why every attempt fails after almost exactly five seconds.

  ✓ Verification:

  - All seven device authorization attempts failed after an average of 5.256 seconds.
  - A live diagnostic reproduced:

  code: codex_device_authorization_pending
  status: 200
  retry_after_present: false

  - Two browser OAuth attempts completed successfully on the same cluster.
  - DNS, TLS, system time, and HTTPS connectivity from the Pod to auth.openai.com are healthy.
  - A token exchange using a previously failed device flow subsequently returned 200 with valid token fields.
  - No Cloudflare challenge was present.
  - Upstream issue #188 (https://github.com/icoretech/codex-pooler/issues/188) describes the same symptom and remains open.

  🛠 Permanent fix:
  The 403/404 pending fallback must include:

  retry_after_seconds: parse_interval(state["poll_interval_seconds"])

  This allows the caller to keep polling instead of incorrectly terminating the flow.

  ⚠️ Additional requirement:
  Device-code authorization must also be enabled in ChatGPT under:

  Settings → Security → Enable device code authorization for Codex

  See the Codex Pooler documentation (https://docs.codex-pooler.com/operators/invites/#openai-device-code-setup).

  ▶️ Immediate workaround: Use Browser authorization instead of Device authorization until a patched codex-pooler version is released.

I am sharing my results.

[jskorlol]

Thank you.
It would be great if there were a link copy button in the browser as well.

1. Since I use multiple browsers, the link session sometimes dies when copying and pasting the link into a different browser.
2. It is difficult to copy the URL when asking a friend to verify their account.

[masterkain]

you're right, noted, thanks 👍