Node red not running in Venus OS v3.80~11 available for public testing

Beta testing Venus OS beta testing
1

Please advice me how I can report that Node Red does not open in V3.80~11 if the Venus OS v3.80~11 available for public testing thread is closed?

I got following error:
Error: remote installation does not seem to have a running Node Red service.

2

Like this, are you afraid nobody reads it?

1 Like
3

Yes!
Gone back to 3.72 and node red doesn’t start anymore,…

4

Don’t see the node red icon it in VRM anymore.
Node red is enabled, try a factory reset

5

oh, if you have a moment, we might be able to figure out was is going on.

6

OK
Did an update to 3.80~11, got the error and now switched back to 3.72 the VRM node red icon is gone.

7

And node red is back in 3.72 !

8

Try to install 3.80~11 again?

9

Tomorrow seems like better idea, I don’t know the Node-RED code nor a lot of JavaScript. It is doing this:

2026-04-02 16:25:08.582064500 [red] Uncaught Exception:
2026-04-02 16:25:08.592595500 2 Apr 18:25:08 - [error] TypeError: Cannot read properties of null (reading 'toString')
2026-04-02 16:25:08.592605500     at Timeout.migrateSubscriptions [as _onTimeout] (/usr/lib/node_modules/@victronenergy/node-red-contrib-victron/src/nodes/victron-nodes.js:21:69)
2026-04-02 16:25:08.592611500     at listOnTimeout (node:internal/timers:583:11)
2026-04-02 16:25:08.592613500     at process.processTimers (node:internal/timers:519:7)

Before that line is does check the type is undefined, but null is different than undefined.

1 Like
10

A post was merged into an existing topic: Grid frequency widget resolution

17

Some problem, rollback to v.3.80~9, node-red works fine

1 Like
25

Updating to 3.80~13 didn’t fix the issue.
Now rolling back to 3.72.

Venus OS is running on a Cerbo GX.

After rollback:
Opening node red in 3.72 did give the following error:
“Token expired. Go back to VRM and try again.”

After 3 attempts, node red is up and running again, maybe this helps debugging.

26

I am really quite surprised how you have missed this:

NOTE !

  • There is an issue in v3.80~11 for some Node-RED setups, see above Popular bug report / discussion section. It is a known issue and will be looked at, but it seems to only affect some. Switching to an older version will resolve it. Updating to a newer beta version doesn’t!
1 Like
27

This attitude isn’t professional!

In the note you/victron writes that only SOME are affected.
Some is this only mine Victron Cerbo GX or are all effected?
Sure beta release,…

On mine system none other processes are running, so why is mine system affected and other Cerbo GX systems not?
Maybe other beta releases installed something that is still running?

1 Like
28

I’m affected too… I had the latest 3.80~13 installed; I was working in NodeRED just today, and while I was building a flow, everything suddenly disappeared… I can no longer access NodeRED. I’ve tried everything—restarts, reverting to the current stable release—but nothing works… I can’t access it from the VRM portal, nor directly via IP and port from the Cerbo.

29

This starts to get very strange!
Just checked and mine node red is still running under 3.72.
Whats happens when you install an official release?

30

As I mentioned earlier, even downgrading to the current stable release (3.72) doesn’t help… When I access the Cerbo via WinSCP, it looks like Node-RED has completely disappeared from the system… I’m currently in the process of installing the standard image (without Node-RED) so I can switch back to the Large image afterward…

31

It took several minutes after rollback, check in 10 minutes.

32

Do you get:
“Token expired. Go back to VRM and try again.”
or
" Error: remote installation does not seem to have a running Node Red service."

33

Error: remote installation does not seem to have a running Node Red service.

Edit: Here we go again… I actually had to reset my Cerbo to the standard image and then reinstall the Large image… Lucky for those who happened to back up their flows beforehand :wink: