A fully supported version of the HTML5 client is released with vSphere 6.5, and the official name will be vSphere Client.  We won't be renaming this Fling, but may start saying things like 'vSphere Client Fling' in addition to the other terms we've used before. Fling features are not guaranteed to be implemented into the product.
Feb 19, 2020

I have just downloaded & tried to install v5.0 sadly without success. It's pretty frustrating that every release I try to install ends up not working & the last time I actually had a session with you guys to resolve my problems. I seem to have similar problems again.

I have copied the three config files (from our current working appliance) to their correct locations, which I assume are the same, edited the dns settings, but sadly it doesn't work. The appliance also doesn't want to keep the dns settings & keeps reverting to default. Is there any way we could have a session again? I would really appreciate it!! Thank you!!

Feb 20, 2020

Hi Garth,

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.

We'd be happy to schedule a session, if it's needed!

Feb 20, 2020

Good morning Martin,

I would appreciate a session if you have the time. I am available all of today & also next week. Thank you very much!!

Feb 27, 2020

Is this the only way I can contact you about this?

Mar 06, 2020

I understand that you must be very busy but could you perhaps make time form our issue Martin? Thx!!

Mar 23, 2020

It's been over a month since I asked for assistance with this issue. Please let me know if you till can help and if you can, when that might be...

Feb 14, 2020

After installing the ova and connecting to our VCenter 6.5 appliance, we cannot login. Getting error: "[500] An error occurred while processing the authentication response from the vCenter Single Sign-On server. Details: Empty SSO response string.
Back to login screen". Please advise what we need to do to be able to login?

Feb 20, 2020

The first thing in the checklist: are the times on the fling appliance and vCenter server in sync?

If they are and you still get this, we might need to take a look at the corresponding error that is generated after trying to login in the web client logs (under /usr/lib/vmware-vsphere-ui/server/logs/vsphere_client_virgo.log).

Feb 04, 2020

In the past this fling was updated a lot more frequently than it has been of late. Can we expect this trend to continue? Will 4.4.0 be release any time soon? Thanks guys!!

Jan 23, 2020

How do you uninstall this fling? I assume through the mob somehow?

I no longer have the appliance running but when updating certificates i'm getting an error referencing "Error while creating backup key file for h5-webclient"

Feb 20, 2020

Can you further expand on the "when updating certificates":

* Were the certificates of the previous fling appliance custom (generated by following the steps outlined in the PDF attached to this page)?
* Are you deploying a new appliance and trying to update its certificates?