I’m facing persistent issues with n8n across multiple environments (n8n Cloud, Railway-hosted, and local self-hosted). I have tried many fixes, including updating n8n, running locally, and creating new workspaces, but the problems persist. The main issues are:
1\. **Workflow editor continuously loading** – The editor never fully loads, and I cannot access my existing workflows. Each reload forces me to start a new workflow from scratch.
2\. **Loss of connection to server** – Testing nodes or triggers often fails due to a lost connection error.
What is the error message (if any)?
• WebSocket connection fails with invalid URL: /rest/push?pushRef=...
• “Lost connection to server” when testing a node or event
Please share your workflow
I’m unable to fully open workflows due to the loading issue, so I cannot copy/paste the canvas.
Share the output returned by the last node
Not applicable because I cannot successfully run nodes due to connection issues.
Information on your n8n setup
• n8n version: Latest on n8n Cloud / Railway-hosted / local npm install
• Database (default: SQLite): Default SQLite
• n8n EXECUTIONS_PROCESS setting (default: own, main): Own
• Running n8n via: n8n Cloud, Railway-hosted, local npm install
• Operating system: Windows 10
The fact that the problem exists across local, cloud, and railway instances strongly indicates a persistent issue with your browser and local network configuration, rather than a problem with the n8n instances themselves.
Thank you for your message. I tested n8n in Edge and can confirm that the issues are related to my browser. I was previously using Chrome.
Right now I’m still on Chrome, but I plan to either reset its settings, clear cache, or reinstall it to see if that resolves the problem. If you have any suggestions for browser configurations or steps that usually fix this kind of persistent loading and connection issue, I’d really appreciate your guidance.
I tried all three fixes: resetting Chrome’s settings, clearing the cache, and reinstalling, but none worked. I ran into issues while reinstalling, and it has been problematic for me in the past, so I will stick with Edge for now while using n8n.