Request proxied to Axios failed

Hi there,

After multiple tries, I’m facing issue when I try to use http nodes. After each try, node return “Bad gateway - the service failed to handle your request”
I turned on debug mode and issue maybe come from Axios :
n8n | 2024-12-03T09:49:09.789Z | debug | Execution added {“executionId”:“183”,“file”:“active-executions.js”,“function”:“add”}
n8n | 2024-12-03T09:49:09.791Z | debug | Execution for workflow test was assigned id 183 {“executionId”:“183”,“file”:“workflow-runner.js”,“function”:“runMainProcess”}
n8n | 2024-12-03T09:49:09.801Z | debug | Execution ID 183 is a partial execution. {“executionId”:“183”,“file”:“workflow-runner.js”,“function”:“runMainProcess”}
n8n | 2024-12-03T09:49:09.801Z | debug | Workflow execution started {“workflowId”:“S20M02px1PBtzSuV”,“file”:“LoggerProxy.js”,“function”:“exports.debug”}
n8n | 2024-12-03T09:49:09.802Z | debug | Executing hook (hookFunctionsPush) {“executionId”:“183”,“pushRef”:“xhizrff9js”,“workflowId”:“S20M02px1PBtzSuV”,“file”:“workflow-execute-additional-data.js”,“function”:“workflowExecuteBefore”}
n8n | 2024-12-03T09:49:09.803Z | debug | Send data of type “executionStarted” to editor-UI {“dataType”:“executionStarted”,“pushRefs”:“xhizrff9js”,“file”:“abstract.push.js”,“function”:“sendTo”}
n8n | 2024-12-03T09:49:09.804Z | debug | Start processing node “Sekoia HTTP Request” {“node”:“Sekoia HTTP Request”,“workflowId”:“S20M02px1PBtzSuV”,“file”:“LoggerProxy.js”,“function”:“exports.debug”}
n8n | 2024-12-03T09:49:09.806Z | debug | Executing hook on node “Sekoia HTTP Request” (hookFunctionsPush) {“executionId”:“183”,“pushRef”:“xhizrff9js”,“workflowId”:“S20M02px1PBtzSuV”,“file”:“workflow-execute-additional-data.js”,“function”:“nodeExecuteBefore”}
n8n | 2024-12-03T09:49:09.806Z | debug | Send data of type “nodeExecuteBefore” to editor-UI {“dataType”:“nodeExecuteBefore”,“pushRefs”:“xhizrff9js”,“file”:“abstract.push.js”,“function”:“sendTo”}
n8n | 2024-12-03T09:49:09.806Z | debug | Running node “Sekoia HTTP Request” started {“node”:“Sekoia HTTP Request”,“workflowId”:“S20M02px1PBtzSuV”,“file”:“LoggerProxy.js”,“function”:“exports.debug”}
n8n | 2024-12-03T09:49:09.839Z | debug | Request proxied to Axios failed {“status”:502,“file”:“LoggerProxy.js”,“function”:“exports.debug”}
n8n | 2024-12-03T09:49:09.867Z | debug | Send data of type “sendConsoleMessage” to editor-UI {“dataType”:“sendConsoleMessage”,“pushRefs”:“xhizrff9js”,“file”:“abstract.push.js”,“function”:“sendTo”}
n8n | 2024-12-03T09:49:09.868Z | error | 502 - “\n<html lang="en">\n The webserver reported that an error occurred while trying to access the website. Please return to the previous page.

\n \n \n \n \n \n
URLhttps://api.sekoia.io/v1/sic/alerts?limit=10
\n\n\n\r\n”
n8n | AxiosError: Request failed with status code 502
n8n | at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:19:12)
n8n | at RedirectableRequest.handleResponse (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:547:9)
n8n | at RedirectableRequest.emit (node:events:531:35)
n8n | at RedirectableRequest.emit (node:domain:488:12)
n8n | at RedirectableRequest._processResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:409:10)
n8n | at ClientRequest.RedirectableRequest._onNativeResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:102:12)
n8n | at Object.onceWrapper (node:events:634:26)
n8n | at ClientRequest.emit (node:events:519:28)
n8n | at ClientRequest.emit (node:domain:488:12)
n8n | at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:702:27)
n8n | at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/Axios.js:45:41)
n8n | at processTicksAndRejections (node:internal/process/task_queues:95:5)
n8n | at requestFn (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:617:33)
n8n | at proxyRequestToAxios (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:620:26)
n8n | at Object.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1301:16)
n8n | at Object.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:2090:20)
n8n | {“file”:“LoggerProxy.js”,“function”:“exports.error”}
n8n | 2024-12-03T09:49:09.868Z | debug | Running node “Sekoia HTTP Request” finished with error {“node”:“Sekoia HTTP Request”,“workflowId”:“S20M02px1PBtzSuV”,“file”:“LoggerProxy.js”,“function”:“exports.debug”}
n8n | 2024-12-03T09:49:09.869Z | debug | Executing hook on node “Sekoia HTTP Request” (hookFunctionsPush) {“executionId”:“183”,“pushRef”:“xhizrff9js”,“workflowId”:“S20M02px1PBtzSuV”,“file”:“workflow-execute-additional-data.js”,“function”:“nodeExecuteAfter”}
n8n | 2024-12-03T09:49:09.869Z | debug | Send data of type “nodeExecuteAfter” to editor-UI {“dataType”:“nodeExecuteAfter”,“pushRefs”:“xhizrff9js”,“file”:“abstract.push.js”,“function”:“sendTo”}

And on /home/node/.n8n/n8nEventLog.log I found this:
{“__type”:“$$EventMessageWorkflow”,“id”:“5eb8d483-13ca-4021-bedb-8aaee69b972d”,“ts”:“2024-12-03T04:49:09.897-05:00”,“eventName”:“n8n.workflow.failed”,“message”:“n8
n.workflow.failed”,“payload”:{“executionId”:“183”,“userId”:“4b0bc618-2261-4ba2-8a52-13aad1b875ee”,“success”:false,“isManual”:true,“workflowId”:“S20M02px1PBtzSuV”,"
workflowName":“test”,“lastNodeExecuted”:“Sekoia HTTP Request”,“errorNodeType”:“n8n-nodes-base.httpRequest”,“errorMessage”:“Bad gateway - the service failed to hand
le your request”}}

All logs above comes from Sekoia plugin but it is the same result when I try to request the Sekoia API from http nodes.

About my infrastructure, I pass through my proxy compagny and request appear as allow. Proxy is setup on the option node.

Any idea to fix the issue ? Or to try to debug more

Information on your n8n setup

  • n8n version: 1.69.2
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker compose (configuration file below)
  • Operating system: RH9.4
    Docker compose file:

Hi @Spitgrooves,

This sounds like a similar issue to the one reported here:

This is a known issue we’re working on resolving hopefully soon!

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