Mysql node excutes for too long than we have the following error Connection lost: The server closed the connection. sql: undefined, code: PROTOCOL_CONNECTION_LOST

[Chaima_Belkacem]

here is the error details

{
  "errorMessage": "Connection lost: The server closed the connection.",
  "errorDescription": "sql: undefined, code: PROTOCOL_CONNECTION_LOST",
  "errorDetails": {},
  "n8nDetails": {
    "nodeName": "MySQL",
    "nodeType": "n8n-nodes-base.mySql",
    "nodeVersion": 2.4,
    "resource": "database",
    "operation": "executeQuery",
    "itemIndex": 0,
    "time": "30/10/2024, 15:56:04",
    "n8nVersion": "1.61.0 (Self Hosted)",
    "binaryDataMode": "filesystem",
    "stackTrace": [
      "NodeOperationError: Connection lost: The server closed the connection.",
      "    at Object.parseMySqlError (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/MySql/v2/helpers/utils.js:80:12)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/MySql/v2/helpers/utils.js:189:47",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/MySql/v2/actions/database/executeQuery.operation.js:64:18)",
      "    at Object.router (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/MySql/v2/actions/router.js:48:30)",
      "    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/MySql/v2/MySqlV2.node.js:16:16)",
      "    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:722:19)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:711:51",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1141:20"
    ]
  }
}

( i can’t communicate the query since it’s confidential ) .
PS : We are running on a selfhosted instance and Before the latest update we did 1 month ago, it was working fine.

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[Chaima_Belkacem]

Hello , Thank you for your quick response.
We have resolved the issue on our end. It is related to the browser when we switched to private navigator it worked fine. But it’s better to be investigated if this happens again in the future . Please reach out if any further info is needed for your investigation

[Jon]

Hey @Chaima_Belkacem,

That is good to hear, I am not sure why the browser would cause that error as the query would be ran on the backend but it is still interesting to know.