n8n-io
"Connection lost" in self-hosted deployment
Bug Description
This change has broken my self-hosted instance: #15006
Since recent version update I'm getting recurring "Connection lost" message displayed in the UI and the only thing printed in the server logs repeatedly is this:
Origin header does NOT match the expected origin. (Origin: "https://xyz.com", Expected: "wss://xyz.com")
Not sure how to debug the issue tbh.
To Reproduce
Just updated self-hosted instance to 1.95.1. Managing my server with Dokploy with Cloudflare CDN as a proxy.
Expected behavior
Should connect normally.
Operating System
Ubuntu
n8n Version
1.95.1
Node.js Version
20.19.2
Database
PostgreSQL
Execution mode
main (default)
Hey @imajus,
We have created an internal ticket to look into this which we will be tracking as "GHC-2191"
@Joffcom same here:
Scenario:
N8N in Queue, with the N8N Editor at one address and the webhook at another address. There is an intermittent Connection Lost message.
This message appears in the Editor container log:
Browser log:
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.