2 people reported

All time, since Oct 12.

IPv4 literal TLS mismatch

“In the ChatGPT/Dot cloud execution environment, HTTPS requests to an IPv4-literal URL fail during TLS identity verification before any HTTP response.”

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

HTTPS requests to IPv4-literal URLs fail TLS identity check. Proxy-generated certificate has no usable iPAddress SAN for the target IP, so the request fails before any HTTP response in the cloud environment.

Is this your bug?

File my report
Where
Cloud HTTPS proxy
Error text
CERTIFICATE_VERIFY_FAILED: IP address mismatch, certificate is not valid for '<ipv4>'
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. [ChatGPT / Dot cloud] HTTPS proxy cert for IPv4 literals fails IP SAN check (same class as #53406)On GitHub#56358
  2. [Codex Cloud] HTTPS proxy encodes IPv4 literals as DNS SANs, causing IP address mismatchOn GitHub#53406

Do you work on Codex?

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