However, regarding the nova.conf flag in point #3, I can see this text in the manual:
o enable vncproxy in your cloud, in addition to running one or both of the proxies and nova-consoleauth, you need to configure the following options on your compute hosts.
.....
novncproxy_base_url=[base url for client connections] defaults to http://127.0.0.1:6080/vnc_auto.html. This is the public base url to which clients will connect. ?token=abc will be added to this url for the purposes of auth. When using the system as described in this document, an appropriate value is http://$SERVICE_HOST:6080/vnc_auto.html where SERVICE_HOST is a public hostname.
Hi,
Thanks for the report!
I have submitted a fix for point #2 at: https:/ /review. openstack. org/#/c/ 6858/
However, regarding the nova.conf flag in point #3, I can see this text in the manual:
o enable vncproxy in your cloud, in addition to running one or both of the proxies and nova-consoleauth, you need to configure the following options on your compute hosts. base_url= [base url for client connections] defaults to http:// 127.0.0. 1:6080/ vnc_auto. html. This is the public base url to which clients will connect. ?token=abc will be added to this url for the purposes of auth. When using the system as described in this document, an appropriate value is http:// $SERVICE_ HOST:6080/ vnc_auto. html where SERVICE_HOST is a public hostname.
.....
novncproxy_
Is it possible that you just missed this ?
Regards,
Tom