Issue Station
Sign In
Tools hereToolbox

n8n - ✅(Solved) Fix Connection Lost [1 pull requests, 6 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#28850•Fetched 2026-04-23 07:44:24
View on GitHub
Comments
6
Participants
4
Timeline
16
Reactions
0
Author
makingweb-datamakingweb-data
Participants
JonnyPowerJonnyPowermakingweb-datamakingweb-datan8n-assistant[bot]n8n-assistant[bot]sameershamim24sameershamim24
Timeline (top)
commented ×6subscribed ×5cross-referenced ×2mentioned ×2

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Fix Action

Fixed

PR fix notes

PR #27665: fix(core): Fix /healthz endpoint when using N8N_PATH

Description (problem / solution / changelog)

Summary

Fixes an issue introduced in #26129 that caused /healtz endpoint to point to wrong location when using N8N_PATH env variable and reverse proxy setup.|

This PR introduces two methods that resolve health endpoint location separately:

  • resolveBackendHealthEndpointPath() - always returns the bare health endpoint (e.g. /healthz)
  • resolveFrontendHealthEndpointPath() - prepends N8N_PATH with path.posix.join() for proper slash normalization

Related Linear tickets, Github issues, and Community forum posts

Fixes ADO-5016 Fixes 26930

Review / Merge checklist

  • PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
  • Docs updated or follow-up ticket created.
  • Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)

Changed files

  • packages/cli/src/abstract-server.ts (modified, +2/-2)
  • packages/cli/src/commands/base-command.ts (modified, +2/-2)
  • packages/cli/src/scaling/worker-server.ts (modified, +2/-2)
  • packages/cli/src/services/__tests__/frontend.service.test.ts (modified, +2/-2)
  • packages/cli/src/services/frontend.service.ts (modified, +2/-2)
  • packages/cli/src/utils/health-endpoint.util.ts (modified, +16/-4)
  • packages/cli/test/integration/shared/utils/test-server.ts (modified, +2/-2)
  • packages/cli/test/unit/utils/health-endpoint.util.test.ts (modified, +64/-36)
  • packages/frontend/editor-ui/src/app/composables/useBackendStatus.spec.ts (modified, +4/-1)
  • packages/frontend/editor-ui/src/app/composables/useBackendStatus.ts (modified, +3/-1)

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

"Connection Lost" is flashing on/off for all workflows. Workflows will not complete due to issue.

What is the error message (if any)?

"Connection Lost"

Please share your workflow/screenshots/recording

<img width="1506" height="310" alt="Image" src="https://github.com/user-attachments/assets/2f20c9e2-5612-47aa-a9f5-20245e1057be" /> <img width="1615" height="684" alt="Image" src="https://github.com/user-attachments/assets/fc23c965-05c8-449f-86ba-2e89f067d499" /> 
(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. -->

Not available

Debug info

core

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

storage

  • success: none
  • error: all
  • progress: false
  • manual: false
  • 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-22T05:49:44.796Z

extent analysis

TL;DR

The "Connection Lost" issue in n8n workflows may be related to configuration or resource limitations, and checking the database and execution mode settings could help resolve the issue.

Guidance

  • Review the n8nVersion and nodeJsVersion to ensure compatibility and consider updating if necessary.
  • Check the concurrency setting, which is set to 50, and consider reducing it to prevent overloading the system.
  • Investigate the database setting, which is set to sqlite, and consider optimizing or upgrading the database for better performance.
  • Examine the pruning settings to ensure that old executions are being properly removed and not causing resource issues.

Example

No specific code example is provided, but reviewing the n8n configuration files and adjusting settings as needed may help resolve the issue.

Notes

The provided information suggests that the issue may be related to resource limitations or configuration settings, but further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Reduce the concurrency setting to a lower value, such as 10 or 20, to prevent overloading the system and see if it resolves the issue. This change can help mitigate the problem 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…
#api#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

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

Back to top recommendations

TRENDING