Skip to content

Conection Lost 1.95.2 #15897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fabiocavalcantti opened this issue Jun 1, 2025 · 4 comments
Closed

Conection Lost 1.95.2 #15897

fabiocavalcantti opened this issue Jun 1, 2025 · 4 comments
Labels
in linear Issue or PR has been created in Linear for internal review

Comments

@fabiocavalcantti
Copy link

Bug Description

Image

Bug Report: Intermittent "Connection lost" errors in n8n v1.95.2

Describe the bug

I am experiencing frequent and intermittent "Connection lost" errors while using n8n version 1.95.2. This issue occurs randomly and makes it very difficult to work on workflows.

Impact

This issue is significantly impacting productivity by:

  • Preventing the saving of work, leading to potential data loss.
  • Making it difficult to activate or deactivate workflows reliably.
  • Causing frustration and delays in workflow development and management.

To Reproduce

Steps to reproduce

It's hard to provide exact steps to reproduce due to the intermittent nature of the bug. However, the "Connection lost" error typically appears when:

  1. Editing nodes within a workflow.
  2. Attempting to save a workflow.
  3. Trying to activate or deactivate a workflow.
  4. Navigating between different workflows or an n8n sections.
    The connection will drop and then usually reconnect after a few moments, but the interruption is disruptive.

Expected behavior

Actual behavior

The n8n interface frequently displays a "Connection lost" message (similar to the attached image, though the image shows a generic connection lost message, the in-app n8n message is specific to the UI). This prevents saving changes, activating/deactivating workflows, and generally disrupts the workflow editing process. This requires frequent manual retries to save or activate, significantly slowing down development and operations.

Operating System

Unbuntu 22.04

n8n Version

1.95.2

Node.js Version

Docker Image

Database

PostgreSQL

Execution mode

queue

@Joffcom
Copy link
Member

Joffcom commented Jun 1, 2025

Hey @fabiocavalcantti,

We have created an internal ticket to look into this which we will be tracking as "GHC-2288"

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Jun 1, 2025
@Joffcom
Copy link
Member

Joffcom commented Jun 2, 2025

Hey @fabiocavalcantti,

Thank you for bringing this up! It looks like this issue is a duplicate of #15706, where we’re already tracking progress and updates. To keep things organized, we’ll close this issue and continue the discussion over there.

If you have any additional details or context that might help, please feel free to add them to the original issue. Your input is always appreciated!

Thanks again for your contribution, and let us know if there’s anything else we can assist with.

This will be fixed in todays release.

@Joffcom Joffcom closed this as completed Jun 2, 2025
@ngi-oss
Copy link

ngi-oss commented Jun 3, 2025

Hi, I updated to 1.95.2 recently (10mins ago) and now I got the issue of a lost connection.
Self hosted N8N on hetzner with coolify. Docker and overall health check is ok. Log tells: .. " expecting wss:// ... "
Backend in N8n is working, but all workflows are broken at the moment with the message:

Image

Any news on this?
Thanks

@dbfun
Copy link

dbfun commented Jun 3, 2025

How can I downgrade to a working version? Currently, the Docker Compose file uses image: docker.n8n.io/n8nio/n8n.

I'm experiencing the issue with Traefik. Will switching to Nginx or Caddy solve the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review
Projects
None yet
Development

No branches or pull requests

4 participants