VMWareProbe failing: Unable to establish connection to https://<IP>/sdk

[cloudyrobert]

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.

[cloudyrobert]

Looked at this too. The payload shows that it used the correct VMWare credential, and the cred is pre-fixed with the domain.

[cloudyrobert · Accepted solution]

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...

[Ashutosh Munot1]

Oh Yes, You cant have oauth active in credentials table. 

Best luck.

Thanks,
Ashutosh

[HugoMeeuwes]

Although the issue was reported here almost 3 years ago, I ran into it recently and could not find the solution online. Eventually I found a fix:

On the credential record, set 'Applies to: Specific MID servers' and add the correct MID Server(s). This resolved the issue for me. Having the vCenter credential apply to all MID Servers somehow does not work for vCenter discovery anymore.