VMware Support Community
adminsap
Contributor
Contributor
Jump to solution

Unable to add vCenter

Hi,

this is an another post with the well know "internal server error" when you try to add the vcenter server during the configuration process.

Couldn't create collection task to test endpoint. -> java.lang.RuntimeException: Couldn't login the client. -> Couldn't login the client. -> General failure. -> Internal server error

I try to solve the issue rebooting de skyline vm, with FQDN, with ip address, using SSO Config option, configuring Advanced Option, without SSO but the error always is the same.

2020-01-10_094644.jpg

Sorry but i have not experience with skyline, this is my first installation.

Could somebody help me?

Thanks and regards,

Reply
0 Kudos
1 Solution

Accepted Solutions
kishorenelvagal
VMware Employee
VMware Employee
Jump to solution

Hello adminsap,

Welcome to VMware communities. Thank you for posting on Skyline communities.

Based on the screenshot you have posted the error seems to be related to the configuration parameters which were added during deployment.

If you are using embedded PSC but not the default SSO domain vsphere.local

PSC/SSO Host address: Enter vCenter IP/FQDN

SSO Admin URL: https://FQDNofvCenter:7444/sso-adminserver/sdk/SSODomainName

SSO STS URL: https://FQDNofvCenter:7444/sts/STSService/SSODomainName

Lookup Service URL: https://FQDNofvCenter:7444/lookupservice/sdk/SSODomainName

If you are using External PSC and default SSO domain vsphere.local

PSC/SSO Host address: Enter PSC IP/FQDN

SSO Admin URL: https://FQDNofPSC:7444/sso-adminserver/sdk/vsphere.local

SSO STS URL: https://FQDNofPSC:7444/sts/STSService/vsphere.local

Lookup Service URL: https://FQDNofPSC:7444/lookupservice/sdk/vsphere.local

If you are using External PSC and NOT USING default SSO domain vsphere.local

PSC/SSO Host address: Enter PSC IP/FQDN

SSO Admin URL: https://FQDNofPSC:7444/sso-adminserver/sdk/SSODomainName

SSO STS URL: https://FQDNofPSC:7444/sts/STSService/SSODomainName

Lookup Service URL: https://FQDNofPSC:7444/lookupservice/sdk/SSODomainName

Please share your contact details using the following link if the problem persists.

Smartsheet Forms

Sincerely
Kishore N
VMware Support Moderator

View solution in original post

Reply
0 Kudos
3 Replies
kishorenelvagal
VMware Employee
VMware Employee
Jump to solution

Hello adminsap,

Welcome to VMware communities. Thank you for posting on Skyline communities.

Based on the screenshot you have posted the error seems to be related to the configuration parameters which were added during deployment.

If you are using embedded PSC but not the default SSO domain vsphere.local

PSC/SSO Host address: Enter vCenter IP/FQDN

SSO Admin URL: https://FQDNofvCenter:7444/sso-adminserver/sdk/SSODomainName

SSO STS URL: https://FQDNofvCenter:7444/sts/STSService/SSODomainName

Lookup Service URL: https://FQDNofvCenter:7444/lookupservice/sdk/SSODomainName

If you are using External PSC and default SSO domain vsphere.local

PSC/SSO Host address: Enter PSC IP/FQDN

SSO Admin URL: https://FQDNofPSC:7444/sso-adminserver/sdk/vsphere.local

SSO STS URL: https://FQDNofPSC:7444/sts/STSService/vsphere.local

Lookup Service URL: https://FQDNofPSC:7444/lookupservice/sdk/vsphere.local

If you are using External PSC and NOT USING default SSO domain vsphere.local

PSC/SSO Host address: Enter PSC IP/FQDN

SSO Admin URL: https://FQDNofPSC:7444/sso-adminserver/sdk/SSODomainName

SSO STS URL: https://FQDNofPSC:7444/sts/STSService/SSODomainName

Lookup Service URL: https://FQDNofPSC:7444/lookupservice/sdk/SSODomainName

Please share your contact details using the following link if the problem persists.

Smartsheet Forms

Sincerely
Kishore N
VMware Support Moderator
Reply
0 Kudos
sck1025
Enthusiast
Enthusiast
Jump to solution

2020-01-10_094644.jpg

Do you have your firewall open between your Collector and External PSC on port 443?  Not knowing your network layout that's the first thing I would check.

Skyline Collector System Requirements

Reply
0 Kudos
adminsap
Contributor
Contributor
Jump to solution

The configuration is working.

It was a misconfiguration with the SSO url's and ports.

Thank you very much for your help.

Reply
0 Kudos