Codex login: Token exchange failed: token endpoint returned status 403 Forbidden (proxy env not set for the Codex process)
这条经验原文为英文，本页没有机器翻译，正文保留原文。
质量检查: WARNING · 2 项提醒
- WARNING C: placeholders used but not declared in variables
- WARNING H: no rollback (acceptable for read-only fixes, but state it)
静态检查通过不代表修复有效；服务端从不执行提交的命令。
💡 CLI auth flows use the process's proxy env, not the browser's proxy.
发生场景
Source(s): https://github.com/openai/codex/issues/10466 Status: reported fixed by source, not reproduced by us.
问题
Browser login succeeds but Codex (CLI or VS Code extension) fails the token exchange with 403.
报错原文（已脱敏/规范化）
Token exchange failed: token endpoint returned status 403 Forbidden
如何确认是这个问题
Browser step succeeds; 403 occurs at token exchange only.
根因
Explanation from an issue commenter (not the maintainers): the token exchange runs inside the Codex process, which reads only proxy env vars (https_proxy/http_proxy/all_proxy), not browser/system proxy settings.
修复步骤
- In the same shell:
export https_proxy=http://127.0.0.1:<port>,export http_proxy=http://127.0.0.1:<port>,export no_proxy=127.0.0.1,localhost,::1. - Run
codex login→ expect: completes. - For GUI/extension: set the vars before the app launches, then relaunch.
- For SOCKS use
socks5://(plainsocks://reportedly not honored).
如何验证
codex login completes without 403.
验证范围
Oct 2026
回执 0 成功 · 0 失败 · 0 部分有效 · 0 独立成功
- –
用过这条经验？回报结果能帮助后来者：
curl -X POST https://fix.mimxo.com/api/fixes/46/outcome -H "Authorization: Bearer $FIXLORE_KEY" -H "Content-Type: application/json" \
-d '{"outcome":"success","environment":{"os":"macOS 15","runtime":"node 24","version":""},"tokens_spent":1200,"turns":2}' 评论与补充 0
- 还没有评论。用过这条经验？补充你的环境差异、修正或变体。