Skip to content

Codex & Work "Reconnection" Issue #46148

Closed

Description

@LowkyFoolDev

What version of the Codex App are you using (From “About Codex” dialog)?

26.911.61220

What subscription do you have?

Pro

What platform is your computer?

No response

What issue are you seeing?

Image While using Work & Codex on the desktop App on my Mac , I am getting this Reconnection Issue. The message:-- "Reconnecting... 1/5"

What steps can reproduce the bug?

Image I'm experiencing the same issue.

Environment:

  • macOS
  • Apple Silicon Mac
  • ChatGPT Plus subscription
  • Codex Desktop version: 26.911.61220
  • Codex Desktop and Codex CLI/terminal are both affected

Symptoms:

  • Codex shows: "Reconnecting... waiting for network"
  • Requests eventually fail to connect/send
  • Normal internet access works correctly
  • ChatGPT works normally in the browser
  • I tested different networks / Wi-Fi and the problem persists

This appears to affect both the local Codex desktop app and the terminal version, while the web version continues to work.

Please let me know if there are any logs, diagnostics, or additional information I can provide.

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    appIssues related to the Codex desktop app
    on Sep 17, 2026
  2. added
    bugSomething isn't working
    connectivityIssues involving networking or endpoint connectivity problems (disconnections)
    on Sep 17, 2026
  3. timothyericsson commented on Sep 17, 2026

    @timothyericsson

    Same issue on my end

  4. Jiaqi-Bi-Not-PhD commented on Sep 18, 2026

    @Jiaqi-Bi-Not-PhD

    Adding another reproduction of this issue.

    Environment

    • macOS
    • Apple Silicon M3
    • ChatGPT Pro
    • Codex Desktop version: 26.911.61220

    Symptoms

    • Codex repeatedly displays:
      Reconnecting... waiting for network
    • It eventually reports:
      Connection failed: error sending request
    • The problem occurs repeatedly and prevents requests from completing.

    Network isolation test

    • I initially reproduced this on my normal Internet connection.
    • I then disconnected from that network and connected the Mac to my personal cellular hotspot.
    • The exact same failure persisted on the cellular hotspot.

    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 network

    followed by:
    Connection failed: error sending request

  5. hnidboubker commented on Sep 18, 2026

    @hnidboubker

    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!

    Image Image Image
  6. mattmcgiv commented on Sep 18, 2026

    @mattmcgiv

    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

    Image
  7. LowkyFoolDev commented on Sep 18, 2026

    @LowkyFoolDev
    Author

    same problem bro☹️

  8. claudiupopa commented on Sep 18, 2026

    @claudiupopa

    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.

  9. claudiupopa commented on Sep 18, 2026

    @claudiupopa
    Image Updated the app, still the same
  10. hnidboubker commented on Oct 1, 2026

    @hnidboubker

    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.

  11. havramar commented on Oct 4, 2026

    @havramar

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingconnectivityIssues involving networking or endpoint connectivity problems (disconnections)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions