"Failed to initialilze SSL session to remote host" won't dismiss after clicking OK

[raiford]

I've seen this for quite a while (several versions of Fusion) and have never reported it.  Sometimes when I try to connect to a VM hosted on an ESXi server I get the "Failed to initialize SSL session to remote host".  This typically happens if I try to open a VM too quickly after connecting to the server.  That isn't that big of a problem - I'm happy to dismiss the message and try again.  The real problem is that it won't actually dismiss the message box until the server connection is disconnected.

If it helps I'm running "Professional Version 11.5.0 (14634996)" on macOS 10.14.5 on a 2018 MacBook Pro.

Thanks!

[raiford]

For what it's worth, this is still an issue in 11.5.1.  Once clicked, the OK button is greyed out and the message never goes away.

[aordway]

I have the same problem as well. However, I have found that if I use vcenter and Launch Remote Console using VMware Remote Console that the VM opens up fine. Before downloading VMRC I tried opening from vcenter with Fusion and got the same SSL error as just double clicking the VM in Fusion.

I am running Fusion 11.5.1 on 10.15.3 on a 2013 MacPro connecting to various ESXi servers, 6.0 - 6.7. Some of the VMs are Ubuntu and some are Windows Server 2016. I have filed a support ticket. Hopefully I will find out something since this problem has been around for years. Seems to have gotten worse for me in the last few months. Maybe Catalina??

[aordway]

I just talked with Fusion support and I am able to get around the SSL error by powering off the VM and then in Fusion powering on the VM. Of course this is not a very good solution because I can't power off a production server every time I need console access. Fusion support asked me to submit a new case for vcenter support. Since some of my ESXi servers are still on 6.0 I'll get them updated to 6.7 before proceeding with vcenter support.

[j7ody]

So I dont have much, but I investigated this a while back, possibly either when upgrading to 11, or to 10 one of the two. Anyway, the issue is AV related. I did a lot of diagnosis work and at the time could stop the issue happening by disabling realtime file scanning, or ignoring the root file system. I have eset installed and if you search for that and this error it even gives you a filepath to ignore, however that no longer works.

I have not picked it up since, however have come across similar posts with the common theme being both eset and vmware blame each other and to sort the issue out with them.

[raiford]

I recently upgraded to the latest Fusion build and this problem appears to be gone.  I've only seen one issue and that is after pulling my network cable to move my laptop.  As long as I use the system in a normal way this issue no longer appears to happen.