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.
What's the difference between this and the ESXi embedded client? https://flings.vmware.com/esxi-embedded-host-client
Does it work with vSphere or something?
The embedded host client is made for managing a single host, and it's also now shipping directly with ESXi 6.0U2.
The vSphere HTML5 Web Client works with vCenter (and will ONLY work with vCenter, not individual ESXi Hosts).
With windows vcenter i have this message when i go to https://vcenterweb:9443/ui/login
HTTP Status 400 - An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
Problem with certificat ?
I have a selfsign certificat on my vcenter
This error is new to me.
Did you already do the 'add your dns to /etc/resolv.conf' steps? They were recently added to the instructions.
Can you, from the H5client appliance:
1) Ping the vCenter using IP address
2) Ping the vCenter using domain name
and if you have an external PSC
3) Ping the PSC using IP
4) Ping the PSC using domain name
resolv.conf OK, I can ping google.fr
From the H5client appliance:
1) Ping the vCenter using IP address OK
2) Ping the vCenter using domain name OK
We don't have an external PSC
Server-configure.bat create other file where not used in configuration : store, keyfile, certfile, ... it's normal ?
You should only need the 3 files from the .bat output, and they're all highlighted in the instructions.
webclient.properties, ds.properties, and store.jks
Please check on the h5client appliance that they're all in the expected locations after you copied them from the Windows vCenter:
i) /etc/vmware/vsphere-client/store.jks OK
ii) /etc/vmware/vsphere-client/config/ds.properties OK
iii) /etc/vmware/vsphere-client/vsphere-client/webclient.properties OK
Can you run "/etc/init.d/vsphere-client tail_log" on the h5client appliance and email me the results?
You should be able to find my email address by searching for 'vmware.com' on this page.
email sent with log file
You can add the Custom Attributes and Tags display
Definitely on our list for later!
I've got the h5client appliance set up with a windows vCenter 6.0 U1 server, installed it following the instructions, but it doesn't let me log in using the admin account I use for the regular webclient. Error: Unable to authenticate user. Please try again.
Logging in with the root account works, all settings like dns and time are ok. Any idea why it fails to log me on? Any logs I can check? First feedback tip: On the root config webpage, add a button to check the vcenter connection.
And something else, when checking for updates I got this error:
Failed to check for updates(Error validating the digital signature of the update manifest. Please contact your vendor.) on Thursday, 2016 April 07 11:22:26 UTC+2
"When checking for updates" - Where are you doing this?
You can try running "/etc/init.d/vsphere-client tail_log" on the H5client appliance and see if there's any errors there.
Your situation does sound weird though. Can you try pinging your PSC from the H5client appliance, maybe that's the issue?
I've checked for updates by logging in with the root account on the web page, choosing the update tab and pressing the button Check Updates.
I can ping the PSC, that's not an issue.
The only entries I see using the vsphere-client tail_log command are core dump rotations every hour. If I attempt to login on the webpage, nothing is logged.
Can you email me your webclient.properties file (feel free to obscure whatever you need)?
You should find my email in an earlier comment on this page (search for vmware.com)
Same error here when doing an update through the interface on 5480:
Failed to check for updates(Error validating the digital signature of the update manifest. Please contact your vendor.) on Thursday, 2016 April 14 20:54:54 UTC+2
We don't support updating through the 5480 UI, it's actually designed for a different use. I misread this before.
The instructions for updating are available in the Instructions tab on this page, or under "Upgrade Flow" in the instructions pdf. It involves manually downloading the rpm to the appliance and then applying it. We will improve this flow in the future.