Node-Red - HTTP GET: RequestError: EPROTO wrong signature type:ssl/t1_lib.c


I tried to set up my first HTTP Request Node.

The assignment is (or should be) rather simple. It should GET this URL.

If I paste this URL in my browser, I get a valid response. Obviously the URL above is modified to hide some username details, but even then, the response is a valid one “0|1|user not found”. Feel free to try it.

However, if I try this via the HTTP request node with the settings below, it just doesn’t work:

I am received the following error message:
RequestError: write EPROTO 3801D2F14F7F0000:error:0A000172:SSL routines:tls12_check_peer_sigalg:wrong signature type:ssl/t1_lib.c:1572:

So what am I doing wrong?

I currently run this:

Welcome to Node-RED
18 Jan 16:00:23 - [info] Node-RED version: v3.0.2
18 Jan 16:00:23 - [info] Node.js  version: v18.12.1
18 Jan 16:00:23 - [info] Linux 5.15.80 x64 LE

Add-on: Node-RED
 Flow-based programming for the Internet of Things
 Add-on version: 14.0.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.4  (amd64 / qemux86-64)
 Home Assistant Core: 2023.1.5
 Home Assistant Supervisor: 2022.12.1

If I change HTTPS to HTTP, it is working fine (it returns 0|1|user not found). But it should work with HTTPS as well…

I looked for help on the Node-Red forum, but they seem to believe it’s Home Assistant related. A stand-alone Node-Red install doesn’t have this issue.

Hi @DriesA , did you ever find a solution for this issue? I’m experiencing the same problem as first have a go using the http nodes.

Could this be the consequence of Node Red running in a container? The error arises because Node Red inside its container can’t see the Internet?