Cloud task proxy:8080 unreachable

“Codex Cloud cannot connect to its automatically configured internal HTTP/HTTPS proxy at http://proxy:8080.”

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/themes/204/file
Follow it to file my report. Show me the text before you send.

Fading. No reports and thumbs-up in the last 7 days and 2 the week before, down from 6 a week at the early-October peak.

curl exit 7 "Failed to connect to proxy port 8080 after 0 ms" with HTTP 000 although proxy hostname resolves
Fails with internet access set to All (unrestricted) as well as restricted or Package managers allowlists
Persists after enabling internet, allowlisting domains, republishing and starting fresh tasks
Intermittent: same published environment reaches GitHub in some task VMs but not others
git fetch, GitHub, Google OAuth and tool downloads blocked; bypassing the proxy fails with DNS errors or socket permission denied

Setup-stage or environment onboarding repository access, which succeeds in these reports
Local Codex CLI or desktop app network or proxy settings

Oct 29, 2026[Codex Cloud] Managed proxy:8080 unreachable after internet enable and republish (curl 7 / HTTP 000)On GitHub#58059
Oct 23, 2026Codex Cloud: managed proxy proxy:8080 unreachable in restricted (Package managers) environmentOn GitHub#56491
Oct 15, 2026[Codex Cloud] Internal proxy:8080 TCP connection fails despite internet access enabledOn GitHub#54179
Oct 8, 2026Intermittent Codex Cloud proxy port 8080 failures across isolated task VMsOn GitHub#52321
Oct 8, 2026Default proxy connectivity in Codex Cloud brokenOn GitHub#52161
Oct 4, 2026Codex Cloud runtime cannot access outbound network: proxy unreachable and direct DNS failsOn GitHub#50988
Oct 4, 2026Codex Cloud runtime cannot access outbound network - proxy:8080 unreachable and direct DNS failsOn GitHub#50986