n8n - 💡(How to fix) Fix Lost Connection / Websock Issue [4 comments, 4 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#28587Fetched 2026-04-17 08:54:48
View on GitHub
Comments
4
Participants
4
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×4subscribed ×2

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • 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

WebSocket connection to n8n editor push endpoint connects (101) but drops every ~2–4 seconds (code 1005). Occurs across:

  • Chrome and Brave
  • multiple machines
  • multiple networks (Fios, Verizon mobile)
  • VPN (different regions)

Indicates push/WebSocket layer instability.

What is the error message (if any)?

Connection Lost

Please share your workflow/screenshots/recording

<img width="1465" height="715" alt="Image" src="https://github.com/user-attachments/assets/6478e498-fbc3-4393-b25a-44687280b817" />
(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.16.1
  • 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 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-16T17:11:32.359Z

extent analysis

TL;DR

The WebSocket connection to the n8n editor push endpoint is likely experiencing instability due to a timeout or configuration issue, causing it to drop every 2-4 seconds.

Guidance

  • Verify the WebSocket connection timeout settings in the n8n configuration to ensure it is not set too low, which could be causing the connection to drop.
  • Check the server-side logs for any errors or warnings related to WebSocket connections to identify potential issues.
  • Test the WebSocket connection with a different client or tool to isolate if the issue is client-specific or server-side.
  • Review the n8n documentation for any known issues or configuration recommendations related to WebSocket connections.

Example

No code snippet is provided as the issue is more related to configuration and setup.

Notes

The issue seems to be related to the WebSocket connection and not specific to a particular browser, machine, or network, indicating a potential server-side or configuration issue.

Recommendation

Apply workaround: Adjust the WebSocket connection timeout settings in the n8n configuration to a higher value to see if it resolves the issue, as the current setup seems to be causing the connection to drop too frequently.

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