Just updated to venus-os-v3-70-91 , NodeRed (:1881) gives http error 400
Reset Node did not help
Booting backup V3.70~88 works fine.
Update: the flow loaded with ~88 is running in ~91, but port 1881 can not be reached.
it is on hold for the moment.
1 Like
In venus os v3.70~91 node red isn’t accessible anymore.
SignalK server doesnt start after upgrade to v3.70~91 (from 88). Investigating.
The last signalk change we made is in v3.70~73 (and that is a minor one)
likely related to Venus-os-v3-70-91 Node-red not working - #3 by jeroen
Looking into it.
The same error
IP:3000/admin/#/dashboard returns HTTP ERROR 400
Some plugins seems to be working, some not
SignalK server doesnt start after upgrade to v3.70~91 (from 88). Investigating.
Thanks for noticing (and for the others as well). But please do me a favor and look if there is already an issue about it. It is really a waste of time to double check that (duplicated issues) are present. (Well, we even don’t know for sure the signalk and node-red issues are the same, but well …). Anyway, seems to be a nodejs “security update” which bricks both. I will revert those changes.
check v3.70~92
2 Likes
NodeRed is running with V3.70~92.
well done !!
but now its time to go to bed
Thanks a lot for this quick fix
1 Like
Bingo!
SignalK back to live in 92 without uninstalling 91.
BTW: Time for SignalK server upgrade? 22.1 is out
yes. time to go to bed…
3 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.