HTTP 524 error? ERROR: The service failed to process your request

A working HTTP node that was calling an API happily suddenly started throwing errors.

HTTP 524 error ERROR: The service failed to process your request.

I had to google a 524 error having not seen it before and it appears to be linked to timeouts.

I am charged credits for these failing api calls so it seems they are partially working but I am not getting data back, only the error

I have reached out to support at proxycurl, the service supplying the API. They take 24hrs to reply so in the meantime I thought I would ask here and see if there is any chance this is an n8n related error, maybe a bad config? Which I doubt as it was working.

Please share your workflow

Error output

"524 - """,
"Error: 524 - "" at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15) at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12) at ClientRequest.handleResponse (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:238:9) at Object.onceWrapper (node:events:628:26) at ClientRequest.emit (node:events:525:35) at ClientRequest.emit (node:domain:489:12) at HTTPParser.parserOnIncomingClient (node:_http_client:693:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17) at TLSSocket.socketOnData (node:_http_client:534:22) at TLSSocket.emit (node:events:513:28) at TLSSocket.emit (node:domain:489:12) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at TLSSocket.Readable.push (node:internal/streams/readable:228:10) at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)"

Running the latest n8n self hosted using docker.

Hey @Robm,

From what I remember a 524 is normally cloudflare timing out the connection so I suspect the service you are using is sat behind it and the response for whatever API you are calling takes longer than Cloudflare is configured for.

Sadly I don’t think we have any options to get around this.

Thanks @Jon passed your thoughts onto the proxycurl support team. They have said it’s an issue on their side.

Appreciate you taking the time to reply.

1 Like

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