VM Explorer Practitioner Forum
cancel

ESX Connect Error: The request was aborted: Could not create SSL/TLS secure channel.

Highlighted
JBR2
Frequent Contributor.

ESX Connect Error: The request was aborted: Could not create SSL/TLS secure channel.

Since upgrading one of our ESXi Host servers from v4.1 to v6.0,  the server shows as "(Disconnected)" in the VM Explorer "My DataCentre" view and backup tasks are failing.  (We are using the free edition of ESXi without vCenter). 

When I re-run the VM Explorer "Edit Server" wizard, the "Test Connection" stage fails with the following error:
"ESX Connect Error: The request was aborted: Could not create SSL/TLS secure channel."

Please find attached a screenshot.

However, the vSphere Client v6.0 successfully connects to the ESXi Host. 

SSH is enabled and I have tried re-starting the Management Agents in the ESXi Direct Console User Interface (DCUI). I have also tried enabling the ESXi Shell without success.

My next thought is to re-generate the SSL certificate on the ESXi host but can't see why that would have any effect if the vSphere Client is working ok.

I would be grateful for any help re the meaning of the error messages above and possible solutions.

Thanks.

 

 

2 REPLIES
MichaelFunke
Honored Contributor.

Re: ESX Connect Error: The request was aborted: Could not create SSL/TLS secure channel.

Did the ESXi Server get a new IP address and/or hostname?

JBR2
Frequent Contributor.

Re: ESX Connect Error: The request was aborted: Could not create SSL/TLS secure channel.

No, the IP address and hostname remained the same during the upgrade process.

However, another couple of clues:

1) I have tried installing another copy of VM Explorer on another system and that connects successfully to the ESXi Host.  So that means there can't be a problem with the ESXi Host.

2) I then tried using a different browser (IE) in case Chrome was caching something but the problem persisted.

3) I tried deleting the ESXi Host from the My Datacenter list and re-adding the server but still the problem persists. 

I am sure the solution is staring me in the face but I have given in and opened a case with HP...