VCSA 7.0 - Web Console not Connecting to VM

[Teparky]

Hi Guys,

Apologies if this is a bit of a silly question, however I have been having some issues with vCenter 7.0 and connecting to VM's remotely. 

I have configured vCenter Server behind a squid reverse proxy, every time a try to connect to a VM Console I immediately get the following error "The console has been disconnected. Close this window and re-launch the console to reconnect". 

If I attempt the same connection on the internal LAN it works perfectly fine. I have also tried putting the VC Server directly on the internet (with strict source IP Control) but this didn't seam to resolve the issue.

Does anyone know of logs (and there locations) that I can look at that might give me an insight into what is going on here and or a way of me getting around this issue?

Any help would be appreciated, I have already had a look around the internet (googled) and I haven't found anything that has resolved my issue. I have seen a nigx solution however at this stage I'm trying to avoid setting up another machine on our network.

Regards, 

[maksym007]

Could you specify again, please?
Does not work console for all VMs in the vCenter or we are talking about the Console of vCenter itself?

[Teparky]

Hi,

So I am talking about using the vCenter Web Console to connect to a VM. I have attached a screen shot to this post to help.

[Teparky]

Hi Guys,

I have been working on this issue for a while and I have managed to resolve the issue myself. 

For our reverse proxy we were using Squid 4.x which turns out doesn't handle WSS very well. We tried a few suggestions we had found online that we thought might help however the on feature that should resolve the issue is not implemented in Squid 4.x but is present in squid 5.x. We decided for testing we would switch over to HAProxy and test this for a while and see if this resolved the issue. 

Out of the box with very basic configuration this worked flawlessly and we are now able to access the vCenter Server Web Console for VM control remotely with no issues. At this stage we are not able to get the vmrc working however that is currently not important to us. 

Before anyone says it I know exposing vCenter Server directly to internet is not best practice however we do have this locked down to select IP's. 

I hope that this information helps someone else out.

Regards,

Tom