
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2020 09:10 AM
Anyone solved this Discovery issue? Historically, we've successfully discovered our vCenters, but it's stopped working relatively recently. We're getting:
Unable to establish connection to https://<IP>/sdk |
We attempted the guidance in this KB under 'Probe "VMWare - vCenter Datacenters" fails with "Unable to establish connection to https:///sdk"'. We're able to "successfully" hit /sdk from the browser on the MID host. I put that in quotes, because it's not a web server, so you don't really get a page. We're able to successfully log into /mob using the same domain credentials that we're using with Discovery.
Edit 1:
Looked at this too. The payload shows that it used the correct VMWare credential, and the cred is pre-fixed with the domain.
Edit 2:
We're seeing the error "SEVERE *** ERROR *** An error occurred while decrypting credentials from instance" in our MID logs. This isn't OAuth, but wonder if this is relevant. We're patching to New York Patch 8 in less than a week, but we're not there yet.
Edit 3:
We just ran into this orphaned record issue with the connection table related to an integration after a clone due to the preservers only being set up for the child tables, but I don't think that's the issue here. I can open the credential records as I would expect.
Edit 4:
Just in case... I deleted the keystore & re-validated the MID server.
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-11-2020 04:28 AM
HI is saying it's this: An error occurred while decrypting credentials from instance - Creating OAuth 2.0 credential results....
Upgrading to Patch 8 shortly, so we will see...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2020 09:29 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2020 10:20 AM
Linux

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2020 12:17 PM
HI,
Few things to check then:
1) Port 9443 and 5480.
2) You need to authenticate with that Linux machine.
3) Dont worry if the Linux machine is not discovered if the ports are open all vcenter probes will automatically trigger.
Thanks,
Ashutosh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-11-2020 04:27 AM
Thanks, Ashutosh.
1 - Both ports are open.
2 & 3 - We have VMware creds in place, and they've historically worked. The probe is triggering; it's just not succeeding in doing much of anything.