Rank, 14 days: 155 on the Codex sheet
10 people reported
All time, since Oct 4, including 4 thumbs-up on GitHub.
Cloud proxy:8080 unreachable
“Codex Cloud runtime cannot access external network resources.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/9695/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Codex Cloud tasks cannot reach managed proxy on port 8080. Outbound requests fail with no HTTP response (HTTP 000) even with internet access enabled and domains allowlisted; bypassing the proxy fails on DNS resolution.
Is this your bug?
File my report- Where
- Codex Cloud runtime
- Error text
curl: (7) Failed to connect to proxy port 8080 after 0 ms: Could not connect to server- Versions
- 0.163.0
- Platforms
- Linux, Windows
- How bad
- Stops work: a core feature can't be used. Some reports say it blocks them completely.
Not quite your bug?
- Cloud setup fails with two accounts5 people
- Network blocked despite setting on6 people
- Shell network blocked7 people
Original reports7, newest first
- [Codex Cloud] Managed proxy:8080 unreachable after internet enable and republish (curl 7 / HTTP 000)On GitHub#58059
- Codex Cloud: managed proxy proxy:8080 unreachable in restricted (Package managers) environmentOn GitHub#56491
- [Codex Cloud] Internal proxy:8080 TCP connection fails despite internet access enabledOn GitHub#54179
- Intermittent Codex Cloud proxy port 8080 failures across isolated task VMsOn GitHub#52321
- Default proxy connectivity in Codex Cloud brokenOn GitHub#52161
- Codex Cloud runtime cannot access outbound network: proxy unreachable and direct DNS failsOn GitHub#50988
- Codex Cloud runtime cannot access outbound network - proxy:8080 unreachable and direct DNS failsOn GitHub#50986