Welcome to Skyline community!
Please try below steps and share the output.
- Check if we are able to ping vrops from skyline appliance?
- Check if we are able to resolve vrops FQDN from skyline appliance?
- Do we have a default or custom certificate?
- Please check vrops certificate information if the "Subject Alternate Name" is configured with FQDN or IP address.
- Try to configure vrops with the information available from SAN (FQDN/IP).
Further, if you still face challenges, let us know if we can setup webex, I would request to provide your contact details in below smart sheet to proceed.
1 person found this helpful
We had similar issue.
Skyline user password expired in vROM.
The solution was to log in with skyline user in vROM and change the password.
I hope it helps.
I'm getting the same error.
From the Skyline appliance, I can ping the vRops server by IP, and by FQDN (yes it resolves)
I can log in to vRops with the Skyline service account (set up as Read Only role in vRops)
I tried IP and FQDN in the Skyline "Add vRealize Operations" screen
(note: strangely enough, set up vSphere with FQDN as IP was failing)
I do get the yellow "Certificate thumbprint" message with either the IP or FQDN
I get a different error if I enter "domain\user" vs "user@domain"
If I enter user@domain with a bad password, I'm back to the "Endpoint test failed ...." error.
I get the same error if I use my personal account that can log into vRops.
Welcome to Skyline Communities!
There is known issue, if we are adding VROPS with read-only account.
To work around this issue please add vrops with a default admin account.
Once added, you can change the user from admin to read-only account.
I'm still getting the same error.
I gave it a bit of time, and I logged in to vRops again with the account.
Ajay was very helpful.
One of the key things that I remember was to use the actual admin account to add vRops, rather than an account with Admin role.
Then we could change the account used to the proper one.
Feedback noted. We will work on it.