Server issue after upgrading to [10.7.0] - 2022-10-29

[houser42]

Hello, It could be something else of course, but I can not start my node red server after upgrading to [10.7.0] - 2022-10-29. Is there a possibility that there is something wrong in that package? [10.6.0] - 2022-10-28 was working fine. Grateful for a comment.

[windkh]

What node version do you have?

[windkh]

I just removed dependency to crypto and fs as they are integrated into node... but it could be that this is only available in a later node version

[houser42]

I just removed dependency to crypto and fs as they are integrated into node... but it could be that this is only available in a later node version

I see. I am not by the server, but I can say that it is less than v14.17.6 as there is an update available to that version; nodejs to v14.17.6 in the linux branch I am using.

[houser42]

Can you comment on which versions I need for your 10.7 version to be supported please?

[windkh]

Is somethi g printed in the nodered console? So that I know what package caused the problems?

[houser42]

Is somethi g printed in the nodered console? So that I know what package caused the problems?

As it stands I can not start the node red server after the upgrade to [node-red-contrib-shelly 10.7. SO I can not see the console. I need to either downgrade the [node-red-contrib-shelly node or upgrade my linux branch which will give me the v14.17.6 node.js that perhaps might help?

[windkh]

Why did you close it?

[houser42]

mistake. apologies

[windkh]

I can revert the changes if required... don't know by heart what node version supports crypto

[houser42]

That is your expertise and I am afraid I can not say anything about that. I can just say that on this particular branch this change disrupts the node red flows and makes the server unresponsive.

[houser42]

So I got the server up again by safe booting it.. My problem is that I only have access to this particular site install via the Node Red webgui, so I can’t downgrade AFAIK. Grateful for an helpful hints if you have any.

[windkh]

I will revert the changes and create a new version

[windkh]

V10.8.0 should fix it

[houser42]

I am sorry to report that I am still having issues after this upgrade. I am unable to get this install working again, even after a complete wipe and reinstall.

I keep seeing this, even after a vanilla reinstall. Is it possible that something has gone wrong in the code? As soon as I drag one shelly node in to a flow I get this message in the pallete. No other nodes are acting upon from backup and reinstall. Only this Shelly node.

Can I go back to 10.5 that worked perfectly from a terminal reinstall? Sorry about this and thanks for your patience.

[windkh]

I will install it on my own right now... gimme a few minutes

[windkh]

installed correctly on node-red 3.0.2, nodejs 16.6.0

[windkh]

what does the node-red console output say?

[houser42]

I can install it too but have you tried deploying a node or two? This error comes after a deploy,

[windkh]

yes, everything works as expected.

[windkh]

We need to find out what module was not found: for that reason the console output is needed

[windkh]

maybe it is the path dependency const path = require('node:path');

[windkh]

just pushed 10.9.0 with a changed path require. Please try it.

[windkh]

I mean 10.9.1

[houser42]

Ok. Will try its as soon as I see it. NR server is 3.02 and nodejs is v14.17.6 FYI.

[houser42]

Yes! That appears to have fixed it. Working on getting the site up again, but pretty sure that was the issue. Appreciate your prompt help enormously!