2 people reported

All time, since Oct 10.

Sockets not permitted in proxy sandbox

“Wait for the DevTools endpoint; Chromium terminates before it becomes available.”

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

Operation not permitted on sockets in managed-proxy Linux sandbox. In a workspace-write sandbox with a managed proxy, Chromium exits before DevTools starts and package installs fail connecting to the proxy.

Is this your bug?

File my report
Where
cloud sandbox
Error text
FATAL:chrome/browser/process_singleton_posix.cc:297] Check failed: . socket() failed: Operation not permitted (1)
Platforms
Linux
How bad
Stops work: a core feature can't be used.

Original reports2, newest first

  1. Cloud sandbox restrictions block dependency installation and Chromium startupOn GitHub#53187
  2. Chromium exits before CDP startup with socket() EPERM in managed-proxy Linux environmentOn GitHub#52927

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.