Repository navigation
Private ChatGPT Sites source unavailable: git.chatgpt-team.site getaddrinfo thread failed to start #54015
Description
Summary
A private ChatGPT Sites project cannot read its source repository, blocking an approved one-line configuration update.
What fails
From Codex Desktop on Windows, any Git read of the private Sites remote fails before authentication:
fatal: unable to access 'https://git.chatgpt-team.site/<redacted-private-site-repository>.git/':
getaddrinfo() thread failed to start
For example:
git ls-remote --heads origin main
The same result has persisted across repeated checks for more than a day.
Expected behavior
Codex should be able to read the existing private Sites source repository so an already-prepared, narrow configuration change can be published.
Actual behavior
The private source cannot be resolved/read. The deployed Site remains reachable, but its private Git source is not.
Notes
- This occurs before authentication; it does not appear to be a missing GitHub credential.
- No private repository URL, customer data, workbook data, or source contents are included here.
- This appears related to other recent reports involving existing Sites projects and
git.chatgpt-team.site, but the specific error isgetaddrinfo() thread failed to start. - Environment: Windows, Codex Desktop, private ChatGPT Sites project.
Could the team confirm whether there is a known issue with the private Sites source/Git connection or advise a supported recovery path?
Activity
github-actions commentedon Oct 14, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
mal9770-glitch commentedon Oct 14, 2026
Additional diagnostic result from Oct 14, 2026:
git ls-remote --heads origin mainagainst the private Sites remote fails immediately withgetaddrinfo() thread failed to start.git.chatgpt-team.siteto IPv4 addresses and a TCP connectivity test to port 443 succeeds.This isolates the immediate
getaddrinfofailure to the Codex execution environment rather than the Windows machine's general DNS or TCP connectivity. No private repository URL or source content is included.mal9770-glitch commentedon Oct 16, 2026
Follow-up (Oct 16, 2026): This remains reproducible after fully exiting and reopening Codex Desktop. From the private ChatGPT Sites worktree,
git ls-remote --heads origin mainstill fails immediately withgetaddrinfo() thread failed to startbefore authentication. The live private Site remains reachable, but an already-tested, narrow update cannot be published because its private source cannot be read.Could the Codex team please triage this Windows Desktop sandbox/networking issue or provide a supported recovery path? No credentials, private repository URL, customer data, workbook data, or source contents are needed to investigate.
mal9770-glitch commentedon Oct 16, 2026
Business-impact request: This unresolved Windows Codex Desktop networking defect is now blocking publication of a tested, private operational update for a small business field-work app. The update itself is ready and narrow; the only blocker is the inability to read the private Sites source from Codex Desktop.
Could the team confirm whether this is under active triage and, if possible, prioritize either a fix or a supported workaround? We can provide additional non-sensitive diagnostics if useful, but cannot share credentials or the private repository URL.