A fresh vCD 8.1 install is having issues with console access to VMs within a vDC. I'm using a shared IP for the cell, https on one port and console proxy on another. Both NATed from public network to the private DMZ. All vCD config uses the private IP or the vCD Cell server.
vCD is installed on a CentOS 7 server
When I open a console in Chrome, I get "Disconnected" and just a white popup with some options at the top (Power on etc)
In the Developer console (F12) I see:
WebSocket connection to 'wss://EXTERNAL-FQDN/902;cst.........' failed: Error during WebSocket handshake: Unexpected response code: 404
I'm not using port 902 for HTTPS or the Proxy Console, so suspect this is something to do with communication between VDC and VC/ESXi
The console proxy port isn't showing up on the perimeter firewall logs but the HTTPS port set for the UI is, so perhaps the console proxy traffic is encapsulated within the HTTPs traffic? -- Not sure on this one really.
Have tried disabling the vCD server firewall
There is nothing in cell.log
The console-proxy.log file just shows a successful bind of the console port to the interface.
There are no certificate errors on the page (All signed by a trusted CA)
On the IE developer console, I'm getting "Connecting...", a black screen and the below, which is pointing to a possible certificate issue but I can't think where the problem could be other than that I'm using a wildcard SSL cert on for the FQDN?
An error occurred that affected the security of the connection
If I log out and back in again, then open up a console I sometimes get this in the IE developer console:
Object doesn't suport property or method "isReadyToStart"
After reading this vCloud and wildcard cert, it looks like wildcard certs are okay to use now so I'm at a loss!
Any advice is appreciated.