I am repeatedly getting the “connection lost” warning and can not access any workflows. This has never happened before. I have tried logging out and logging back in. I am not running a VPN.
n8n version 1.8.2
running from Chrome browser
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Hi @pmg
We would need more info on your setup for this one.
Probably an issue with websocket support not being configured correctly.
What other information can I provide to help you debug this as soon as possible?
are you running n8n behind a reverse-proxy? if yes, which one.
I have been informed this is impacting multiple users on our account. I’m not sure if we are running n8n behind a reverse proxy - how can I determine this? I do not think we are but can’t confirm-
are you self-hosting, or using a cloud instance?
If self-hosting, maybe check with whoever deployed n8n if they setup something like nginx, traefik, or caddy along with n8n.
Usually the Connection lost error comes from something between the browser and the n8n server terminating the Websocket connection. This is usually a reverse-proxy, but sometimes it’s also a corporate forward-proxy.
If you don’t have a reverse-proxy setup, and if you have an IT team, please check with them if you have a proxy that all requests go through.
2 Likes
Ok, there isn’t any proxy between the N8N and the endpoint in question
What endpoint?
It is about a reverse proxy between the user and n8n.
Sorry, my colleague misunderstood what has happening. An update: “You are using their service and are unable to access it even though you are connected directly to the internet”
To confirm, I am accessing n8n using your service/website. This morning, one of our users was was running a long-standing workflow (2 hours) and this is when connection issues were discovered for all users.
Sounds like you are using the cloud.
We made some changes on the cloud reverse-proxy 5 hours ago, so this is likely related to it.
We are investigating now.
2 Likes
Next time please give the details the bot has asked you for. The fact that you are using n8n cloud is a very important detail 
4 Likes
Thanks for letting me know! I’ll be sure to log this for future reference. And thank you all for your help.
Can you please check if you are still seeing the issue?
2 Likes
About 10-15 minutes ago, we updated to the newest n8n version (1.36.1) so not sure if that is relevant. But yes, the “connection lost” error has stopped! Thank you!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.