VMware Support Community
JK926
Contributor
Contributor
Jump to solution

Unable to add vCentre endpoint.

I am attempting to configure Skyline. I am in the vCenter configuration section. I have put in the vCenter address and filled out the RO user credentials. When I click Continue I see: The certificate provided by your vCenter is not valid (Certificate Thumbprint [1c1e2085ca8fa309e5dcad61b145ec89964e3a99]).

Press "CONTINUE" if you would like to continue using an invalid certificate

I press Continue and I get: Endpoint test failed. Error message: Couldn't create PropertyCollector facade for getting the VC UUID -> java.lang.RuntimeException: Couldn't login the client. -> Couldn't login the client. -> General failure. -> org.apache.http.conn.HttpHostConnectException: Connect to 10.1.252.24:7444 [/10.1.252.24] failed: Connection refused (Connection refused) -> Connect to 10.1.252.24:7444 [/10.1.252.24] failed: Connection refused (Connection refused) -> Connection refused (Connection refused)

I have an separate VM with the  PSC/SSO. I have tried using the Custom SSO configuration both on and off with the same results.

Error received when FQDN of VC and PSC was used.

Endpoint test failed. Error message: Couldn't create PropertyCollector facade for getting the VC UUID -> java.lang.RuntimeException: Couldn't login the client.

-> Couldn't login the client. -> Error communicating to the remote server https://10.1.252.205:7444/sts/stsservice/vsphere.local ->

Error communicating to the remote server https://10.1.252.205:7444/sts/stsservice/vsphere.local -> HTTP transport

error: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names matching IP address 10.1.252.205 found -> java.security.cert.CertificateException:

No subject alternative names matching IP address 10.1.252.205 found -> No subject alternative names matching IP address 10.1.252.205 found.

Any assistance is greatly appreciated.

Regards,

Jim

1 Solution

Accepted Solutions
PDM_cbujak
Enthusiast
Enthusiast
Jump to solution

I have a similar error when adding my vCenter

Endpoint test failed. Error message: Couldn't create PropertyCollector facade for getting the VC UUID -> java.lang.RuntimeException: Couldn't login the client. -> Couldn't login the client. -> Error communicating to the remote server https://FQDN/sts/STService/vsphere.local -> Error communicating to the remote server https://FQDN/sts/STService/vsphere.local -> The server sent HTTP status code 404: null

I have 4 v6.5 PSC appliances, served by 2 load-balanced addresses.  This error is present if I use the load-balanced address or the direct address.

The install document specifies that with v6.5 you only need port 443 to the PSC.  But in the config it references port 7444.  Is this port needed for v6.5?

PM me for EA and company name

View solution in original post

0 Kudos
4 Replies
HarishV
Enthusiast
Enthusiast
Jump to solution

Hello Jim,

Thank you for the post.

Please provide your EA number and the company name. I will check this in the backend and update you.

Sincerely Harish Venkatachalam Skyline Support Moderator
0 Kudos
PDM_cbujak
Enthusiast
Enthusiast
Jump to solution

I have a similar error when adding my vCenter

Endpoint test failed. Error message: Couldn't create PropertyCollector facade for getting the VC UUID -> java.lang.RuntimeException: Couldn't login the client. -> Couldn't login the client. -> Error communicating to the remote server https://FQDN/sts/STService/vsphere.local -> Error communicating to the remote server https://FQDN/sts/STService/vsphere.local -> The server sent HTTP status code 404: null

I have 4 v6.5 PSC appliances, served by 2 load-balanced addresses.  This error is present if I use the load-balanced address or the direct address.

The install document specifies that with v6.5 you only need port 443 to the PSC.  But in the config it references port 7444.  Is this port needed for v6.5?

PM me for EA and company name

0 Kudos
PDM_cbujak
Enthusiast
Enthusiast
Jump to solution

As I was re-reading my post I noticed the typo in the STSService URL.

I'm leaving my reply post so that others know to double-check.

ashwin_prakash
VMware Employee
VMware Employee
Jump to solution

Hello

Thank you for sharing the update.

We understand that you were able to configure Skyline Collector with vCenter server after correcting the changes on the STSService URL.

Now the collector would be working fine without any issues.

Sincerely,
Ashwin Prakash
Skyline Support Moderator
0 Kudos