参考下这个：https://ask.openstack.org/en/question/520/vnc-console-in-dashboard-fails-to-connect-ot-server-code-1006/内容如下：controller - 10.30.177.42running:
nova-consoleauth
nova-novncproxynova.conf:
novncproxy_host=0.0.0.0
novncproxy_port=6080
novncproxy_base_url=http://10.30.177.42:6080/vnc_auto.htmlcompute - 10.30.177.39running:
nova-computenova.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.39Then I restarted all the processes and it was able to establish a connection. The hangup for me was that 'vncserverproxyclientaddress' 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.
nova-consoleauth
nova-novncproxynova.conf:
novncproxy_host=0.0.0.0
novncproxy_port=6080
novncproxy_base_url=http://10.30.177.42:6080/vnc_auto.htmlcompute - 10.30.177.39running:
nova-computenova.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.39Then I restarted all the processes and it was able to establish a connection. The hangup for me was that 'vncserverproxyclientaddress' 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.
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货