Trial Period - n8n executions not working due to persisting Connection Lost Status

Describe the problem/error/question

I signed up two dasy ago to an n8n trial. I tried following the beginner training and created the first workflow (Hacker News Workflow). Nevertheless, it will not execute as my status is and remains “Connection Lost)

What is the error message (if any)?

Connection Lost. You have a connection issue or the server is down.
n8n should reconnect automatically once the issue is resolved.

Please share your workflow

{
  "nodes": [
    {
      "parameters": {},
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "id": "035cfd07-7c23-44d7-87ad-ec2cdb519ae5",
      "name": "When clicking ‘Execute workflow’"
    },
    {
      "parameters": {
        "resource": "all",
        "limit": 10,
        "additionalFields": {
          "keyword": "automation"
        }
      },
      "type": "n8n-nodes-base.hackerNews",
      "typeVersion": 1,
      "position": [
        208,
        0
      ],
      "id": "1008ae60-72fe-47f7-b008-0f8d51478e7c",
      "name": "Get many items",
      "notesInFlow": true
    }
  ],
  "connections": {
    "When clicking ‘Execute workflow’": {
      "main": [
        [
          {
            "node": "Get many items",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "meta": {
    "templateCredsSetupCompleted": true,
    "instanceId": "f9c074921e5d594997f09c12157c527ad0a9d5e0695614601a2503db6e5f97f0"
  }
}
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.1.4
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud - Trial Period
  • Operating system: Mac Os

What I tried:

  • Login out and back in again, no change
  • Restarting the Workspace: Done. no change
  • Sending a ticket to support. Never received a code to complete the sign-in procedure despite several resend code requests.

I hope you guys can help me though with this.

Hi @Smoke,

I understand your frustration with the persistent “Connection Lost” issue on n8n Cloud. This can be quite challenging during the trial period. Here are some troubleshooting steps:

1. Browser & Network Checks:

  • Try accessing your n8n Cloud instance from a different browser (Chrome, Firefox, Safari)
  • Clear your browser cache and cookies
  • Disable any VPN or proxy that might be interfering with the WebSocket connections
  • Check if your firewall or corporate network is blocking WebSocket connections (n8n Cloud uses WSS for real-time communication)

2. Connection Status:
The “Connection Lost” error typically indicates an issue with the WebSocket connection between your browser and the n8n Cloud server. This can be caused by:

  • Network instability
  • Browser extensions blocking WebSocket connections (try disabling ad blockers)
  • Corporate firewall restrictions

3. Cloud Instance Issues:
Since you’re on n8n Cloud trial (v2.1.4), there might be an infrastructure issue:

  • Check the n8n status page for any ongoing incidents
  • Try accessing your instance URL directly in an incognito/private browsing window

4. Support Ticket Issue:
Regarding the support ticket verification code not arriving:

  • Check your spam/junk folder
  • Try using a different email address if possible
  • You can also reach out to n8n support via their community Discord or tag @n8n-team here

5. Temporary Workaround:
If this is blocking you from trying n8n, consider:

Given that you’ve already restarted the workspace with no success, this might require attention from the n8n support team. I’d recommend:

  1. Trying the browser/network checks above first
  2. Joining the n8n Discord for faster support response
  3. Checking if others are experiencing similar issues on the status page

Hope this helps! Let me know if any of these steps resolve your issue. :slightly_smiling_face:

Hi @hoiyothaheem ,

And thanks a lot for all these options, greatly appreciated. Unfortunately, I am still in the exact same spot as before.

On the same computer, I shut it down completely and restarted it. Launched sessions in FF and Chrome. Connection Lost appears instantly. I do not even see anything else to be honest.

I tried deactivating all the extensions as well as lowering my Browser Security Level to Standard where Strict would be my normal go-to setting. I tried private and incognito windows. No change, still Connection Lost.

I tried on a different computer. The one on the desk right in front of me using the same Wifi connection and a lot of the same settings and apps. n8n works perfectly there, even with extensions such as FB container or Grammarly and DeepL activated.

The cloud instance issues page you gave me leads to a dead page https://status.n8n.io/
But the support bot told me no issues were reported, so …

I’ll hop on Discord to see if I find any other clues on what is happening but it seems to be related to my computer.

Hi @Smoke,

Thanks for the detailed update! This is really helpful. Since n8n works perfectly on your other computer with the same WiFi connection, this clearly narrows it down to something specific on your Mac.

Computer-Specific Troubleshooting:

Since it’s isolated to one machine, here are some Mac-specific things to check:

  1. macOS Firewall/Security Settings:

    • Go to System Settings > Network > Firewall
    • Check if the firewall is blocking WebSocket connections
    • Try temporarily disabling the firewall to test if that’s the culprit
    • Also check System Settings > Privacy & Security for any browser restrictions
  2. Network Settings on that Mac:

    • Go to System Settings > Network > Advanced > DNS
    • Try switching to Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1)
    • Flush DNS cache: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Antivirus/Security Software:

    • Do you have any antivirus or security software installed on this Mac (like Norton, McAfee, Bitdefender, etc.)?
    • These can sometimes interfere with WebSocket connections
    • Try temporarily disabling it to test
  4. Browser Settings Deep Dive:

    • In Chrome/Firefox, check if “Block third-party cookies” is enabled - try disabling it
    • Clear site data completely for your n8n Cloud URL (not just cache)
    • Check if any content blockers or privacy extensions are active
  5. Network Proxy Settings:

    • System Settings > Network > select your connection > Advanced > Proxies
    • Make sure no proxies are configured
  6. MTU Size Issue:

    • Sometimes MTU settings can cause WebSocket issues
    • In Terminal: networksetup -listallhardwareports (find your active connection)
    • Then: networksetup -getMTU <port> to check current MTU
    • If it’s not 1500, you might want to try setting it to 1500

Quick Test:
Open your browser’s Developer Console (Cmd+Option+I in Chrome) when you’re on your n8n Cloud page and check the Console and Network tabs for any specific WebSocket connection errors. Share any errors you see there - they might give us a specific clue.

Alternative Workaround:
While we troubleshoot this, you can continue learning n8n using:

  • The computer where it works perfectly
  • The desktop app on this problematic Mac (it might bypass whatever is blocking the cloud connection)

Let me know what you find, especially any Console errors! We’ll get this sorted out. :+1:

  1. Firewall - I have deactivated it fully and Connection Lost persists in FF and Chrome

  2. I entered the two Google DNs and Cloudflare’s - no change. I then ran the terminal command and no change either. I just did not get a confirmed flush message.

  3. Antivirus is Webroot but is installed on both computers with the same parameters. Anyway I shut it down and issue persists

  4. Set Chrome to accept all cookies, disconnect all extensions, clear all navigation data. Issue persists

  5. No proxies configured

  6. Got an error when running this line networksetup -getMTU <port> Error says: -bash: syntax error near unexpected token `newline’
    I wouldn’t know how to set it to 1500 if need be.

  7. Quick Test : here is a Console Screen Capture
    In network I get several 403s (3 to be exact) See screen capture as well

I can video capture too should it be helpful.

Thanks in advance

Thanks for the incredibly thorough testing! The 403 errors in your Network tab are the breakthrough clue we needed. This tells us that requests ARE reaching n8n Cloud servers, but they’re being actively rejected/blocked by something.

The 403 Forbidden Errors Point To:

Since you’re getting 403s (Forbidden) instead of timeouts or connection refused errors, this means:

  1. Network requests are successfully leaving your Mac
  2. They’re reaching n8n Cloud servers
  3. But something is blocking/rejecting the authenticated connection

This is almost certainly caused by:

Most Likely: macOS Content Filter or Network Extension

MacOS has system-level content filtering that can block WebSocket connections even when the firewall is off.

Check for these:

  1. System Settings → General → Login Items

    • Look for any security/VPN apps in “Allow in Background”
    • Temporarily disable them
  2. Check for MDM/Corporate Profiles:

    • System Settings → Privacy & Security → Profiles
    • Do you have any profiles installed (especially from work/school)?
    • These can enforce content filtering policies
  3. Network Extensions:

    • Open Terminal and run:

      systemextensionsctl list
      
    • Look for any network/security extensions from Webroot or other security software

The MTU Command Fix

You got a syntax error because of the backticks. Here’s the correct sequence:

# First, find your network interface name
networksetup -listallhardwareports

# Look for "Wi-Fi" and note the "Device:" (usually en0 or en1)
# Then check current MTU:
networksetup -getMTU Wi-Fi

# If it's not 1500, set it:
sudo networksetup -setMTU Wi-Fi 1500

Webroot Deeper Investigation

Even though Webroot is shut down, it may have left system-level network filters active:

  1. Check for Webroot kexts/extensions:

    kextstat | grep -i webroot
    
  2. Webroot may have installed network filters that persist even when “disabled”

  3. Try completely uninstalling Webroot temporarily (not just disabling) and test

Advanced Test: Bypass System Network Stack

Let’s see if this is truly a system-level block:

  1. Try n8n Cloud in Safari (different browser = different network handling)

  2. Test with mobile hotspot:

    • Enable hotspot on your phone
    • Connect your Mac to your phone’s hotspot (different network path)
    • Try n8n Cloud
    • If it works on hotspot but not WiFi, it confirms Mac-specific network filtering

The Nuclear Option: Safe Mode

Boot your Mac in Safe Mode (hold Shift during startup):

  • This disables all third-party kernel extensions and system filters
  • If n8n works in Safe Mode, we know it’s a background process/extension causing this

What Those 403s Tell Us

The fact that you’re seeing exactly 3× 403 errors suggests:

  • These are likely WebSocket upgrade attempts being rejected
  • Or authentication tokens being blocked by a content filter
  • The pattern (exactly 3) suggests retry logic

Can you share:

  1. The exact URLs of those 403 requests from Network tab?
  2. Any error messages in the Console tab related to WebSocket or “ws://” or “wss://”?

This will help us pinpoint exactly which connection is being blocked.

Immediate Workaround

While we debug this, use:

  1. The other Mac (where it works)
  2. n8n Desktop App on this Mac - it might bypass the block
  3. Your phone’s hotspot to isolate if it’s WiFi-specific

We’re getting close to the root cause! The 403s are actually good news - they give us a specific error to track down. Let me know the results of the Safe Mode test and those WebSocket error details.

Before running all the new suggestions, a quick note.
In the screen captures I attached, one mentions “DOME Exception: Failed to construct ‘WebSocket’: The URL ‘/rest/push?pushRef=dacbztu0ft’ is invalid.”
I am reattaching the screen capture and pointing to the referred event in case it allows for a rapid solution.

The 3 urls for the 403s are in reality the same url 3 times.

https://o1420875.ingest.us.sentry.io/api/4503960699273216/envelope/?sentry_version=7&sentry_key=3a848d77e104fa41f2735a1d3a1ef8e7&sentry_client=sentry.javascript.vue%2F9.42.1

https://o1420875.ingest.us.sentry.io/api/4503960699273216/envelope/?sentry_version=7&sentry_key=3a848d77e104fa41f2735a1d3a1ef8e7&sentry_client=sentry.javascript.vue%2F9.42.1

https://o1420875.ingest.us.sentry.io/api/4503960699273216/envelope/?sentry_version=7&sentry_key=3a848d77e104fa41f2735a1d3a1ef8e7&sentry_client=sentry.javascript.vue%2F9.42.1

Hey @hoiyothaheem , still with me on this one?

This isn’t caused by the trial itself. A persistent “Connection Lost” status usually means the n8n editor can’t maintain a WebSocket connection to the n8n backend.

Common causes:

  • Running n8n behind a reverse proxy (Nginx, Cloudflare, Hostinger) without WebSocket support

  • Proxy timeouts / buffering enabled

  • Incorrect N8N_HOST, N8N_PROTOCOL, or WEBHOOK_URL

  • Firewall or network blocking WebSockets

Things to check:

  1. Ensure your proxy supports WebSockets (Upgrade + Connection headers)

  2. Disable proxy buffering (e.g. proxy_buffering off;)

  3. Set these env vars correctly:

    N8N_HOST=your-domain
    N8N_PROTOCOL=https
    WEBHOOK_URL=https://your-domain/
    
    
  4. Restart n8n after changes

Once the WebSocket connection is stable, executions will run normally the trial doesn’t limit or block them.

[email protected]

I am sorry but I subscribed to a 14-day trial. I am not an engineer. I am not hosting n8n. I am just connecting with a login and password via a web browser. I am afraid I do not understand most of the language you are using. I have copied above a screen capture with a websocket apparent error but got no feedback on whether this was the issue.

My trial is now less than 2 days away from ending. I have received no support from an email sent to [email protected] and despite doing all that was offered in this thread “connection lost” status has never evolved since January 1st. I am starting to feel that this n8n plug n play marketing image is far from plug leaving play non existing in my limited experience.

Thanks for clarifying that really helps.

If you’re using the 14-day trial and only logging in via the browser, then you’re right: you shouldn’t need to understand hosting, servers, or engineering terms. At that level, “Connection lost” should not be happening, and it’s understandably frustrating especially with the trial almost over.

I can help you with this.

At a high level, what you’re seeing usually means the web app is not able to maintain a live connection to the n8n service, which prevents executions from running even though everything looks set up. You don’t need to change anything technical yourself for me to help diagnose this.

If you’re open to it, you can:

  • Share the workflow (or screenshots)

  • Confirm whether any execution has ever completed

  • Confirm if the issue happens immediately after login or only when running workflows

I’ve helped others unblock similar “connection lost” issues on trial accounts, and I’m happy to walk you through this step-by-step in plain language so you can at least get value before the trial ends.

No pressure just offering help.

Thanks for your help, much appreciated.
I had already exchanged some information about the situation I am facing and performed some tests recommended by @hoiyothaheem the other person kindly assisting in this thread. Yoy may find information of interest regarding my particular situation.

Regarding your questions:

  • I will paste the workflows here below. They are the 2 workflows used as teaching material in n8n level one course.
  • No execution was ever completed on my computer. I have run the longer one once on the computer of a colleague, sitting right across my table.
  • The connection lost message appears even before executing any workflow.

Workflow 1:
{
“nodes”: [
{
“parameters”: {},
“type”: “n8n-nodes-base.manualTrigger”,
“typeVersion”: 1,
“position”: [
0,
0
],
“id”: “035cfd07-7c23-44d7-87ad-ec2cdb519ae5”,
“name”: “When clicking ‘Execute workflow’”
},
{
“parameters”: {
“resource”: “all”,
“limit”: 10,
“additionalFields”: {
“keyword”: “automation”
}
},
“type”: “n8n-nodes-base.hackerNews”,
“typeVersion”: 1,
“position”: [
208,
0
],
“id”: “1008ae60-72fe-47f7-b008-0f8d51478e7c”,
“name”: “Hacker News”,
“notesInFlow”: true
}
],
“connections”: {
“When clicking ‘Execute workflow’”: {
“main”: [
[
{
“node”: “Hacker News”,
“type”: “main”,
“index”: 0
}
]
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “f9c074921e5d594997f09c12157c527ad0a9d5e0695614601a2503db6e5f97f0”
}
}

Workflow 2 :

{
“nodes”: [
{
“parameters”: {
“url”: “https://learn.app.n8n.cloud/webhook/custom-erp”,
“authentication”: “genericCredentialType”,
“genericAuthType”: “httpHeaderAuth”,
“sendHeaders”: true,
“headerParameters”: {
“parameters”: [
{
“name”: “unique_id”,
“value”: “a49f98ff15279f652a023153a6f4fc00”
}
]
},
“options”: {}
},
“type”: “n8n-nodes-base.httpRequest”,
“typeVersion”: 4.3,
“position”: [
224,
0
],
“id”: “2fbf78f9-a49a-4ff0-bfe5-366e8ee3b655”,
“name”: “HTTP Request”,
“credentials”: {
“httpHeaderAuth”: {
“id”: “LYMa3Qrg2lPJvTVN”,
“name”: “Header Auth account”
}
}
},
{
“parameters”: {
“operation”: “create”,
“base”: {
“__rl”: true,
“value”: “appQfnjq5nWiK7oLb”,
“mode”: “list”,
“cachedResultName”: “n8n level 1 course”,
“cachedResultUrl”: “https://airtable.com/appQfnjq5nWiK7oLb”
},
“table”: {
“__rl”: true,
“value”: “tblrXK943C0kqp9CO”,
“mode”: “list”,
“cachedResultName”: “processingOrders”,
“cachedResultUrl”: “https://airtable.com/appQfnjq5nWiK7oLb/tblrXK943C0kqp9CO”
},
“columns”: {
“mappingMode”: “autoMapInputData”,
“value”: {},
“matchingColumns”: ,
“schema”: [
{
“id”: “orderID”,
“displayName”: “orderID”,
“required”: false,
“defaultMatch”: false,
“canBeUsedToMatch”: true,
“display”: true,
“type”: “number”,
“readOnly”: false,
“removed”: false
},
{
“id”: “employeeName”,
“displayName”: “employeeName”,
“required”: false,
“defaultMatch”: false,
“canBeUsedToMatch”: true,
“display”: true,
“type”: “string”,
“readOnly”: false,
“removed”: false
}
],
“attemptToConvertTypes”: false,
“convertFieldsToString”: false
},
“options”: {}
},
“type”: “n8n-nodes-base.airtable”,
“typeVersion”: 2.1,
“position”: [
880,
-128
],
“id”: “565c09aa-4089-4469-a5d7-2aada2a03427”,
“name”: “Create a record”,
“credentials”: {
“airtableTokenApi”: {
“id”: “EvLBK2GT3NzUeFsQ”,
“name”: “Airtable Personal Access Token account”
}
}
},
{
“parameters”: {
“conditions”: {
“options”: {
“caseSensitive”: true,
“leftValue”: “”,
“typeValidation”: “strict”,
“version”: 3
},
“conditions”: [
{
“id”: “7b7db419-9d44-4897-9349-337bc28a20a4”,
“leftValue”: “={{ $json.orderStatus }}”,
“rightValue”: “processing”,
“operator”: {
“type”: “string”,
“operation”: “equals”,
“name”: “filter.operator.equals”
}
}
],
“combinator”: “and”
},
“options”: {}
},
“type”: “n8n-nodes-base.if”,
“typeVersion”: 2.3,
“position”: [
448,
0
],
“id”: “78a32255-27fa-449b-afe3-346cb41adbc6”,
“name”: “If”
},
{
“parameters”: {
“assignments”: {
“assignments”: [
{
“id”: “0becb8a2-a3e7-4c36-9ce8-32a7349e4f38”,
“name”: “orderID”,
“value”: “={{ $json.orderID }}”,
“type”: “number”
},
{
“id”: “cb8f90c9-e4b2-4bdf-b759-f68a0d9d3724”,
“name”: “employeeName”,
“value”: “={{ $json.employeeName }}”,
“type”: “string”
}
]
},
“options”: {}
},
“type”: “n8n-nodes-base.set”,
“typeVersion”: 3.4,
“position”: [
672,
-128
],
“id”: “518124f1-811e-4f35-885e-6ff3c6123558”,
“name”: “Edit Fields”
},
{
“parameters”: {
“jsCode”: “let items = $input.all();\nlet totalBooked = items.length;\nlet bookedSum = 0;\n\nfor (let i=0; i < items.length; i++) {\n bookedSum = bookedSum + items[i].json.orderPrice;\n}\n\nreturn [{ json: {totalBooked, bookedSum} }];”
},
“type”: “n8n-nodes-base.code”,
“typeVersion”: 2,
“position”: [
656,
96
],
“id”: “29642ec0-f9f5-49c3-887b-1bb404d24dca”,
“name”: “Code in JavaScript”
},
{
“parameters”: {
“authentication”: “webhook”,
“content”: “=This week we’ve {{$json[“totalBooked”]}} booked orders with a total value of {{$json[“bookedSum”]}}. My Unique ID: {{ $(‘HTTP Request’).params[“headerParameters”][“parameters”][0][“value”] }}”,
“options”: {}
},
“type”: “n8n-nodes-base.discord”,
“typeVersion”: 2,
“position”: [
864,
96
],
“id”: “7a577297-8b8a-4477-a5f4-8c27445d4ffb”,
“name”: “Discord”,
“webhookId”: “d3451e27-f9c4-4da5-90ca-813e37c28813”,
“credentials”: {
“discordWebhookApi”: {
“id”: “pw6AALHIKOf1jcnO”,
“name”: “Discord Webhook account”
}
}
},
{
“parameters”: {
“rule”: {
“interval”: [
{
“field”: “weeks”,
“triggerAtDay”: [
1
],
“triggerAtHour”: 9
}
]
}
},
“type”: “n8n-nodes-base.scheduleTrigger”,
“typeVersion”: 1.3,
“position”: [
32,
0
],
“id”: “62bee414-4296-4797-a84e-bc7cba07224c”,
“name”: “Schedule Trigger”
}
],
“connections”: {
“HTTP Request”: {
“main”: [
[
{
“node”: “If”,
“type”: “main”,
“index”: 0
}
]
]
},
“If”: {
“main”: [
[
{
“node”: “Edit Fields”,
“type”: “main”,
“index”: 0
}
],
[
{
“node”: “Code in JavaScript”,
“type”: “main”,
“index”: 0
}
]
]
},
“Edit Fields”: {
“main”: [
[
{
“node”: “Create a record”,
“type”: “main”,
“index”: 0
}
]
]
},
“Code in JavaScript”: {
“main”: [
[
{
“node”: “Discord”,
“type”: “main”,
“index”: 0
}
]
]
},
“Schedule Trigger”: {
“main”: [
[
{
“node”: “HTTP Request”,
“type”: “main”,
“index”: 0
}
]
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “f9c074921e5d594997f09c12157c527ad0a9d5e0695614601a2503db6e5f97f0”
}
}