Built-in websocket nodes not compatible with Node.js 18?

parasaurolophus · 12 January 2023 12:30

Is this a known issue? (Maybe the reason the NR 3.0.2 installation script still installs Node.js 16?)

In any event (pun intended), websocket server ("listen to") nodes appear to be broken in NR 3.0.2 under Node.js 18.12.1 (the latest LTS version as of the time I had reason to configure a new Raspberry Pi a short while ago). Does anyone know of a work-around other than "use MQTT instead" or "keep using the out-of-date Node.js?"

Thanks in advance for any info.

Steve-Mcl · 12 January 2023 12:35

Node JS v16 LTS is still "in date"

I dont recall it being raised - have you looked (or raised) an issue on the node-red repository?

parasaurolophus · 12 January 2023 13:31

Node JS v16 LTS is still "in date"

Ok, "...superseded..."

dont recall it being raised - have you looked (or raised) an issue on the node-red repository?

Didn't see an issue matching this particular compatibility problem on the node-red repo. Just added one.

TotallyInformation · 12 January 2023 14:31

Are you getting any error messages? Have you tried increasing the Node-RED logging level to see what is happening?

Colin · 12 January 2023 14:31

Please post a link to it so those interested can watch it.

dceejay · 12 January 2023 17:26

github.com/node-red/node-red

WebSocket compatibility with Node.js 18.x

opened 01:13PM - 12 Jan 23 UTC

parasaurolophus

needs-triage

### Current Behavior WebSocket client ("connect to") nodes fail to connect to s…erver ("listen to") nodes when the latter are running under Node.js 18.12.1. ### Expected Behavior WebSocket connections should work consistently on LTS version of Node.js as well as earlier versions. ### Steps To Reproduce 1. Install Node.js LTS 2. Install Node-RED using the standard Debian script without specifying a version of Node.js 3. Create a pair of "listen to" and "connect to" websocket nodes using the corresponding URI and URL values such that they should connect, e.g. "listen to" URI = /test and "connect to" URL = ws://localhost:1880/test In my case, the latter works when the "listen to" node is running under Node.js 16.x but not when it is running under 18.x. If it helps in debugging, "connect to" nodes running under Node.js 18.x do appear able to connect to "listen to" nodes on the network when the "listen to" nodes are running under 16.x. I.e. the issue appears to be on the server side. ### Example flow ``` [ { "id": "ef1453a3ef0962a6", "type": "tab", "label": "WebSocket Test", "disabled": false, "info": "", "env": [] }, { "id": "4cfc8d3ec3a4b40b", "type": "websocket in", "z": "ef1453a3ef0962a6", "name": "", "server": "1f015a9cb54deefa", "client": "", "x": 240, "y": 180, "wires": [ [ "d7ee73bf93a4919a" ] ] }, { "id": "29e40922241ebcd3", "type": "websocket out", "z": "ef1453a3ef0962a6", "name": "", "server": "1f015a9cb54deefa", "client": "", "x": 600, "y": 180, "wires": [] }, { "id": "d7ee73bf93a4919a", "type": "change", "z": "ef1453a3ef0962a6", "name": "", "rules": [ { "t": "delete", "p": "_session", "pt": "msg" } ], "action": "", "property": "", "from": "", "to": "", "reg": false, "x": 420, "y": 180, "wires": [ [ "29e40922241ebcd3" ] ] }, { "id": "eeba8377b2b3fae4", "type": "websocket in", "z": "ef1453a3ef0962a6", "name": "", "server": "", "client": "78b63c8224717d1a", "x": 300, "y": 280, "wires": [ [ "1402b256df6187d6" ] ] }, { "id": "1402b256df6187d6", "type": "debug", "z": "ef1453a3ef0962a6", "name": "debug 1", "active": true, "tosidebar": true, "console": false, "tostatus": true, "complete": "payload", "targetType": "msg", "statusVal": "", "statusType": "counter", "x": 500, "y": 280, "wires": [] }, { "id": "1f015a9cb54deefa", "type": "websocket-listener", "z": "ef1453a3ef0962a6", "path": "/test", "wholemsg": "true" }, { "id": "78b63c8224717d1a", "type": "websocket-client", "z": "ef1453a3ef0962a6", "path": "ws://localhost:1880/test", "tls": "", "wholemsg": "true", "hb": "5", "subprotocol": "" } ] ``` ### Environment - Node-RED version: 3.0.2 - Node.js version: 18.12.1 - npm version: 8.19.2 - Platform/OS: Raspberry Pi OS (bullseye) - Browser: Chromium 104.0.5112.105 (Official Build) Built on Raspbian , running on Raspbian 11 (32-bit)

system · 13 March 2023 17:26

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

Topic		Replies	Views
:tada: Node-RED 1.2.6 released News	83	5278	27 January 2021
Can't connect websocket (disconnected) General	16	2582	17 February 2021
Sanity check on my node-red version General	16	1109	10 October 2020
Some node installs failing General	8	600	17 December 2018
Debugging and Notification issues General	7	220	2 August 2021

Built-in websocket nodes not compatible with Node.js 18?

Related Topics