Hi There. I’ve had my Cerbo GX connected to my Vans’ Wifi and reporting into the VRM portal with no issues until recently.
Since approximately 3.60 It would report in successfully for a seemingly random amount of time (hours to days) before the following DNS errors:
<urlib3.connection.HTTPSCpnnection object at 0xb4d2fa08>; failed to resolve ‘ccgxlogging.victronenergy.com’ ([Errno -3 Temporary failure in name resolution)
It doesn’t appear that the Cerbo GX would retry those DNS resolution attempts so, rebooting the Cerbo manually was the only solution (setting to auto reboot at disconnect did not seem to help).
Recently (last couple of days) I have had no luck connecting to my wifi network at all with the Cerbo. No obvious error messages.
There have been no changes to the wifi network and no other devices on the network (both 5Ghz and 2.4Ghz) have not reported any issues.
OS versions 3.60 - 3.64 have displayed at least the DNS error and reverting back to 3.63 did not resolve the connecting to wifi issue.
Hey Derek- I went with connecting to my router via Ethernet cable and that solved the issue for me. It’s been flawless since. I’ve noticed since the new UI was introduced, services that may take extra cpu are less likely to work well (I’ve gone with using an external Bluetooth adapter as well, because my Bluetooth tank sensor connections became unreliable).
Thanks. Sadly connecting via Ethernet isn’t an option for me but it’s been working fine on WiFi for a couple of years. Some time this morning it just stopped.
No matter what setting I try, even manual configuring IP settings, this issue still remains. I can confirm that if I connect via Ethernet to the same router it works, disconnecting and connecting via WiFi and it immediately stops working again. Sadly though this can’t be a permanent solution.
my next course of action is to do a factory reset of the Cerbo GX
Ok, so,I’ve finally figured this out. Didn’t need a factory reset in the end. It’s seems to have got itself confused regarding failover. To fix it…
Plugged in an ethernet connection and left WiFi connected. Disabled “allow using WiFi for internet access”, disabled “allow using Ethernet for internet access” and rebooted. After reboot, enabled “allow using WiFi for internet access”, removed the ethernet cable, rebooted. Wifi now works. The reboots seem important!
Decided to check failover after all of this, so inserted the Ethernet cable again, enabled “allow using Ethernet for internet access” (so both Ethernet and WiFi are allowed internet access), rebooted. Once back up played around removing the Ethernet cable and reinserting it, failover to WiFi worked as expected and no VRM connection issues (although it can take up to 2 mins to connect to VRM after switching network interfaces.
hopefully this is helpful to anyone else in a similar situation.
