V3.70~9 not detecting headless GX state

After updating to v3.70~9 i have only limited access trough VRM, including no remote console. Since im using the Cerbo headless, eg no physical display connected to it, i essentially have no access.

I believe the Cerbo decides by itself that if during boot theres no display connected, then VRM is automatically gives full access instead of read-only. This check seems to fail.

Ive first encountered this when updating to v3.70~5 but thought nothing of it. Removing power, so letting it boot again, fixed the issue.

I can try other things first today, maybe theres an option if accessed trough bluetooth or trough web console

You can access the GX locally, using https://

And via Bluetooth, using the VictronConnect app

Yes, i just tried that, however it looks like its weird.

Theres no firmware version visible in the app

VRM has limited access, no remote console and no right side menu for quick settings

However, the webconsole did load and its showing that VRM is set to full access

A few more screenshots, is there something else i could grab before i reboot it? Ive got SSH access but im not sure what could be of value


Hi, I’ll check internally and get back to you next week

1 Like

One last question, can you post a screenshot of the lower section of the vrm portal menu?

Where it says Error / connection status and such?

Dang, i just rebooted it, but let me see if rolling back to the previous firmware breaks it again

Updated to v3.70~19 when it was released and the issue seems to be resolved

Ok. Good.

I hate to say it, but this is back with v3.64~2

Ive updated yesterday evening, and as of now the VRM connection is again read-only (no remote console, no right side switch menu)

Im fairly certain that a powercycle would fix it, but before i do that what can i check?

Hi, we’re looking into it. Would be great if you could leave it in its current state for today.

Thanks !

Will do





Hey @chrigu , thanks - we’ve gotten all available diagnostics. If you reboot it again it will probably work again.

Thanks for your help!

1 Like

v3.70~25 worked fine directly after the update

1 Like

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