Falling back from WebSockets to HTTPS transport.

Resolved 💬 4 comments Opened Mar 1, 2026 by ValadaresX Closed Mar 1, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Description
When opening the Codex-CLI, a warning appears stating that the WebSockets connection was terminated before the response finished ("stream disconnected before completion"), and therefore the application automatically switched to using HTTPS.

Environment
OS: Microsoft Windows 10 Pro (10.0.19045 build 19045)
System: MSI MS-7C37 (AMD64 Family 23 Model 113 @ 3.6GHz)
Memory: 32GB RAM
Codex CLI: v0.106.0
Node.js: v25.2.1
npm: 11.11.0
Antivirus: ESET v19.14.0
Pi-hole: Core v6.4 | FTL v6.5 | Web v6.4.1

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #13168
  • #13158
  • #13041
  • #13143
  • #13039

Powered by Codex Action

kali113 · 5 months ago

#13041

nylla8444 · 3 months ago

I need to up this because its been months already and we still experience this "Falling back from WebSockets to HTTPS transport. stream disconnected before completion: websocket closed by server before response.completed"

can we please prioritize functional stuff before shipping "Pets", tysm

Forux · 3 months ago

I am getting the same very often "Falling back from WebSockets to HTTPS transport. stream disconnected before completion: websocket closed by server before response.completed"

Macos, VS Code plugin, Codex cli - both, latest