you have a connection issue or server is down. n8n should reconnect once the issue is resloved #185215
Replies: 1 comment
-
|
Hey there, "Connection lost" issue with n8n in Codespaces , It usually happens because the Codespace environment doesn't forward the WebSocket connection correctly by default, or n8n doesn't know its own public URL. Here is the fix that worked for me:
Go to the Ports tab in your Codespace (bottom panel near the terminal). Find port 5678 (or whichever port n8n is running on). Right-click it and change Port Visibility to Public. Why? If it's set to "Private," the authentication cookies sometimes interfere with the WebSocket connection n8n uses to update the UI.
The Problem: If you use the public URL, the request goes out to the internet and hits the GitHub Codespace authentication wall (which returns a 403 or Login page), causing the node to fail. The Fix: Use the local Docker network address. In your HTTP Request node, set the URL to: http://localhost: (e.g., http://localhost:3000) or http://127.0.0.1: This keeps the traffic internal and bypasses the public auth checks. Hope this gets your workflow running! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
i have installed n8n in GitHub codespaces, i have create a simple html web app on same codespace
now i want to monitor this web app using n8n
while configuring im getting connection lost
i have added screenshot below
Beta Was this translation helpful? Give feedback.
All reactions