Connectivity problems with n8n

Questions
1

Describe the problem/error/question

I’m having some troubles in my n8n with the saving and test step. cuando estoy empezando a crear el flujo y coloco el api de mi plataforma a conectar (kommo crm) yo presiono sobre el “test step” y sale un error abajo que dice “lost connection to the server” and the workflow also appears “Connection lost.”

What is the error message (if any)?

“lost connection to the server” and the workflow also appears “Connection lost.”

Please share your workflow

(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.)

{
“nodes”: [
{
“parameters”: {},
“type”: “n8n-nodes-base.manualTrigger”,
“typeVersion”: 1,
“position”: [
0,
0
],
“id”: “0874a911-a2ed-4518-b857-ab21e8befc9d”,
“name”: “When clicking ‘Test workflow’”
}
],
“connections”: {
“When clicking ‘Test workflow’”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“instanceId”: “fb74efb3ed87f2ccb6bea3a34fd82cfdc3c900c09d58e25d0ecc086550bc35b6”
}
}

image_48
image_48858×675 113 KB

Information on your n8n setup

  • n8n version: 1.80.5
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

maibe its important to clarify that I have N8N installed on my local server, and go to the Internet through Cloudflare Zero Trust Tunnel

3

Hi, I have the same problem on my cloud server on hetzner:

Information on your n8n setup

  • n8n version: 1.81.4
  • Database (default: SQLite): Sqlite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux

I solved it: in nginx conf I added:
# Abilita WebSocket
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “Upgrade”;
proxy_http_version 1.1;

1 Like
4

so, the problem would be in the Nginx Ok … thanks I will do it and notify if there was any change

5

thanks the problem was the nginx and its solved

6

Great that it solved your issue. Can you please mark the reply with the solution as the solution as well. :slightly_smiling_face:

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.