VConnect on Cerbo shows network even when off - How can I troubleshoot?

My GX won’t/can’t connect to WIFI. I’m trying to troubleshoot.

VictronConnect > Network Settings (via bluetooth) shows the WIFI with 70% bars and a checkmark. It also shows the WIFI access point as a network, no checkmark. If I turn off the WIFI, VConnect still shows that network with bars and a checkmark. If I disable Access Point, VConnect still shows that with bars. It seems VConnect does not use live status for network availability.

VConnect says “Not connected to a wireless network.”

Click Scan for Networks, and it does nothing. The button “depresses”, but that’s all. No spinning or other sign of a scan. No change to network status. If I click to connect to network, it immediately posts “Connection failed” – no scan, no sign of trying to get a handshake or signal. If I click FORGET, the FORGET button goes grey, but the network is still in the list, with a checkmark. When I restart VConnect and look at Network Settings, the FORGET button is bold again.

I know the bluetooth connection is alive – I can use it to turn off the Wireless Access Point. When I do that, the access point still remains in the list. Yes, I have shut down and restarted VConnect between every change I’ve tried to execute.

Here’s my problem. I just want to know whether the Cerbo ACTUALLY sees my network. Nothing in the VConnect GUI convinces me either way. It just looks like a static page that doesn’t reflect the current state. Is this a bug in the VConnect GUI? Or does this actually indicate something? How can I verify that the GX can or cannot see my WIFI? Is there another way to do that?

Update: Hunting around in VictronConnect I found the network errors - failure to resolve DNS name for what loojs like the Victron logger service or some such. Hunting the form I found that a GX reboot sometimes fixes things. I never did find what a reboot actually does, but I saw that it retains your settings, which is ok. Also saw that you dhould set to reboot on disconnect - this must be a common problem. Reboot fixed the main issue - we have connectivity. Still two mysteries:

  1. Why is DNS failure so common ans how can I mitigate that?
  2. Why does the VConnect bluetooth GUI fail to show realtime list of available networks. I believe this is actually a bug.