HTTP node: PUT request returns "Only absolute URLs are supported"

Describe the problem/error/question

Hey dear community! I’m sending a PUT request to a widget API endpoint and receive the error “Only absolute URLs are supported”, even when the URL is using an absolute path. I’ve tried sending the same request via Postman and that to my surprise works with having copied the same body, headers and URL, which then makes me think something happens on node level when the response comes in. Also, all other HTTP methods work (GET, HEAD, OPTIONS, POST). For nondisclosure purposes, I’ve covered most of the sensitive data. Hope you understand and still are having enough info to support me with this!

Now, my questions: How I can fix it for my running self-hosted instances? Could it be that the response of the endpoint is causing this or could it be something else? And is there any chance of debugging this and see the full request + response objects? Could it be a misconfiguration of the proxy?

What is the error message (if any)?

Error JSON:
{ "status": "rejected", "reason": { "message": "500 - \"Only absolute URLs are supported\"", "name": "Error", "stack": "Error: 500 - \"Only absolute URLs are supported\"\n at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)\n at RedirectableRequest.handleResponse (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:238:9)\n at RedirectableRequest.emit (node:events:525:35)\n at RedirectableRequest.emit (node:domain:489:12)\n at RedirectableRequest._processResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:356:10)\n at ClientRequest.RedirectableRequest._onNativeResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:62:10)\n at Object.onceWrapper (node:events:628:26)\n at ClientRequest.emit (node:events:525:35)\n at ClientRequest.emit (node:domain:489:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:693:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)\n at TLSSocket.socketOnData (node:_http_client:534:22)\n at TLSSocket.emit (node:events:513:28)\n at TLSSocket.emit (node:domain:489:12)\n at addChunk (node:internal/streams/readable:315:12)\n at readableAddChunk (node:internal/streams/readable:289:9)\n at TLSSocket.Readable.push (node:internal/streams/readable:228:10)\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)" } }

Stack trace:

NodeApiError: The service was not able to process your request
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:1281:27)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:655:19)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:596:53

Please share your workflow

It’s just a simple HTTP request node, started by a manual trigger.

Share the output returned by the last node

Information on your n8n setup

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

Okay, so this might actually have more to do with the endpoint than n8n. I’ll keep you posted.

So yes, it was the provider of the widget API, that seemed to have a misconfiguration of their endpoint going on. Contacting them has resolved the issue and with that n8n and the HTTP node is working fine :slight_smile:


Sweet, glad you figured it out @Marcelo! And welcome to the n8n community :slight_smile:

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