Comment 4 for bug 1593672

From the evidence provided, I don't think I can say whether your issue is a match to an issue I had or not, but I'm just going to share, and see if rings any bells for you...

In a prototype instance that we were deploying by hand (first mistake, perhaps!), I failed to set my_ip correctly on one of the compute nodes. As a result, many of the consoles for virtual machines on that compute node, were reporting consoles from the machine that my_ip specified, In my case, it was my_ip that was wrong, although I expect that if you hard code the IP address in other more specific configurations, such as vncserver_proxyclient_address or others, that the symptoms would be the same.