After the downgrade initiated by Victron from firmware v3.80~22 to v3.73~1 I can’t connect to Node-Red not via VRM-Portal and also not via Remote Console (see screenshots).
Please, can you fix it shortly?
Regards,
Gerd
Did you already try booting back to 3.80~22 via Settings → General → Firmware → Stored backup firmware to see if that fixes it?
If you are running beta firmware, disable automatic updates to avoid this issue, monitor the beta section in the community and update manually.
If your system is important to you, please don’t run betas in production.
The territory comes with challenges and inevitably takes down to resolve.
It’s easiest, as suggested to rollback to the backup image or switch back to GA software (3.72). Thanks.
I never had any issues with automatic updates before, since this downgrade initiated by Victron.
Regards,
Gerd
Alternatively, you can switch Node-RED to start in safe mode (via Settings → Integrations → Node-RED → Node-RED → Enabled (safe mode). This will start Node-RED in safe mode: all of the flows will be disabled. That way you should be able to access the flow editor and fix the issue.
Are there any third party mods or drivers loaded?
If you can screenshot:
Settings → General → support
safe mode and Node-RED factory reset doesn’t help.
Regards,
Gerd
Both of those mods have known issues like this. Please check the guimods and setuphelper topics of @kwindrem Modifications section. Likely need updates or a reflash to fix.
When reporting issues, it’s important to mention if mods or drivers are loaded, they are the cause of so many issues.
After uninstalling all @kwindrem modifications und installing the latest official release v3.73 released today, the Node-RED remote access is also not working (see attachments).
Regards,
Gerd
@nickdb I’m with you, but I hoped to get shortly a solution for this issue:
with the beta version.
But unfortunately also installing the official release v7.37 an uninstalling the modifications didn’t solve my problem of not connecion to remote Node-RED.
Regards,
Gerd
I can only suggest you reflash the cerbo.
Did you check the disk isn’t full? That sometimes happens.
Resetting to default is a pain but it does often solve strange issues.
Hopefully you have an export of all your flows.
I thought, I did it by installing the latest official release v7.37 via online update, or is there a difference between online update and update via SD Card?
Regards,
Gerd
Yes, the manual is a full factory reset. The others preserve settings and data
Good morning @nickdb,
- I think there is enough space on my CerboGX:
root@einstein:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 1197224 1021872 97372 91% /
devtmpfs 464828 0 464828 0% /dev
tmpfs 514492 984 513508 0% /run
tmpfs 514492 204 514288 0% /var/volatile
/dev/mmcblk1p5 4839520 15328 4557648 0% /data
tmpfs 514492 984 513508 0% /service
overlay 514492 204 514288 0% /var/lib
Data partition free space: 4.3 GB
or do you mean the space on my PC?
-
I have a full backup from my Node-RED flows.
-
And now the best: I got the remote access back to Node-RED on my CerboGX this morning. I don’t know why, I didn’t change anything on my PC, network, or CerboGX, but I’m happy not to have all the pain with resetting my CerboGX.
Thanks a lot again for all your support to @nickdb and @dfaber.
Regards,
Gerd
How strange. Glad it is working.
reinistalling latest @kwindrem GUImods on latest official release v7.37 and sill working 
I do experience the same. Also beta 3.80 22. Most of the time NodeRed is accessable, today it is not. I don not think it is related to the beta version. Testing the Shelly EM50 Pro. It does not work in VenusOs 3.7.3.