Please provide your feedback in this short Flings' survey.
Jun 18, 2020

I am using vSphere Client version and recently stood up FAMI Build 15670023

When attempting to navigate to https://IP.address/UI I am directed to a blue screen with a red banner at the top of the the page containing the following text; "[400] An error occurred while sending a logout request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - Failed to connect to VMware Lookup Service"

Has anyone else encountered this before and/or does anyone have advice on how to remedy it?

Jun 18, 2020

Nevermind. I found the problem. The DNS settings at https://IP.address:5480/ wouldn't save. Doing some research in this thread I found that changing the file directions was required to activate the UI updates.

Here is the relevant thread.

"due to changing the base operating system for the fling, the DNS system used has changed to systemd-resolved, which operates differently to the one in previous fling releases.

The easiest workaround is to link /etc/resolv.conf to point to /run/systemd/resolve/resolv.conf; the changes made to resolv.conf will then be respected by systemd. To do this, execute the following on the fling appliance:

rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

The DNS servers added to /etc/resolv.conf will now be used and the changes won't be overwritten."

Once I logged into the VM from the console and ran this command I was able to successfully update the DNS settings AND save them. After that, I no longer received my above error.

Perhaps the developers could look at this as a learning moving forward and enable the actual UI for clients and admins instead of hard coding a vital setting like DNS internally?