Repository navigation
stream disconnected - retrying sampling request (1/5 in 205ms)-codex #52380
Description
What version of the Codex App are you using (From “About Codex” dialog)?
0.153.4
What subscription do you have?
stream disconnected - retrying sampling request (1/5 in 205ms)-codex
What platform is your computer?
No response
What issue are you seeing?
WARN codex_core::responses_retry
stream disconnected - retrying sampling request (1/5 in 205ms)...
turn_id=01a11e7e-60ec-7a30-8cd6-010e5e604426
retries=1 max_retries=5
sampling_error=unexpected status 503 Service Unavailable:
An error occurred while processing your request.
(2/5 in 401ms) ... status 503 Service Unavailable
(3/5 in 728ms) ... status 503 Service Unavailable
(4/5 in 1.553s) ... status 503 Service Unavailable
(5/5 in 3.386s) ... status 503 Service Unavailable
INFO responses_websocket:
successfully connected to websocket:
wss://chatgpt.com/backend-api/codex/responses
这次错误里没有记录 error.code、Retry-After 或服务端 request_id；相关字段是空的：
auth_error=""
auth_error_code=""
auth_request_id=""
auth_cf_ray=""
从日志看，每次重试都能重新连上 wss://chatgpt.com/backend-api/codex/responses，因此不像 TCP 443 或 WebSocket Upgrade 被完全拦截，更像服务端暂时返回 503（过载/后端不可用）。代理仍可能在握手后返回 503，但证据偏向服务端问题。
另外，当前环境确实有 Codex CLI，但版本不一致：
/opt/homebrew/bin/codex
codex-cli 0.153.4
桌面内置 CLI 是 0.160.1，当前桌面日志也显示 client_version=0.160.1。
What steps can reproduce the bug?
01a11e7e-49c0-7cd2-aff7-8de136e25b1d
What is the expected behavior?
No response
Additional information
No response
Activity
github-actions commentedon Oct 9, 2026
English translation:
What version of the Codex App are you using (From “About Codex” dialog)?
0.153.4
What subscription do you have?
stream disconnected - retrying sampling request (1/5 in 205ms)-codex
What platform is your computer?
No response
What issue are you seeing?
This error did not record
error.code,Retry-After, or the server-siderequest_id; the related fields are empty:The logs show that each retry successfully reconnects to
wss://chatgpt.com/backend-api/codex/responses, so it does not look like TCP 443 or WebSocket Upgrade is completely blocked. It looks more like the server is temporarily returning 503 (overloaded/backend unavailable). A proxy could still return 503 after the handshake, but the evidence points toward a server-side issue.Also, the current environment does have Codex CLI, but the versions differ:
The CLI bundled with the desktop app is
0.160.1, and the current desktop logs also showclient_version=0.160.1.What steps can reproduce the bug?
01a11e7e-49c0-7cd2-aff7-8de136e25b1d
What is the expected behavior?
No response
Additional information
No response
diamont1001 commentedon Oct 9, 2026
+1
重启后还登录不上了
Jeazun commentedon Oct 9, 2026
same