https://blog.baifan.site/en/tags/network-configuration/Recent content in Network Configuration on ByF (BaiFan) · Daily Deep ThinkHugo -- gohugo.ioenblog@baifan.site (ByF (BaiFan))blog@baifan.site (ByF (BaiFan))CC BY-NC 4.0Tue, 31 Mar 2026 14:00:00 +0800https://blog.baifan.site/en/codex-websocket-reconnect-fix/Tue, 31 Mar 2026 14:00:00 +0800blog@baifan.site (ByF (BaiFan))https://blog.baifan.site/en/codex-websocket-reconnect-fix/<!-- more --> <p>Codex talks to the ChatGPT backend over WebSocket by default. If your network path involves Clash, a corporate proxy, cross-border transit, or Cloudflare challenge pages, that long-lived WebSocket gets killed easily — and you end up staring at <code>Reconnecting... 1/5</code> over and over. Turn off WebSocket and switch to plain HTTP streaming requests, and the problem mostly disappears.</p> <figure class="my-6 flex flex-col items-center"> <img src="https://blog.baifan.site/pictures/posts/codex-websocket-reconnect-solutions.svg" alt="Comparison of the four fixes" style="max-width: 900px;" class="rounded-lg shadow-md mx-auto " loading="lazy" /> <figcaption class="mt-2 text-center text-sm text-neutral-500 dark:text-neutral-400 italic">Comparison of the four fixes</figcaption> </figure> <h2 class="relative group">Why WebSocket Breaks Behind Proxies <div id="why-websocket-breaks-behind-proxies" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-websocket-breaks-behind-proxies" aria-label="Anchor">#</a> </span> </h2> <p>The WebSocket protocol starts with an HTTP Upgrade request; only after the server returns 101 does it switch to the long-lived connection. That long-lived connection is exactly where the problem sits — proxy servers, firewalls, and CDN nodes all run timeout policies on idle connections, and Cloudflare&rsquo;s challenge mechanism can inject an interstitial page mid-path. Any link in that chain kills the connection, and the Codex client starts <code>Reconnecting</code>.</p>