When creating an OCPP server node, specifying the same port as the node-red itself will lead to node-red itself crashing. In principle this issue could be viewed as two distinct problems:
The fact that node-red crashes instead of the faulty node reporting an error (this happens when a catch:all node is present in the flow too);
The fact that the node attempts to bind a new server to the port, rather than adding a route on the same server that node-red already has up (similarly to how e.g. @flowfuse/node-red-dashboard does.)
It would be lovely if at least the first issue was fixed however, as starting node-red in safe mode can be not straightforward to figure out.
When creating an OCPP server node, specifying the same port as the node-red itself will lead to node-red itself crashing. In principle this issue could be viewed as two distinct problems:
catch:allnode is present in the flow too);@flowfuse/node-red-dashboarddoes.)It would be lovely if at least the first issue was fixed however, as starting node-red in safe mode can be not straightforward to figure out.