HTTP Request / Lead Generation

Questions
,
1

Screenshot (66)
Screenshot (66)1920×1080 138 KB

Screenshot (65)
Screenshot (65)1920×1080 232 KB

Describe the problem/error/question

One of the workflows that I am using for lead generation ,the HTTP Request node gives me an error like this: “Connection was aborted, perhaps the server is offline”. What is the solution for this ?

What is the error message (if any)?

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

Share the output returned by the last node

Information on your n8n setup

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

@Kuti01 The error message “The connection was aborted, perhaps the server is offline” usually means that n8n was unable to reach the target server.

3

That error almost always means one of a few things. Here’s how to narrow it down fast:

1. The target server is blocking automated requests
Lead scraping/gen APIs often rate-limit or block based on headers. Add these to your HTTP node:

  • User-Agent: Mozilla/5.0 (compatible; n8n-automation/1.0)
  • Accept: application/json

2. No retry on transient failures
The connection drops mid-request and n8n doesn’t retry by default. Enable retry in the HTTP node Options tab — set “Retry On Fail” to 3 retries with a 2000ms wait. For batch lead workflows this alone fixes ~80% of aborted connection errors.

3. Timeout too short
Default timeout is 10s. If the server is slow or the payload is large, increase it in the HTTP node Options to 30-60 seconds.

4. SSL/TLS mismatch
If you’re hitting an HTTP (not HTTPS) endpoint or an endpoint with a self-signed cert, toggle “Ignore SSL Issues” in the node settings.

Quick diagnostic: test the exact URL in a browser or with curl -v [url] on your n8n server to confirm it’s reachable from that network. If curl works but n8n fails, it’s almost always a header or timeout issue.

What’s the target domain/API you’re hitting? That would help narrow it down further.