You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Id feedback = no-active-thread-01a0b2a4-9ad4-7d81-99b2-22139f4290bc
Codex has been unable to connect since I installed it. I constantly get the following error:
“Reconnecting... waiting for network
Connection failed: error sending request”
Unfortunately, I’m experiencing the same issue with ChatGPT Desktop, Codex in the terminal, and the Codex interface integrated into VS Code.
It seems to be a general connectivity issue rather than something specific to a particular interface.
Could someone please help me identify the cause of this issue and find a solution?
macOS / Apple Silicon / ChatGPT Plus
ChatGPT Desktop version: 26.915.31029
Work and Codex in the desktop app are stuck on "Reconnecting... waiting for network". Regular ChatGPT works normally, and Work works correctly in Safari on chatgpt.com.
Troubleshooting already performed:
Signed out and revoked active sessions, then signed in again
Tested both regular Wi-Fi and mobile hotspot, same result
No macOS proxy configured
No HTTP_PROXY / HTTPS_PROXY / ALL_PROXY variables in the shell or ~/.codex/.env
DNS and TCP/443 connectivity are working
ws.chatgpt.com is reachable
curl to https://chatgpt.com/backend-api/codex returns HTTP/2 403 with cf-mitigated: challenge
The issue appears isolated to Work/Codex in the desktop client. Browser Work continues to function normally.
In my case, it was the Headroom proxy that was misconfigured in the Codex settings. After removing it from the settings completely, everything started to work again.
Activity
github-actions commentedon Sep 17, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
timothyericsson commentedon Sep 17, 2026
Same issue on my end
Jiaqi-Bi-Not-PhD commentedon Sep 18, 2026
Adding another reproduction of this issue.
Environment
Symptoms
Reconnecting... waiting for networkConnection failed: error sending requestNetwork isolation test
Therefore, changing the network/router/public Internet connection does not resolve the issue.
ChatGPT Web continues to function while Codex Desktop experiences the failure.
The issue was reproduced on September 17, 2026, including around 9:09 PM EDT.
The failure pattern is repeated:
Reconnecting... waiting for networkfollowed by:
Connection failed: error sending requesthnidboubker commentedon Sep 18, 2026
Hello,
Id feedback = no-active-thread-01a0b2a4-9ad4-7d81-99b2-22139f4290bc
Codex has been unable to connect since I installed it. I constantly get the following error:
“Reconnecting... waiting for network
Connection failed: error sending request”
Unfortunately, I’m experiencing the same issue with ChatGPT Desktop, Codex in the terminal, and the Codex interface integrated into VS Code.
It seems to be a general connectivity issue rather than something specific to a particular interface.
Could someone please help me identify the cause of this issue and find a solution?
Thanks in advance for your help!
mattmcgiv commentedon Sep 18, 2026
Stuck in a reconnecting loop for 12 hours or so across chats.
ChatGPT for MacOS Version 26.911.61220
Submitted feedback with logs as feedback id 01a0ac4b-e060-7d63-b2da-2d8cd1cf6f19
LowkyFoolDev commentedon Sep 18, 2026
same problem bro☹️
claudiupopa commentedon Sep 18, 2026
macOS / Apple Silicon / ChatGPT Plus
ChatGPT Desktop version: 26.915.31029
Work and Codex in the desktop app are stuck on "Reconnecting... waiting for network". Regular ChatGPT works normally, and Work works correctly in Safari on chatgpt.com.
Troubleshooting already performed:
Signed out and revoked active sessions, then signed in again
Tested both regular Wi-Fi and mobile hotspot, same result
No macOS proxy configured
No HTTP_PROXY / HTTPS_PROXY / ALL_PROXY variables in the shell or ~/.codex/.env
DNS and TCP/443 connectivity are working
ws.chatgpt.com is reachable
curl to https://chatgpt.com/backend-api/codex returns HTTP/2 403 with cf-mitigated: challenge
The issue appears isolated to Work/Codex in the desktop client. Browser Work continues to function normally.
claudiupopa commentedon Sep 18, 2026
hnidboubker commentedon Oct 1, 2026
Finally, I solved my problem! After searching and searching, and since I’m pretty stubborn 😅, I finally figured out where the issue was coming from.
I don’t know why he had configured models or why he had used .claude-code-router, but I eventually started over from scratch.
I uninstalled everything: Codex CLI as well as ChatGPT Desktop. Then I deleted the .codex and .codex-log folders.
After restarting my PC, I reinstalled ChatGPT Desktop and then Codex.
I also ran these commands in PowerShell:
Remove-Item Env:CODEX_CA_CERTIFICATE -ErrorAction SilentlyContinue
Remove-Item Env:SSL_CERT_FILE -ErrorAction SilentlyContinue
[Environment]::SetEnvironmentVariable("CODEX_CA_CERTIFICATE",$null,"User")
[Environment]::SetEnvironmentVariable("SSL_CERT_FILE",$null,"User")
Then, I closed all PowerShell/Git Bash windows as well as Codex, and reopened them.
To check that the variables had indeed been removed:
echo $env:CODEX_CA_CERTIFICATE
echo $env:SSL_CERT_FILE
And there you go, the problem was solved! 🎉
I’m sharing this in case these steps can help someone else who runs into the same problem.
havramar commentedon Oct 4, 2026
In my case, it was the Headroom proxy that was misconfigured in the Codex settings. After removing it from the settings completely, everything started to work again.