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
{{ message }}
Repository navigation
not able to connect to codex --- keeps saying reconnecting #9556
@saiaprameya, I looked at your logs. It's the same problem that you reported previously. Codex isn't able to connect to the OpenAI endpoint https://chatgpt.com/backend-api/codex/responses. This appears to be a networking issue on your machine or network. You'll need to do some diagnosis of your own to figure out why this endpoint isn't reachable.
@Howchie, unfortunately, your logs didn't get uploaded. We had a temporary service issue where uploads of logs were being rejected. This has now been addressed. If you're still able to repro this problem, please use the /feedback command again and open a new bug report. Sorry for the inconvenicence.
Activity
github-actions commentedon Jan 20, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Jan 20, 2026
Please use the
/feedbackslash command to upload your logs and session details, then post the thread ID here.Howchie commentedon Jan 21, 2026
019bde35-ec01-7732-8456-f6fdefa4b659
Same error on windows using cli or VSCode (NOT in WSL mode), my ubuntu server with same credentials is working fine.
saiaprameya commentedon Jan 21, 2026
Here it is:
• Feedback uploaded. Please open an issue using the following URL:
https://github.com/openai/codex/issues/new?template=2-bug-report.yml&steps=Uploaded%20thread:%20019bdef0-11e6-7050-b09b-95e974da69cf
Or mention your thread ID 019bdef0-11e6-7050-b09b-95e974da69cf in an existing issue.
etraut-openai commentedon Jan 21, 2026
@saiaprameya, I looked at your logs. It's the same problem that you reported previously. Codex isn't able to connect to the OpenAI endpoint
https://chatgpt.com/backend-api/codex/responses. This appears to be a networking issue on your machine or network. You'll need to do some diagnosis of your own to figure out why this endpoint isn't reachable.@Howchie, unfortunately, your logs didn't get uploaded. We had a temporary service issue where uploads of logs were being rejected. This has now been addressed. If you're still able to repro this problem, please use the
/feedbackcommand again and open a new bug report. Sorry for the inconvenicence.lbrendle commentedon Jan 23, 2026
019beb17-e7b2-7191-848b-9d25b4a00ab
019beaab-7754-7d91-a54f-54ed606a7bc