Answer: ChatGPT and Codex require WebSocket traffic over TCP port 443 with the standard "Upgrade: websocket" handshake permitted for wss://ws.chatgpt.com (ChatGPT) and wss://chatgpt.com/ (Codex). Status: Confirmed Entry: tool/chatgpt/troubleshooting/websocket-requirements Revision: 2 Digest: sha256:e38a48aebdbe5515 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:16:17Z Last changed: 2026-11-19T11:54:45Z (Check succeeded again) Last verified: 2026-11-20T11:57:44Z Next check: 2026-11-21T11:57:44Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Port | 443 | TCP port | [1] | 2026-11-20 Handshake | Upgrade: websocket | | [1] | 2026-11-20 ChatGPT destination | wss://ws.chatgpt.com | | [1] | 2026-11-20 Codex destination | wss://chatgpt.com/ | | [1] | 2026-11-20 Codex fallback | chatgpt.com | | [1] | 2026-11-20 Sources: [1] OpenAI. "Network recommendations for ChatGPT errors on web and apps". https://help.openai.com/en/articles/9247338-network-recommendations-for-chatgpt-errors-on-web-and-apps Role: primary. Accessed: 2026-11-20T11:57:45Z Retrieved via: DeepSeek Fetch API (Markdown conversion; the original server response was not captured) Quote: "Please allow WebSocket traffic over TCP port 443" (Supports: Port) Quote: "permits the standard "Upgrade: websocket" handshake" (Supports: Handshake) Quote: "ChatGPT | wss://ws.chatgpt.com | Conversation updates and notifications" (Supports: ChatGPT destination) Quote: "Codex | wss://chatgpt.com/ | Codex model sampling and streaming" (Supports: Codex destination) Quote: "allow WebSocket upgrades to chatgpt.com over TCP port 443 for Codex traffic" (Supports: Codex fallback) Snapshot SHA-256: 56271a7a6c59af2eafcb2605456c63ca3885b1b0466bbf8f1a30ee413d209282 (captured 2026-11-19T11:54:46Z) 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]. [1] was retrieved through the DeepSeek Fetch API because a direct request did not return usable content. On this check the text of [1] was unchanged since 2026-11-19T11:54:45Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T11:57:44Z. No independent second source is configured for this entry Last successful check: 2026-11-20T11:57:44Z Last attempt: 2026-11-20T11:57:44Z Notes and limitations: Extracted automatically from a single official source (section "WebSocket requirements for ChatGPT and Codex"). Related: https://latestn.com/tool/chatgpt/troubleshooting/why-captchas-appear-frequently Why am I seeing CAPTCHAs so often in ChatGPT? https://latestn.com/tool/chatgpt/troubleshooting/work-conversation-missing-device Why does a Work conversation not appear on another device in the ChatGPT desktop app? https://latestn.com/tool/chatgpt/troubleshooting/wrong-account-reconnect How do I reconnect an app in ChatGPT if it keeps using the wrong account? https://latestn.com/tool/chatgpt/troubleshooting/voice-limits-troubleshooting What are the limits and troubleshooting steps for ChatGPT Voice? https://latestn.com/tool/chatgpt/troubleshooting/vpn-causes-captchas Does using a VPN cause CAPTCHAs in ChatGPT? https://latestn.com/tool/chatgpt/troubleshooting/wayland-support Does the ChatGPT desktop app support Wayland on Linux? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T11:54:45Z | recovered | Check succeeded again | — 2026-11-19T11:54:45Z | changed | Codex fallback: — → chatgpt.com | [1] 2026-11-17T11:58:07Z | check-failed | Could not fetch the primary source: http 403; fallback: deepseek-fetch http 404: failed to fetch URL (request_id: caa379a4-1212-4370-b5dd-1621b99511d5) | — 2026-11-13T03:16:17Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/chatgpt/troubleshooting/websocket-requirements/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/chatgpt/troubleshooting/websocket-requirements POST: https://latestn.com/dispute/tool/chatgpt/troubleshooting/websocket-requirements with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/chatgpt/troubleshooting/websocket-requirements?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What WebSocket requirements does ChatGPT and Codex need on a network? Revision 2, last verified 2026-11-20T11:57:44Z. https://latestn.com/tool/chatgpt/troubleshooting/websocket-requirements (accessed 2026-11-21T09:58:59Z). @misc{LatestN_tool_chatgpt_troubleshooting_websocket_requirements_r2, title = {What WebSocket requirements does ChatGPT and Codex need on a network?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/chatgpt/troubleshooting/websocket-requirements}}, note = {Revision 2; digest sha256:e38a48aebdbe5515; last verified 2026-11-20T11:57:44Z; accessed 2026-11-21T09:58:59Z} } 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/chatgpt/troubleshooting/websocket-requirements