n8n - 💡(How to fix) Fix Continuous WebSocket disconnections in n8n Cloud editor [1 comments, 2 participants]

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…
GitHub stats
n8n-io/n8n#29540Fetched 2026-04-30 06:43:55
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • Error checking for cloud plan data
  • Error fetching user cloud account
  • error: all

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
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

The n8n editor is continuously losing its WebSocket connection and attempting to reconnect in a loop, making the editor essentially unusable. This is a server-side issue — my network connection is strong and stable (high WiFi signal, fast speed test results).

What is the error message (if any)?

Console errors observed:

  • [WebSocketClient] Connection lost, code=1005 — repeating continuously
  • [WebSocketClient] Attempting to reconnect in 1000ms — repeating continuously
  • Error checking for cloud plan data
  • Error fetching user cloud account
  • HTTP 500 on /rest/executions/{id}/stop
  • HTTP 403 on o1420875.ingest.us.sentry.io (Sentry envelope endpoint)

Please share your workflow/screenshots/recording

Connection Lost is persistent across ALL Workflows

<img width="1911" height="991" alt="Image" src="https://github.com/user-attachments/assets/1cde623e-65bc-4af5-9538-6d4708b32f47" />
(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

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

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

storage

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

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-29T16:15:41.930Z

extent analysis

TL;DR

The n8n editor's continuous WebSocket connection loss and reconnection attempts may be caused by server-side issues, and checking the server logs and adjusting the WebSocket connection settings could help resolve the issue.

Guidance

  • Investigate server-side logs to identify potential causes of the WebSocket connection loss, such as errors or timeouts.
  • Verify that the n8n server is properly configured and running without issues, checking for any recent changes or updates that may have caused the problem.
  • Consider adjusting the WebSocket connection settings, such as increasing the connection timeout or retry interval, to see if it improves the stability of the connection.
  • Check for any issues with the /rest/executions/{id}/stop endpoint, which is returning an HTTP 500 error, as this could be contributing to the connection loss.

Notes

The provided information suggests a server-side issue, but without access to the server logs or more detailed information about the n8n configuration, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Adjust the WebSocket connection settings to improve stability, as this may help mitigate the connection loss issue until the root cause can be identified and resolved.

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 Continuous WebSocket disconnections in n8n Cloud editor [1 comments, 2 participants]