Answer: Use the troubleshooting table to match your symptom to what to check, and when requesting help include your client version, operating system, expected provider and model alias, authentication method, and the step that failed, along with the error message and request time. Remove tokens, cookies, authorization headers, and sensitive prompts, and don't send credential files or a configuration dump containing secrets. Status: Confirmed Entry: tool/codex/troubleshooting/troubleshoot-gateway-connection Revision: 2 Digest: sha256:f8fa8222e685f22e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:49:41Z Last changed: 2026-11-17T14:01:39Z (what not to send: — → credential files or a configuration dump containing secrets) Last verified: 2026-11-20T13:37:40Z Next check: 2026-11-21T13:37:40Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of troubleshooting approach | Troubleshoot the connection | [1] | 2026-11-20 info to include when requesting help | client version, operating system, expected provider and model alias, authentication method, and the step that failed | [1] | 2026-11-20 error details to include | the error message and request time | [1] | 2026-11-20 what to remove | tokens, cookies, authorization headers, and sensitive prompts | [1] | 2026-11-20 what not to send | credential files or a configuration dump containing secrets | [1] | 2026-11-20 Sources: [1] OpenAI. "Connect to a gateway". https://learn.chatgpt.com/docs/enterprise/connect-to-a-gateway.md Role: primary. Accessed: 2026-11-20T13:37:40Z Quote: "## Troubleshoot the connection" (Supports: troubleshooting approach) Quote: "include your client version, operating system, expected provider and model alias, authentication method, and the step that failed" (Supports: info to include when requesting help) Quote: "Include the error message and request time so the gateway owner can locate the request." (Supports: error details to include) Quote: "Remove tokens, cookies, authorization headers, and sensitive prompts." (Supports: what to remove) Quote: "Don't send credential files or a configuration dump containing secrets." (Supports: what not to send) Snapshot SHA-256: 15eaf69816d5b67ce28e980ae9e19729e556aa4089e16c7c110d50ee7736d17b (captured 2026-11-17T14:01:37Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T14:01:39Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:37:40Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:37:40Z Last attempt: 2026-11-20T13:37:40Z Notes and limitations: Extracted automatically from a single official source (section "Troubleshoot the connection"). Related: https://latestn.com/tool/codex/troubleshooting/troubleshoot-model-access How do I troubleshoot why a user in my ChatGPT workspace can't access a model in Codex? https://latestn.com/tool/codex/troubleshooting/troubleshoot-setup-runtime How do I troubleshoot setup or runtime access issues in Codex Cloud? https://latestn.com/tool/codex/troubleshooting/verify-bedrock-connection How do I verify that Codex is connected to Amazon Bedrock correctly? https://latestn.com/tool/codex/troubleshooting/resume-bulk-scan-campaign How do I resume or retry a Codex Security bulk scan campaign after it is interrupted? https://latestn.com/tool/codex/troubleshooting/security-plugin-disabled-by-admin How do I fix a Codex Security plugin that shows 'Disabled by admin' in a managed workspace? https://latestn.com/tool/codex/troubleshooting/troubleshoot-agents-md-discovery How do I troubleshoot Codex not picking up my AGENTS.md instructions? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T14:01:39Z | changed | what not to send: — → credential files or a configuration dump containing secrets | [1] 2026-11-17T14:01:39Z | changed | error details to include: — → the error message and request time | [1] 2026-11-17T14:01:39Z | changed | troubleshooting approach: — → Troubleshoot the connection | [1] 2026-11-17T14:01:39Z | changed | what to remove: Remove tokens, cookies, authorization headers, and sensitive prompts. → tokens, cookies, authorization headers, and sensitive prompts | [1] 2026-11-17T14:01:39Z | changed | info to include when requesting help: include your client version, operating system, expected provider and model alias, authentication method, and the step that failed → client version, operating system, expected provider and model alias, authentication method, and the step that failed | [1] 2026-11-17T14:01:39Z | changed | catalog or helper path check: Confirm that the file exists at the configured absolute path in the environment running Codex. → — | [1] 2026-11-17T14:01:39Z | changed | streaming stall check: Ask the gateway owner to check proxy buffering, the terminal `response.completed` event → — | [1] 2026-11-17T14:01:39Z | changed | model not found check: Confirm the supplied model name and ask the administrator to check its route. → — | [1] 2026-11-17T14:01:39Z | changed | API-key or helper auth check: Check that the credential variable reaches the client process, or that the installed helper can retrieve a current token. → — | [1] 2026-11-17T14:01:39Z | changed | OAuth failure check: Check the public client registration, redirect URI, scopes, and configured cookie or header. → — | [1] 2026-11-17T14:01:39Z | changed | provider not active check: Check the selected profile and configuration precedence. → — | [1] 2026-11-13T03:49:41Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/troubleshooting/troubleshoot-gateway-connection/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/troubleshooting/troubleshoot-gateway-connection POST: https://latestn.com/dispute/tool/codex/troubleshooting/troubleshoot-gateway-connection with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/troubleshooting/troubleshoot-gateway-connection?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I troubleshoot a Codex gateway connection that isn't working? Revision 2, last verified 2026-11-20T13:37:40Z. https://latestn.com/tool/codex/troubleshooting/troubleshoot-gateway-connection (accessed 2026-11-21T10:02:39Z). @misc{LatestN_tool_codex_troubleshooting_troubleshoot_gateway_connection_r2, title = {How do I troubleshoot a Codex gateway connection that isn't working?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/troubleshooting/troubleshoot-gateway-connection}}, note = {Revision 2; digest sha256:f8fa8222e685f22e; last verified 2026-11-20T13:37:40Z; accessed 2026-11-21T10:02:39Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/troubleshooting/troubleshoot-gateway-connection