SMTP node "timedout" error

Describe the problem/error/question

Hi n8n team!

I recently migrated my n8n instance(postgresSQL) that was running on Elestio/AWS to my own instance (SQLite) on Hetzner Cloud. I exported the workflows and credentials through CLI.

Almost everything is working except SMTP node, everytime the workflow runs, I got an TIMEDOUT error in the last node.

I already tried to create a new SMTP credential but it get stuck with “Testing” message after saving the credential. All my saved credentials are working just the SMTP node and credentials have this weird behauvior.

Nothing has changed, this began to ocurred after the migration. In my firewall inbound ports 80 and 443 are open, outbound traffic is not restricted.

What is the error message (if any)?

The connection timed out, consider setting the ‘Retry on Fail’ option in the node settings

Please share your workflow

Share the output returned by the last node

{
  "errorMessage": "The connection timed out, consider setting the 'Retry on Fail' option in the node settings",
  "errorDetails": {
    "rawErrorMessage": [
      "Connection timeout",
      "Connection timeout"
    ],
    "httpCode": "ETIMEDOUT"
  },
  "n8nDetails": {
    "nodeName": "Send Email",
    "nodeType": "n8n-nodes-base.emailSend",
    "nodeVersion": 2,
    "resource": "email",
    "operation": "send",
    "time": "8/8/2024, 3:30:00 PM",
    "n8nVersion": "1.53.2 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "NodeApiError: The connection timed out, consider setting the 'Retry on Fail' option in the node settings",
      "    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/EmailSend/v2/send.operation.js:317:19)",
      "    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/EmailSend/v2/EmailSendV2.node.js:91:22)",
      "    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:728:19)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:673:51",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1086:20"
    ]
  }
}

Information on your n8n setup

  • n8n version: 1.53.2
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): IDK
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Easypanel running on Ubuntu 22.04LTS

Hey @rodmontgt,

The message you are getting is a fairly generic network message and it typically means n8n can’t get to the mail server before the connection is closed.

In your case though as you are using Hetzner they actually block outbound traffic on port 465 and you need to open a support case with them to have it unblocked. You can find more details on this here: https://docs.hetzner.com/cloud/servers/faq/#why-can-i-not-send-any-mails-from-my-server

Thank you very much @Jon, I was able to use the port 587, I realized about this firewall blocking one day after my post.

Thanks again!

2 Likes

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