Comment by Deepa for I have the VNC console working, but in the openstack dashboard, it does not load and shows an error code 1006 instead. If I click to show only the console, then it loads. Nova logs on the controller when getting code:1006 on the dashboard: ==> /var/log/nova/nova-consoleauth.log <== 2018-04-24 10:23:58.894 3109 INFO nova.consoleauth.manager [req-41c322e4-76b7-47a3-aa10-27de67b47568 8bf003cdf58a4233b7e279aee1eec593 ee5d821a39174d8a91e3a741a6ecd97e - default default] Received Token: a634ec8f-c7db-45e2-8fc2-851340bb8ad3, {'instance_uuid': u'5f6785ff-f592-4f68-88a4-3ad512a959f2', 'access_url': u'http://controller:6080/vnc_auto.html?token=a634ec8f-c7db-45e2-8fc2-851340bb8ad3', 'token': u'a634ec8f-c7db-45e2-8fc2-851340bb8ad3', 'last_activity_at': 1524579838.89435, 'internal_access_path': None, 'console_type': u'novnc', 'host': u'192.168.116.23', 'port': u'5900'} ==> /var/log/nova/nova-novncproxy.log <== 2018-04-24 10:23:59.647 9358 INFO nova.console.websocketproxy [-] 192.168.116.22 - - [24/Apr/2018 10:23:59] 192.168.116.22: Plain non-SSL (ws://) WebSocket connection 2018-04-24 10:23:59.648 9358 INFO nova.console.websocketproxy [-] 192.168.116.22 - - [24/Apr/2018 10:23:59] 192.168.116.22: Version hybi-13, base64: 'False' 2018-04-24 10:23:59.649 9358 INFO nova.console.websocketproxy [-] 192.168.116.22 - - [24/Apr/2018 10:23:59] 192.168.116.22: Path: '/websockify' 2018-04-24 10:23:59.769 9358 INFO nova.console.websocketproxy [req-261346a6-84eb-4829-bdc6-b85f53939786 - - - - -] handler exception: The token 'a634ec8f-c7db-45e2-8fc2-851340bb8ad3' is invalid or has expired The same logs when successfully showing only the console: ==> /var/log/nova/nova-consoleauth.log <== 2018-04-24 10:25:04.291 3109 INFO nova.consoleauth.manager [req-7926032b-fcd7-490e-8f0e-99b5bccef8da - - - - -] Checking Token: a634ec8f-c7db-45e2-8fc2-851340bb8ad3, True ==> /var/log/nova/nova-novncproxy.log <== 2018-04-24 10:25:04.589 9513 INFO nova.console.websocketproxy [req-7926032b-fcd7-490e-8f0e-99b5bccef8da - - - - -] 8: connect info: {u'instance_uuid': u'5f6785ff-f592-4f68-88a4-3ad512a959f2', u'internal_access_path': None, u'last_activity_at': 1524579838.89435, u'console_type': u'novnc', u'host': u'192.168.116.23', u'token': u'a634ec8f-c7db-45e2-8fc2-851340bb8ad3', u'access_url': u'http://controller:6080/vnc_auto.html?token=a634ec8f-c7db-45e2-8fc2-851340bb8ad3', u'port': u'5900'} 2018-04-24 10:25:04.590 9513 INFO nova.console.websocketproxy [req-7926032b-fcd7-490e-8f0e-99b5bccef8da - - - - -] 8: connecting to: 192.168.116.23:5900 The [vnc] section of /etc/nova/nova.conf on the controller my_ip = 192.168.116.21 [vnc] enabled = true vncserver_listen = $my_ip vncserver_proxyclient_address = $my_ip novncproxy_host = 192.168.116.21 The [vnc] section of /etc/nova/nova.conf on the controller my_ip = 192.168.116.23 [vnc] enabled = true vncserver_listen = 0.0.0.0 vncserver_proxyclient_address = $my_ip novncproxy_base_url = http://controller:6080/vnc_auto.html The connection to the controller is also going through HAProxy. I wouldn't expect this to be an issue as the console does partially work, but I thought I would include this detail anyway if there could be an issue with this.

$