I just upgraded my 2.0Beta instance to 2.0GA and was looking at the inventory dashboard and noticed that the number of vCenters connected was 0.
I figured I need to update the password, so I did and when I tested the password I got:
HTTP transport error: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificates does not conform to algorithm constraints
I was working on a separate problem with someone trying to connect a tool the vcenter and they had a certificate error as well, I think it may have to do with this KB
This is an old vCenter that has been upgraded over time. It is as 5.5GA
I was able to add another vCenter that is 5.5u1 that has a 2048 bit cert.
Check the certificate of your old vCenter, this need to be at least 1024-bit, if not you can modify the Log Insight to support 512-bit as a workaround.
Check this thread for more info: vCenter not connecting after upgrade to 2.0
Check the certificate of your old vCenter, this need to be at least 1024-bit, if not you can modify the Log Insight to support 512-bit as a workaround.
Check this thread for more info: vCenter not connecting after upgrade to 2.0
That was my suspicion since I ran into a similar issue with the other tool. Thanks for pointing out the other thread!