UPDATE / Resolved: Upgraded to 3.1 - http request nodes are now giving ERR_TLS_CERT_ALTNAME_INVALID error. Rolled back to 3.0, error is gone

General
, ,
1

@TotallyInformation Finally figured this one out, and wanted to share the resolution!

Because an older palette I had installed was using an older version of agent-base, it was breaking the http-response node. Which meant that it was only getting responses from my OWN nginx server.
I cleared out a bunch of unused palette (I suspect the culprit was an old mqtt one...), restarted my docker container and viola - it works again.

The reason it worked in 3.0 vs 3.1 is that in 3.0 it used to "fix" it. Now it doesn't, which I suppose it a good thing. :slight_smile: Anyways, thanks for all the help talking it out!

---------------------------------------------------------------------
Patched https.request function detected. This will break the
HTTP Request node. The original code has now been restored.

This is likely caused by a contrib node including an old version of
the 'agent-base@<5.0.0' module.

You can identify what node is at fault by running:
   npm list agent-base
in your Node-RED user directory (/data).
---------------------------------------------------------------------
1 Like
2

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