Encountering Axios ‘socket hang up’ Error on API Calls After n8n Update

Below is some guidance to help troubleshoot and work around the error:

What “socket hang up” Means

The error indicates that the connection was unexpectedly closed (“reset”) while waiting for a response. In a Node.js context, this is often reported as an ECONNRESET error. It may originate on the server side (or any intermediary such as a reverse proxy) or be caused by network issues.

Possible Causes

• Service-Side Issues or Rate Limiting:
  The remote API may be receiving too many requests or taking too long to respond. If the service enforces rate limits or terminates idle connections, the connection might be dropped.

• Network or Proxy Configuration:
  If you’re running n8n behind a reverse proxy (or similar setups), ensure that the proxy configuration allows for long-lived connections (or supports websockets if needed). Misconfigurations (including TLS/SSL issues) can lead to dropped connections.

• Timeouts or Resource Limitations:
  If the API call takes longer than expected—perhaps due to large payloads or slow responses—the connection might get reset. In some cases, issues like low memory (especially on self-hosted setups) can also contribute to sporadic connection failures.

Potential Workarounds

• Enable Retry on Fail:
  In the HTTP Request node’s settings, enable the Retry on Fail option along with settings for Max Tries and Wait Between Tries (ms). This can help mitigate transient network issues by retrying the failed request.

  JSONCopied
  {
      "settings": {
          "retryOnFail": true,
          "maxTries": 3,
          "waitBetweenTries": 1000
      }
  }

• Use Batching:
  If you suspect that sending too many requests rapidly is the problem, consider using the built-in Batching option for the HTTP Request node. Reduce the number of simultaneous requests and introduce a delay between batches.

  1. In your HTTP Request node, select Add Option > Batching.
  2. Specify Items per Batch.
  3. Set an appropriate Batch Interval (ms) (e.g. 1000 ms for one request per second).

• Review Your API and Network Setup:
  Double-check that the API endpoint URL is correct and verify that any reverse proxies or load balancers are configured correctly. If your instance uses SSL/TLS, make sure certificates are valid and that any TLS termination is properly handled.

• Monitor and Adjust Timeouts:
  In some cases, adjusting the timeout settings for axios (or network settings on your server) can help if the remote API is slow to respond. This might involve increasing timeout values if supported by your configuration.

Summary

The sporadic “socket hang up” error in your updated n8n instance is most likely due to the connection being reset—often related to rate limiting, network configuration, or timeout issues. By enabling retries, batching requests, and reviewing your proxy and API endpoint settings, you can mitigate these errors.

If the issues persist over time, further investigation into network logs and the target API’s reliability may be necessary.