Cloudflare WebSocket Connection Drops

Hi Sanne

The 100‑second drop with code 1006 is almost always Cloudflare’s idle timeout kicking in. By default, Cloudflare closes WebSocket connections if they don’t see traffic for about that window. The trick is to configure keep‑alive pings from both client and server send a ping every 30–60 seconds and make sure the server replies with pong. That keeps the tunnel “active” in Cloudflare’s eyes. On top of that, check your Cloudflare idle timeout settings in the dashboard; depending on your plan, you can extend the limit beyond the default. Also make sure your origin server (like Nginx or IIS) has its own read timeout set longer than Cloudflare’s, otherwise you’ll still see drops. If you’re on Enterprise, you can ask Cloudflare support to bump the idle timeout higher, but for most setups, regular ping/pong frames are enough to keep connections alive.

If this explanation helps you stabilize your WebSocket sessions, please hit “accept answer” so we know the response was useful

Please "Accept the answer" so that it could be spread further to those in need too. If not, is there anything I can help you with? Please let me know.