Dear Railway Support Team,

I am running an n8n instance (N8N (w/ webhook processors) template) on Railway, and I am encountering a persistent issue with outbound network connectivity specifically to the Telegram API.

My n8n workflow attempts to send messages to https://api.telegram.org/, but consistently fails with the following error:

json

{
  "errorMessage": "The connection was aborted, perhaps the server is offline",
  "errorDetails": {
    "rawErrorMessage": [
      "timeout of 5000ms exceeded",
      "timeout of 5000ms exceeded"
    ],
    "httpCode": "ECONNABORTED"
  },
  "n8nDetails": {
    "nodeName": "HTTP Request", // or your Telegram node name
    "nodeType": "n8n-nodes-base.httpRequest", // or n8n-nodes-base.telegram
    // ... rest of the n8nDetails ...
  }
}

Key Observation: To diagnose the issue, I performed an internal network test using n8n's HTTP Request node from within the n8n container:

• Connecting to https://www.google.com/ was successful (returned status code 200).

• Connecting to https://api.telegram.org/ (IP: 149.154.167.220:443) consistently results in the ECONNABORTED / timeout error.

This indicates that my n8n container has general outbound internet access, particularly over HTTPS (port 443). However, there appears to be a specific connectivity issue or blockage between my Railway hosted n8n service and Telegram's API servers.

I have already verified that:

• There are no HTTP_PROXY, HTTPS_PROXY, or NO_PROXY environment variables configured on my Primary or Webhook processor services.

• The WEBHOOK_URL for my Primary service is correctly set to the public domain of the Webhook processor.

• The N8N_BACKEND_TRUST_PROXY variable is set to true.

My Railway project ID is [048e4a86-372b-48e0-85ee-daf78135a280]. The affected service (where n8n runs/makes outbound calls) is primary, webhook processor, worker.

Could you please investigate if there are any network routing issues, firewall rules, or specific blocks on Railway's infrastructure that could be preventing successful outbound connections from my container to api.telegram.org (specifically 149.154.167.220:443)?

Thank you for your time and assistance.

This is error log on n8n

{

"errorMessage": "The connection was aborted, perhaps the server is offline",

"errorDetails": {

"rawErrorMessage": [

"timeout of 5000ms exceeded",

"timeout of 5000ms exceeded"

],

"httpCode": "ECONNABORTED"

},

"n8nDetails": {

"nodeName": "HTTP Request",

"nodeType": "n8n-nodes-base.httpRequest",

"nodeVersion": 4.3,

"itemIndex": 0,

"time": "2025. 12. 31. 오전 11:29:01",

"n8nVersion": "2.1.4 (Self Hosted)",

"binaryDataMode": "database",

"stackTrace": [

"NodeApiError: The connection was aborted, perhaps the server is offline",

" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:859:16)",

" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8)",

" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1226:11)",

" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1662:27",

" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2274:11"

]

}

}