Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix n8n Editor WebSocket Reconnects Every ~2 Seconds on ARM64 [2 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#29032•Fetched 2026-04-24 10:43:18
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
luckychu119luckychu119
Participants
luckychu119luckychu119n8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×2labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Root Cause

Root Cause (Hypothesis — Unconfirmed) Server-side debug logging (N8N_LOG_LEVEL=debug) shows the same pushRef calling Add editor-UI session exactly every 2 seconds, with no corresponding Removed editor-UI session log. The server never explicitly closes the connection.

RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

Title: n8n Editor WebSocket Reconnects Every ~2 Seconds on ARM64

Environment

  • Server: Oracle Cloud ARM64 A1.Flex (4 core, 23 GB RAM)
  • n8n version: 2.17.5 (Docker docker.n8n.io/n8nio/n8n:2.17.5)
  • Mode: Queue (3 workers, concurrency 40)
  • Access: Cloudflare Tunnel (arm.medicontentslab.com) + Zero Trust

Symptoms

  • A "Connection lost" banner flashes every ~2 seconds in the n8n editor UI.
  • The "Execute Workflow" button works, but there is a ~2-second response lag that matches the reconnection cycle.
  • Scheduled/queue workflow executions are completely unaffected.
  • The issue persists regardless of the browser, network, or the number of tabs open.

What Was Ruled Out

HypothesisTestResult
Cloudflare Tunnel / Zero TrustSSH local port-forward bypass (-L 5679:localhost:5678)❌ Issue persists
N8N_PUSH_BACKEND=sseChanged setting, restarted❌ Cloudflare buffers SSE; complete failure
N8N_RUNNERS_ENABLEDSet to false❌ No change
PostgreSQL connection exhaustionpg_stat_activity count❌ 15/150 connections used
High CPU / event loop blockingdocker stats, execution rate❌ CPU ~0.5%, 1 exec per 4 min
Node.js version differenceCompared with x86 server (H3)❌ Both v24.14.1
cloudflared protocol/versionCompared H3 config❌ Both cloudflared:latest --protocol http2
Multi-tab cascade loopClosed all but one tab❌ Issue persists with single tab
Stale execution recovery broadcastsDB query for running/crashed executions❌ 0 running/new executions

Root Cause (Hypothesis — Unconfirmed) Server-side debug logging (N8N_LOG_LEVEL=debug) shows the same pushRef calling Add editor-UI session exactly every 2 seconds, with no corresponding Removed editor-UI session log. The server never explicitly closes the connection.

Source analysis of the frontend bundle (pushConnection.store-DEk_ymyD.js, usePushConnection-Cx7SjRqY.js):

  1. Queue mode polls worker status every 1 second via setInterval(..., 1000).
  2. This triggers Pinia store updates, which may cause a Vue component holding the push connection to unmount/remount.
  3. On remount: pushDisconnect() + pushConnect() → WebSocket closes and reopens.
  4. Reconnect backoff on the first attempt is 1 second (Math.min(1000 * 2^0, 15000)).
  5. Total cycle: ~1s (connection lifetime) + ~1s (backoff) = 2 seconds ✓

Why only ARM64? On x86 servers (H3, H1, etc.) using the same n8n version and Queue mode, the worker status API responds faster, so the reactive update is timing-safe and the component does not remount.

What is the error message (if any)?

  • UI: "Connection lost" banner flashing continuously.
  • Server Logs (N8N_LOG_LEVEL=debug): Continuous Add editor-UI session logs for the exact same pushRef every 2 seconds, without any Removed editor-UI session logs.

Please share your workflow/screenshots/recording

The attached recording

Share the output returned by the last node

(Not applicable)

Debug info

core

  • n8nVersion: 2.17.5
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: scaling (single-main)
  • concurrency: -1
  • license: enterprise (production)

storage

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

pruning

  • enabled: true
  • maxAge: 72 hours
  • maxCount: 10000 executions

https://github.com/user-attachments/assets/d8b043b2-3b61-4dad-a25a-362f1a9f8e39

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-24T03:51:50.100Z

extent analysis

TL;DR

The n8n Editor WebSocket reconnects every ~2 seconds on ARM64 due to a timing issue with the Queue mode and Pinia store updates, causing the WebSocket to close and reopen.

Guidance

  • Investigate the setInterval function in the frontend bundle (pushConnection.store-DEk_ymyD.js, usePushConnection-Cx7SjRqY.js) to see if the polling interval can be adjusted to prevent the WebSocket from closing and reopening.
  • Consider increasing the reconnect backoff time to reduce the frequency of reconnects.
  • Review the server-side debug logs to confirm that the Add editor-UI session logs are indeed causing the reconnects.
  • Test the application on a different architecture (e.g., x86) to confirm that the issue is specific to ARM64.

Example

No code snippet is provided as the issue is related to the interaction between the frontend and backend, and modifying the code without further investigation may not yield the desired results.

Notes

The issue seems to be specific to ARM64 architecture, and the same n8n version and Queue mode do not exhibit this behavior on x86 servers. Further investigation is needed to determine the root cause and develop a permanent fix.

Recommendation

Apply a workaround by adjusting the polling interval or reconnect backoff time to reduce the frequency of reconnects, as the root cause of the issue is not fully understood and may require further investigation.

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…
#api#API routing#API middleware#SSR setup#ISR setup

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 n8n Editor WebSocket Reconnects Every ~2 Seconds on ARM64 [2 comments, 2 participants]