CONNECTION LOST

[MKS-5]

Bug Description

When open a workflow, the system could not connect with the server and get a "conncetion lost" mensage

To Reproduce

1. workflow

Expected behavior

lost connection

Operating System

google cloud

n8n Version

1.88.0

Node.js Version

nd

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @MKS-5,

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

[Shlashzeid]

Bug Description

When open a workflow, the system could not connect with the server and get a "conncetion lost" mensage

To Reproduce

1. workflow

Expected behavior

lost connection

Operating System

google cloud

n8n Version

1.88.0

Node.js Version

nd

Database

SQLite (default)

Execution mode

main (default)

[Shlashzeid]

Bug Description

When open a workflow, the system could not connect with the server and get a "conncetion lost" mensage

To Reproduce

1. workflow

Expected behavior

lost connection

Operating System

google cloud

n8n Version

1.88.0

Node.js Version

nd

Database

SQLite (default)

Execution mode

main (default)

[MKS-5]

*MAIN PROBLEM
I just updated to 1.88.0 version, and a "LOST CONNECTON" error occurs when i try to execute a workflow.

[ffMathy]

This happens only when connecting via a local address that is HTTP. Over an external address that's HTTPs, it seems to work fine. Using Edge.

[MKS-5]

I've updated to the latest version, 1.89, and the same connection loss error continues. I've reverted to version 1.86, and it works correctly in this version. Any clues as to what the problem might be?

[ffMathy]

Not sure. It fixed the problem for me. What's your config like?

[oumaymaabdelkefi]

Did you check your browser console ?
I’m thinking this might be related to WebSocket communication changes in the newer version.

[rialco]

Hey! I am also getting this error in the latest update. The difference is I am using traefik for my reverse proxy.

I tried setting the header like so:

"traefik.http.middlewares.n8n-origin.headers.customrequestheaders.Origin=https://${DOMAIN_NAME}" # Changed name for clarity
its not working though.. still I am getting the websocket error and the invalid origin response.

Anyone else managed to fix it with traefik as the reverse proxy?

[Jorgeruiz97]

Hello - I started having the same issue after upgrading from 1.94.1 -> 1.95.2, it is related to websockets.

my logs constantly show this:
Origin header does NOT match the expected origin. (Origin: "https://n8n.mydomain.com", Expected: "wss://n8n.mydomain.com")

[abelfodil]

I have the same error. I am running behind traefik as well.

I downgraded to 1.93.0 for now.