VMWare's "console popup" immediately goes "disconnected" on Firefox and Chrome?
 

Please don't ask me ... I didn't want the client to buy it ... :banghead:

In a VMWare "VCloud Director" virtual-machine window, when I start a VM and try to call up "Popout Console" to, (y'know ...) talk to the damned thing ... :scratch: ... I am immediately given a status of "Disconnected."

This happens both on Firefox and on Chrome, both on OS/X.

I also do not see how, in either browser, I can say ... "(!!!) it! Let these sites run anything ... any plug-in they want to run!"

I observe that I am never being asked whether I want to install a plugin or to allow it to run, and my guess is that (yet another) plugin is needed here.

Uninstall the plugin and install it again via prompting upon activating the "Popout Console"?
I show these as installed on my XP/SP3 guest using IE 8.0

VMWare Client Integration Plug-in 5.5.0
VMWare Remote Console Plug-in 5.5.1
Your OS/X may have similarly installed software packages...?

Subscribed with interest...

Edit: Mon May 23, 2016 8:51:05 AM EDT
So, I chose to "upgrade" an lo and behold, prompt to save "VMWare Client Integration Plug-in 5.5.0.exe",
a file I already have locally...
Close IE.
Navigate to saved file. Launch.
No MSI option for uninstall. Could be custom (silent) uninstall option, or perhaps just an old
packager.

"Popout Console" prompt is gone.

Hope that helps?

vCloud Director 5.6 says my interface.

New Firefox profile make any difference to "Popout Console"?

You ever get a handle on this?

I know this is a pretty old thread, but I found out what the problem was, at least for me...

When I opened the console of my browser ("developer options" or whatever) I saw a lot of SSL errors related to an untrusted certificate. I grabbed the certificate from the failing URL (in my case I was using Chrome, and that option is available in the developer options themselves) and manually added the Root CA as a trusted certificate in my operating system (Mac OS X High Sierra). Then I restarted my browser and it worked just fine.

Bottom line: probably an untrusted SSL certificate and the fix is to add the root CA to your trusted certs. I know this is a high level explanation, but I'm guessing the URL, browser and operating system make all the difference here. Good luck!