n8n - 💡(How to fix) Fix Consistently disconnect (web-socket error?)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Root Cause

"I found the root cause in the browser console. The "Connection lost" issue is being caused by a repeating WebSocket failure paired with rate-limiting on n8n's telemetry endpoint:

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse

Describe the problem/error/question

The workspace keeps disconnecting (from the cloud)

What is the error message (if any)?

⚠️ connection lost

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

don't need help with this.

Claude output

"I found the root cause in the browser console. The "Connection lost" issue is being caused by a repeating WebSocket failure paired with rate-limiting on n8n's telemetry endpoint:

The WebSocket client keeps logging [WebSocketClient] Connection lost, code=1005 and "Attempting to reconnect in 1000ms" every few seconds in a tight loop.

<img width="131" height="45" alt="Image" src="https://github.com/user-attachments/assets/e4a81fb1-8423-474b-8288-826d5c37bf21" />

At the same time, requests to /rest/telemetry/proxy/v1/identify are returning HTTP 429 (Too Many Requests) repeatedly.

WebSocket close code 1005 means the server closed the connection without sending a status code, and combined with the 429s on the telemetry endpoint, this points to n8n's push/telemetry service rate-limiting your session — not a problem with your local Chrome, network, or extensions. That's why disabling extensions and hard-refreshing didn't help: the issue is server-side throttling on the n8n Cloud side, and your client is stuck in a reconnect loop that keeps re-triggering it."

Debug info

core

  • n8nVersion: 2.17.5
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/148.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-08T12:36:54.383Z

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Consistently disconnect (web-socket error?)