Connection Lost (repeatedly) - N8N Cloud - Constant Websocket Fail

Questions
1

I’ve been seeing a constant “Connection lost” issue in the n8n Cloud editor and spent some time isolating it.

The WebSocket connection to the push endpoint connects successfully (HTTP 101), but then drops after about 2–4 seconds and immediately reconnects. This repeats continuously. In the console, it shows:

[WebSocketClient] Connection lost, code=1005

So this isn’t a failed connection — it’s being terminated without a proper close frame.

I went through a pretty thorough set of tests to rule out local issues. The behavior is identical across Chrome (clean profile) and Brave, across multiple machines, and across different networks including Verizon Fios, a Verizon mobile hotspot, and even a VPN connection routed through London. I also disabled QUIC/HTTP3, Secure DNS, and ran without extensions. None of that changed the behavior.

A couple of things stand out. The WebSocket handshake always succeeds, but the connection is never maintained. The exact duration varies slightly depending on region, but it always drops quickly and reconnects. I’m also occasionally seeing 403 responses from an ingest endpoint, which suggests there may be some edge or routing inconsistency.

At this point it doesn’t look client-side. It feels like the WebSocket (push) connection is being dropped somewhere upstream — possibly at the Cloudflare edge or within the n8n Cloud push backend itself.

Workflows still execute fine, but the editor UX is degraded because it can’t maintain a stable real-time connection.

Curious if anyone else on n8n Cloud is seeing this, or if this might be regional or account-specific.

2

@DPAM does it still happens when you use an incognito window? If that does, then it is clearly a n8n cloud side problem, although as you have said the workflow still executes and works fine, but in case if the problem escalates, feel free to reach out at support channels:

3

I have the same Lost connection issue. Seems like it only happens when I open two n8n tabs in the same browser window. The problem persists even if I drag one tab to another window. But it doesn’t happen if I open a new window and then navigate to n8n.

To isolate this problem, I tried,

  • fresh install of n8n with fresh database
  • install n8n on a different server
  • many permutations of http vs https in environment variables and while testing access
  • different browsers
  • different computers
  • different cloudflared instances
  • etc.
4

Interesting deep-dive! A few things that might help narrow it down:

  1. Check X-Forwarded-For headers — if you’re behind a proxy/VPN, Cloudflare sometimes terminates WebSocket connections when it can’t verify the origin. Try opening n8n without the VPN to see if the behavior differs.

  2. Browser DevTools WebSocket frame analysis — open Network tab, filter by WS, and check if the server is sending a CLOSE frame (status 1000/1001) or if the connection just dies. That tells you whether it’s a server-side graceful close or an abrupt termination.

  3. Try a different push backend temporarily — if you have access to n8n Cloud settings, check if there’s a different region/edge endpoint you can route to. Sometimes Cloudflare edge regions have quirky behavior.

  4. Check browser TLS/Network settings — some recent Chromium updates changed how they handle keep-alive timeouts. Try disabling QUIC entirely in chrome://flags (you already did) and check if you have any proxy software installed (Proxyman, Fiddler, etc) that might be terminating long-lived connections.

The fact that it reconnects immediately suggests the client is healthy—pointing to infrastructure-level socket termination.

1 Like