Ask Your Question

Why does nova-novncproxy blank screen and doesn't connect? - ignoring socket not ready

asked 2013-08-07 07:43:41 -0500

jahkeup gravatar image

updated 2013-08-07 07:44:34 -0500

Every time I try to connect to an instance's VNC console (via Horizon or nova get-vnc-console server novnc) the proxy doesn't connect and sits with a nice black screen. The log /var/log/upstart/nova-novncproxy.log reveals nothing, and the consoleauth logs show requests for the connection, but from what I can tell it looks like novncproxy doesn't do "check_token".

I have followed the instructions from the (docs). I can glean no more on the issue from elsewhere around the internet, help please! :)

Here's the services I'm running:


  • nova-{api,scheduler,conductor,novncproxy,consoleauth,cert}

  • quantum-{server,plugin-openvswitch-agent,l3-agent,dhcp-agent}

  • glance-{api,registry}

  • cinder-{api,volume,scheduler}


  • nova-compute

  • quantum-plugin-openvswitch-agent

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted

answered 2013-09-16 03:06:38 -0500

Moss gravatar image

updated 2013-12-03 11:59:38 -0500


I had exactly the same problem but only with below novnc's version:

root@controller:~# apt-cache policy novnc
      Installed: 1:0.4+dfsg+1+20130425+git4973b9cc80-1~bpo70+1
      Candidate: 1:0.4+dfsg+1+20130425+git4973b9cc80-1~bpo70+1
      Version table:
         1:0.4+dfsg+1+20130425+git4973b9cc80-1~bpo70+1 0
            500 grizzly/main amd64

The solution was to reinstall novnc to below version:

root@controller:~# apt-cache policy novnc
      Installed: 2012.2~20120906+dfsg-0ubuntu4~cloud0
      Candidate: 1:0.4+dfsg+1+20130425+git4973b9cc80-1~bpo70+1
      Version table:
         1:0.4+dfsg+1+20130425+git4973b9cc80-1~bpo70+1 0
            500 grizzly/main amd64
     *** 2012.2~20120906+dfsg-0ubuntu4~cloud0 0
            500 precise-updates/grizzly/main amd64

root@controller:~# dpkg -s novnc
        Package: novnc
        Status: install ok installed
        Priority: optional
        Section: web
        Installed-Size: 324
        Maintainer: Ubuntu Developers <>
        Architecture: amd64
        Version: 2012.2~20120906+dfsg-0ubuntu4~cloud0

I'm using grizzly's nova-novncproxy:

root@controller:~# apt-cache policy nova-novncproxy
  Installed: 1:2013.1.2-0ubuntu1~cloud0
  Candidate: 1:2013.1.2-0ubuntu1~cloud0
  Version table:
 *** 1:2013.1.2-0ubuntu1~cloud0 0
        500 precise-updates/grizzly/main amd64

VNC's section of Controller's nova.conf:

novncproxy_base_url =

VNC's section of Compute's nova.conf:


This is my topology:

OpenStack OVS Multinode

edit flag offensive delete link more

answered 2013-08-14 14:22:27 -0500

kesten gravatar image

updated 2013-08-14 14:55:30 -0500

I have the same issue and, quite oddly, and when I click the "Send Ctrl+Alt+del" button, all of a sudden the console springs into action showing that it was sitting at the login prompt, and then going through the shutdown commands all of which are now visible in the vnc console.

I'm running a centOS6.4 vm spun up from a vmdk image hosted on glance. Openstack controller node is hosted on a dedicated vm server, connecting to it from my mac using firefox 23. The log tab shows "?"

With a cirros vm, the log also shows a correct bootup log, but the console still doesn't work.

It may be as simple as - click on the black console. Start typing. When i do this, the console starts displaying output. Cheeky monkey!

Spoke too soon. The horizon console wasn't working by itself. It needed help. Here's what worked for me.

Use the dashboard to view instances, click on yours. Summary tab. Get the id.
controller $ nova get-vnc-console 1cc5f95b-8793-4ab4-864b-d83b2d742bd7 novnc

+-------+---------------------------------------------------------------------------------+ | Type | Url | +-------+---------------------------------------------------------------------------------+ | novnc | | +-------+---------------------------------------------------------------------------------+

Take the url, put it in a new tab in your browser. Now start typing and your console may work. If you go back to the horizon controlled console, it may now have started to work. If you kill the url from nova, the horizon console may die. Note that if your session dies you may have to go to the instances page, click edit or more. Soft or hard reboot the instance. Generate a new url via nova. Bit clunky.


edit flag offensive delete link more

answered 2013-10-08 14:03:47 -0500

smkr gravatar image

hi there, this is quite stupid but since I've spent a good hour searching elsewhere: my problem was with using Vimperator Firefox plugin, you must temporarily disable vimperator (<insert> or <s-esc>) then just click on the grey bar and start typing as suggested in the other comments</s-esc></insert>

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2013-08-07 07:43:41 -0500

Seen: 3,620 times

Last updated: Dec 03 '13