I've got an OpenStack deployment running inside a VM for testing purposes. My setup is as follows: Host Ubuntu x64 with Virtualbox -> Guest Ubuntu x64 with OpenStack -> Ubuntu X64 Server Test Instances through Openstack.

I realize it is of no practical use, but as said, it is for testing purposes only. I successfully launched an instance, binding it to and (host is and I can successfully ssh into it from either the host or the guest VM with ssh -i key.pem ubuntu@ (or Unfortunately, the NoVNC via Horizon does not work (Starting VNC handshake -> Failed to connect).

The relevant lines from my nova.conf are the following:


So I'm not sure what's going wrong. The keypair that matches the .pem file I ssh with is of course coupled with the instance, and the instance is Active and Running.

Any help would be greatly appreciated.

Edit: nova get-vnc-console [id] novnc correctly supplies me with a link to vnc into the vm, but it also fails to connect.

Edit 2: To clarify: I have an active, running instance that successfully launched through the OpenStack dashboard. I can ping the instance, I can ssh into it (using 'ssh -i key.pem ip), but I cannot access it through VNC (specifically novnc on the dashboard). Trying to access the VM through the URL nova supplies through get-vnc-console does not work either. What I wish to do is access this instance via VNC.

  • So is your question about VNC on openstack or VMz not being reachable. – Chakri Apr 5 '13 at 20:56
  • Sorry if it was a little unclear: I added clarification as to what I meant. I wish to access the instance via VNC, but cannot as of right now. – user991710 Apr 5 '13 at 21:21

I think your URL reference should be your public IP.



Try that.

  • Could you elaborate on that slightly? In my nova.conf above, I have: --novncproxy_base_url=, with being the VM's (= the system running Openstack services) public IP address as far as it is concerned. Am I missing something? – user991710 Apr 5 '13 at 21:40

Put --vncserver_listen= instated of --vncserver_listen= in your configuration. Restart relevant services then try to access the instance via VNC. It should work.


Try this on the compute node you want to access from NoVNC

iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 5900:5950 -j ACCEPT
iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited

If this is the right solution save it


Hope you can find the solution. Regards Gerardo

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.