I just had this problem when upgrading FOG from 0.30 to 0.32 though in our case the cause was different.

In our case, we are using 2 interfaces, one on our main network, and the other on a private network used just for imaging. The ‘Failed to Connect to DefaultMember’ error on the dashboard was due to a combination of having a private (non routed) subnet for imaging, and configuring a http proxy in FOG. The problem is that the ‘Fetch’ command defined in commons/functions.include.php and used to get the /fog/status/hw.php page for the StorageNode will try to use the proxy to access the private network IP (which of course is not accessible via the proxy).

Our workaround is to remove the proxy configuration, and the dashboard error disappears.

For a proper solution, is there any way to configure the proxy for internet access, but not use it for accessing the StorageNode URL?

It seems that in 0.30, the StorageNode URL was fetched using curl, and did not use the FOG proxy settings - this behaviour has changed in 0.32 with the introduction of the Fetch command which always uses proxy settings if they are available.