After the redeploy, n8n is running but the editor can’t keep its push connection, so it shows “Lost Connection”. On Railway you need to set the real public URL and push settings explicitly. In your n8n service, set N8N_EDITOR_BASE_URL, WEBHOOK_URL, N8N_HOST, and N8N_PROTOCOL to match your https://<service>.up.railway.app URL, and if you use Redis workers, switch the Redis host/port to the PRIVATE variants. Then redeploy. If it still happens, add N8NPUSH_BACKEND=websocket (or sse) and redeploy again. That usually fixes the “Lost Connection” issue after updates on Railway.