n8n - 💡(How to fix) Fix SERVER DISCONNECTING [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#29008Fetched 2026-04-24 06:12:45
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
subscribed ×2commented ×1labeled ×1mentioned ×1

Error Message

Describe the problem/error/question

The n8n instance keeps disconnecting from the n8n frontend every 2-3 seconds and reconnecting, and if i try to run a workflow at the time when it is disconnected, it gives error

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

The n8n instance keeps disconnecting from the n8n frontend every 2-3 seconds and reconnecting, and if i try to run a workflow at the time when it is disconnected, it gives error

What is the error message (if any)?

Connection Lost at the top AND : could not connect to sever - when i try to run a workflow

Please share your workflow/screenshots/recording

(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 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-23T15:18:13.720Z

extent analysis

TL;DR

The n8n instance's frequent disconnections from the frontend may be related to configuration or environmental issues, and a workaround could involve adjusting settings or checking the infrastructure.

Guidance

  • Check the Docker container's resource allocation and adjust as needed to prevent potential resource exhaustion.
  • Verify the network connectivity and stability between the n8n instance and the frontend.
  • Review the n8n configuration, particularly the concurrency setting, which is currently set to 20, and consider adjusting it to a lower value to reduce the load on the system.
  • Investigate potential issues with the SQLite database, such as connection timeouts or query performance, which could be contributing to the disconnections.

Notes

The provided information does not include specific error logs or detailed system metrics, which would be helpful in pinpointing the root cause of the issue. Additionally, the fact that the issue occurs every 2-3 seconds suggests a periodic or recurring problem, which may be related to a specific system process or timer.

Recommendation

Apply workaround: Adjust the concurrency setting to a lower value, such as 5-10, to reduce the system load and observe if the disconnections persist. This change can help mitigate the issue while further investigation is conducted.

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