GX updated to new firmware last night, and now will not connect to VRM portal. It reboots every hour.
Hi @Kokomo,
You have tagged the Ekrano GX, can you confirm that is the GX device you are using?
The hourly reboot is a feature of VenusOS when the internet connection is not detected, so the internet connection would be where I would investigate first.
It’s sometimes a co-incidence in timing.
If you can’t find any issues with the internet connection, can you try rolling back to 3.55 to see if that resolves it and then help us to isolate the cause.
A post was split to a new topic: Can you disable the automatic reboot when a GX device loses internet?
4 posts were merged into an existing topic: Can you disable the automatic reboot when a GX device loses internet?
OK, I can breathe easy again now.
You had me startled there for a second but it seems it was just an interpretation misunderstanding 
In reply to OP:
If the device is actually an Ekrano (and not a CCGX that turns out to have CPU troubles running the latest v3.60 code), the reboot issue is a weird one.
Internet stability and connection stability between LAN and GX would be the first things I’d check, as well as disabling the “Reboot device when no contact” feature.
1 Like
Yes, I have an Ekrano GX, and it seems to be having issues connecting to the VRM cloud (see screen shot). The boat has internet connectivity.
OK, the hourly reboot is because the “Reboot device when no contact” setting is enabled.
That is one part.
The reason you’re getting timeouts connecting to VRM, that is another part.
In short: it shouldn’t do that.
I’ve updated 6 GX devices to v3.60 now and none of them are having any troubles connecting so your issue is a strange one.
Just to check: is the GX configured to use an IP from DHCP or is it configured for static IP ?
Trying to rule out a firewall or DNS problem here.
Is it even successfully connected to the onboard Wifi ?
It is connected via DHCP. It didn’t have any issues until after it rebooted with the new firmware. It is successfully connected to wifi, and I disconnected and reconnected it. I also tried switching to manual IP settings, but no joy.
Do you want me to try any changes or just roll it back?
Thanks @Kokomo
No settings changes yet, please just try to roll back to 3.55 to see if that resolves it automatically.
If a rollback to the previous version (please do state what version that is) fixes the problem, something might be up.
Reminder: v3.60 can roll back to an earlier version but you won’t be able to simply boot back into v3.60 again after rolling back, due to changes in the filesystem.
If you roll back to a previous version, your only option to get back to v3.60 is to download it again.
Depending on your internet options (at sea or not) it could be a good idea to keep a USB stick with the v3.60 update.swu package close by.
Up to you if you want to roll back to the previous version now to see if that fixes the issue.
If you don’t really need the reporting you could wait until @guystewart had a check with the backend guys to check options.
I’d rather try the roll back first, the other team won’t be able to check my other theory for several hours still, and if roll back resolves it then I can rule out asking them.
1 Like
I’m rolling it back - although it looks like it came online just before I initiatied the rollback. The only other change i made was toggling between automatic and manual ip settings which I had tried several times with no luck.
A very long shot in the dark: the Cerbo GX MK2 (and specifically this version, uncertain about the Ekrano) had some Wifi troubles in the past.
They were fixed in the v3.60 software release but required the GX device to get a cold reboot (power plug out and back in again).
As stated: it’s a long shot but could be worth a try.
Otherwise I’d go for @guystewart’s suggestion of rolling back to v3.55 and see if that fixes the issue or not.
it’s rebooted to 3.55 and is good.
1 Like
I have no knowledge about the internet setup on your boat or the required settings but here’s to hoping your issue will be fixed.
Off to bed here now, hopefully everything will be sorted when I wake up again
That complicates our troubleshooting a little bit now.
If everything is working, let’s leave it as it is for now. If more cases come up, it will be useful to also have this one to help narrow things down, but right now I’ll focus on those that haven’t been able to resolve yet.
If you want to play around with it, then try swapping back and forth between 3.60 and 3.55 to see if you can find anything else out.
I apologize - I’m not sure my above statement is true (that it came online before I rolled it back) – I think it had rebooted already.
Given that I’m in Alaska, I will leave it on 3.55.
2 Likes
Right, thanks for reporting, and I think now that it’s working, disable automatic updates and leaving it is the best.
If you’re feeling lucky you could try updating to v3.60 again (and roll back to v3.55 if that re-introduces the issue) but maybe just keep it at the current working version while more thorough checks are being done