After the nova hosts file deliberately deleted the resolution of the controller domain name, I remembered why the yin link web vnc url needs to be modified to the controller ip to open the web vnc web page.
novncproxy_base_url = http://controller:6080/vnc_auto.html
Default vnc webpage
When the controller cannot parse out the ip or resolves to the wrong old ip, naturally this web vnc webpage cannot be opened.
Beixin vnc is also the vnc_auto.html of this 6080 webpage http://controller:6080/vnc_auto.html
[Uh, I watched this video https://www.bilibili.com/video/BV1LJ411Y7og?p=12 The web vnc cannot be opened. It may be that the current windows cannot resolve the controller domain name. Then you can add windows to the hosts analysis or write like UnionPay ip so it may be caused by that the Windows machine of the UnionPay application publishing machine cannot resolve the domain name]
