Invalid URL in HTTP nodes

Questions
1

Describe the problem/error/question

Unable to fetch URL from HTTP/RSS nodes. RSS trigger is working correctly though

What is the error message (if any)?

Problem in node ‘HTTP Request‘
Invalid URL

Please share your workflow

Share the output returned by the last node

{
  "errorMessage": "Invalid URL",
  "errorDetails": {},
  "n8nDetails": {
    "n8nVersion": "2.14.2 (Self Hosted)",
    "binaryDataMode": "filesystem",
    "stackTrace": [
      "TypeError: Invalid URL",
      "    at new URL (node:internal/url:819:25)",
      "    at appendResumeToken (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/get-additional-keys.ts:20:17)",
      "    at getAdditionalKeys (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/get-additional-keys.ts:36:15)",
      "    at ExecuteContext.get additionalKeys (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/node-execution-context.ts:420:27)",
      "    at ExecuteContext.Memoized.descriptor.get (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+decorators@file+packages+@n8n+decorators/node_modules/@n8n/decorators/src/memoized.ts:29:32)",
      "    at ExecuteContext._getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/node-execution-context.ts:458:11)",
      "    at ExecuteContext.getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/execute-context.ts:136:9)",
      "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:211:22)",
      "    at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:31)",
      "    at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1224:22)"
    ]
  }
}

Information on your n8n setup

  • n8n version: 2.14.2 & 2.15.0
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own, main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker / self-hosted
  • Operating system: Linux / docker
2

Hi @pygillier Welcome!
this error can arise, not due to the misconfiguration of your http node, but some problem with your n8n instance, which in this case can be the WEBHOOK_URL not correctly defined with the https:// like basically your docker compose file should have these variables, please cross check:

environment:
  - WEBHOOK_URL=https://your.domain.com
  - N8N_HOST=your.domain.com
  - N8N_PORT=5678
  - N8N_PROTOCOL=https

if something was missing , add it and restart it and then let me know if the issue persists.

3

Unfortunately, I’m still having the error. Will try to reinstall latest n8n.

4

Let us know if that resolves your issue, or the issue persisted

6

Reinstalling with a clean setup fixed the problem.
@Benjamin_Behrens it was weird as the “RSS trigger” node type was working but the “RSS Read” one (and HTTP request) were not; with the same URL.

7

I’m having exactly the same issue on the HTTP nodes. After recently updating my N8N these nodes stopped working.

Update: fixed & mine was related to this issue: Updated to 2.8.3 and now no "https://" in webhook URL