VMware Horizon Community
BungeBash
Enthusiast
Enthusiast
Jump to solution

View 7 vCenter Server Can't Verify Certificate

We have a vCenter 6 and a vCenter 5.5 instance.  vCenter 6 let's me verify the default self-signed cert. vCenter 5.5 when you click verify does nothing.  When you go to servers, and edit the 5.5 it always gives this error:

"Possibly an invalid vCenter Server certificate. Please verify the identity of the associated vCenter Server."

I have tried uninstalling and reinstalling composer again to no avail.  The "View Composer Servers" let's me verify the certificate.  I'm guessing another bug with Horizon View 7.

1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

It's actually not a bug. You may need to follow http://pubs.vmware.com/horizon-7-view/topic/com.vmware.ICbase/PDF/view-70-installation.pdf  and enable TLSv1.0 on the Connection Server as well as on the Composer.

André

View solution in original post

Reply
0 Kudos
8 Replies
a_p_
Leadership
Leadership
Jump to solution

It's actually not a bug. You may need to follow http://pubs.vmware.com/horizon-7-view/topic/com.vmware.ICbase/PDF/view-70-installation.pdf  and enable TLSv1.0 on the Connection Server as well as on the Composer.

André

Reply
0 Kudos
BungeBash
Enthusiast
Enthusiast
Jump to solution

Already followed that. Did not resolve the issue

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Hm, I did this today and it worked perfectly.

Do you see any errors in the log files?

André

Reply
0 Kudos
BungeBash
Enthusiast
Enthusiast
Jump to solution

Actually, where do you enable this on the connection server? I only have it enabled on the Composer server.  Also, I'll have to go looking for the logs associated with this error.

Reply
0 Kudos
BungeBash
Enthusiast
Enthusiast
Jump to solution

I'm still seeing this in logs:

2016-03-24T19:55:46.894-04:00 ERROR (1304-18F8) <VirtualCenterDriver-ed911b57-304e-4230-9dc2-7bbe8e3d07bd> [ServiceConnection25] Problem connecting to VirtualCenter at https://FQDN:443/sdk (javax.net.ssl.SSLHandshakeException: Server chose TLSv1, but that protocol version is not enabled or not supported by the client.)

2016-03-24T19:55:46.894-04:00 WARN  (1304-18F8) <VirtualCenterDriver-ed911b57-304e-4230-9dc2-7bbe8e3d07bd> [VirtualCenterDriver] Unable to establish a connection with VC <https://FQDN:443/sdk> using VIM 2.5 binding

Even though I have had those registry settings set.  I'm also curious if something similar is why HTML (doesn't even get to the login prompt) and some of the webpages like the admin page don't work in Chrome. 

Reply
0 Kudos
BungeBash
Enthusiast
Enthusiast
Jump to solution

Thank you actually!  I didn't realize I missed the adsi piece to do on the connection servers. Finally did that and it fixed it!

Now the only issue I have is Chrome refuses to work with the admin page or HTML client.  Others are having that issue too.

Reply
0 Kudos
JoaoCastro
Enthusiast
Enthusiast
Jump to solution

Please i have the same problem also created a register key in vmware composer and connection server, but i cant add vcenter yet ..

Do you have any ideia what i can do ?

Regards,

Joao castro

Reply
0 Kudos
sarunpk6
Contributor
Contributor
Jump to solution

Enable TLSv1.0 on Horizon view connection Server.

Tech Kiranangal: Horizon 7: Add Vcenter 5.5 U2 Fails with Certificate Error

Reply
0 Kudos