502 Bad Gateway

Resolved 💬 7 comments Opened Apr 3, 2026 by yzzqwq Closed Apr 3, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

reconnecting 5/5: unexpected status 502 Bad Gateway: Unknown error, url: http://127.0.0.1:8327/v1/responses

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#14743

Powered by Codex Action

etraut-openai contributor · 3 months ago

This error is often due to configuration problem with a VPN, proxy, or firewall.

There's not enough information for us to investigate the problem.

If you'd like to report a bug report, please fill out the information requested in the bug template. For bugs like this, we'll also need you to use /feedback to upload your logs and session details and include your thread ID in the bug report.

yzzqwq · 3 months ago

I'm using the Windows version of Codex. There were no obvious error messages, and it worked fine before, but this error occurred today. The thread ID of the project I'm testing is: 019d5154-9248-77e0-8ecd-1b05d519bd71

yzzqwq · 3 months ago

My VPN proxy port is 7897, and I'm using rule-based proxy mode. Why is it switching to port 8327, and how can I fix it?

yzzqwq · 3 months ago

I deleted the .codex folder, reset the configuration, and that solved the problem.

Ewannai · 1 month ago

我删除了.codex文件夹，重置了配置，问题就解决了。

I reinstalled Codex, but this error still occurs. unexpected status 502 Bad Gateway: Unknown error, url: http://127.0.0.1:8327/v1/responses

lily-jiang1998 · 1 month ago

I deleted the .codex folder, reset the configuration, and that solved the problem.

so it is fault about the .codex folder? Modify the contents of auth.json file ?