Short version: when attempting to run Get-CustomCertificates (after connecting via Connect-VIServer) the following error is received:
Get-CustomCertificates : 12/27/2022 3:21:23 PM Get-CustomCertificates There was no endpoint listening at https://[FQDN]:6502/sdk that could accept the message. This is often caused by an incorrect address or SOAP action.
See InnerException, if present, for more details.
At line:1 char:1
+ Get-CustomCertificates
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-CustomCertificates], VimException
+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.DeployAutomation.Commands.GetCustomCertificates
...and I have agree with the error: I get 404'd if I go to https://[vCenterFQDN]:6502/sdk or https://[vCenterIPAddress]:6502/sdk
Is there something I need to do within vCenter to enable access to the SDK? Or...?
Long version: I'm working through the process of migrating from ESXi 6.7u3 to ESXi 80. To do this, I decided to start with fresh ESXi and vCenter installs.
Those fresh installs have been performed, and I'm wanting to update the certificates within vCenter to those issued from my own certificate authority. I'm using the VMware documentation described here to those ends, which makes use of VMware PowerCLI.
I hadn't used PowerCLI before, but was successful with doing an online install of it on my Windows 10 device.
From there, I was able to Connect-VIServer with the FQDN of my vCenter install.
The next steps in the docs suggest checking to see what custom certificates have been imported thus far, and that's the point at which I receive the above error (optional step 5b in the documentation linked-to above).
Any help appreciated - and thanks in advance,
- Nathan
