Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I ran into the same issue and finally sorted it out with a lot of googling and trial/error. This is my setup:

controller - 10.30.177.42

running:
nova-consoleauth
nova-novncproxy

nova.conf:
novncproxy_host=0.0.0.0
novncproxy_port=6080
novncproxy_base_url=http://10.30.177.42:6080/vnc_auto.html

compute - 10.30.177.39

running:
nova-compute

nova.conf:
vnc_enabled=True
novncproxy_base_url=http://10.30.177.42:6080/vnc_auto.html
vncserver_listen=0.0.0.0
vncserver_proxyclient_address=10.30.177.39

Then I restarted all the processes and it was able to establish a connection. The hangup for me was that 'vncserver_proxyclient_address' is a setting for the compute process and is the address of the compute process that is accessible to the novncproxy process on the other machine (i.e. it needs to be an IP that the novncproxy can connect to if you have multiple networks going on the compute node). I had originally set it on the nonvcproxy side and to its IP, which was wrong. I have a feeling you're doing something similar.

I hope that helps.