Reconnecting 502 Bad Gateway

Resolved 💬 5 comments Opened Jan 8, 2026 by AkanshDivker Closed Jan 12, 2026

What version of Codex is running?

0.79.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.1-codex-max, gpt-5.2-codex

What platform is your computer?

Darwin 25.1.0 arm64 arm

What issue are you seeing?

Been facing reconnecting issues for the past 1-2 days. Codex is generally able to read through my codebase before running into this issue. But as soon as it starts to do some work, it generally fails pretty quickly with a reconnecting issue.

````
• Reconnecting... 4/5 (16m 38s • esc to interrupt)
└ Unexpected status 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body>…

````

````
■ unexpected status 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>cloudflare</center>
</body>
</html>
, request id:

````

What steps can reproduce the bug?

Thread ID: 019b9f87-7391-7ae2-93a0-f25ca7fa218a

Edit: I saw in another reply that my logs are unavailable, possibly because of the bug in this issue. Is there something else I can do to provide the relevant information?

What is the expected behavior?

Task completion

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗