Network blocked despite setting on

“A direct TCP connection to my SSH server on port 22 fails with native socket error 10013.”

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/13379/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

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

Windows sandbox blocks network despite network access enabled. Outgoing connections fail with WSAEACCES or "Access is denied" while the executor shows CODEX_SANDBOX_NETWORK_DISABLED=1, with network_access = true in config.toml and settings.

Is this your bug?

File my report

Where: Windows sandbox
Error text: An attempt was made to access a socket in a way forbidden by its access permissions
Versions: 0.136.0 to 26.1013.4894.0
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: Full access/network setting not applied3 bugs

Shell network blocked7 people
Full access ignored in new chats4 people

Not quite your bug?

Managed networking sandbox error2 people
Sandbox setup lock failure12 people

Original reports4, newest first

Oct 28, 2026[Windows / ChatGPT Work] SSH and HTTPS TCP fail with WSAEACCES 10013 after enabling network access and granting Full accessOn GitHub#57671
Oct 22, 2026[Windows 10][Work + Codex Desktop] Networking disabled despite enabled settings; standalone CLI HTTPS succeeds (26.1016.6573.0)On GitHub#56194
Oct 21, 2026[Windows / ChatGPT Work] Executor runs as CodexSandboxOffline with approval_policy=never despite internet access enabled; SharePoint downloads fail with WSAEACCESOn GitHub#55828
Oct 12, 2026Codex Desktop on Windows applies networkAccess=false despite network access being enabledOn GitHub#53278