[Openstack-operators] Essex VNC problem

livemoon mwjpiero at gmail.com
Fri Apr 20 14:08:56 UTC 2012


Hi,

I think you need use noVNC in essex:
https://github.com/cloudbuilders/noVNC

it should be set in nova.conf like this:
--novncproxy_base_url=http:// 192.168.111.51 :6080/vnc_auto.html
--xvpvncproxy_base_url=http:// 192.168.111.51 :6081/console
--vncserver_listen= 192.168.111.51
--vncserver_proxyclient_address= 192.168.111.51

On Fri, Apr 20, 2012 at 4:07 PM, Sergio Ariel de la Campa Saiz <
sacampa at gmv.com> wrote:

>  Hi:
>
> I have installed Essex and it looks like it works
> ok, except for the fact that I´m unavailable to connect to
> my instance using VNC. I hope you can help me and I
> hope this thread will be usefull to others too :-)
>
> This is what I have in my nova.conf file
> --vncserver_host=0.0.0.0
> --vncproxy_url=http://192.168.111.51:6080
>
> (192.168.111.51 is my public IP for the Ubuntu server in wich nova runs.)
>
> I have installed nova-vncproxy package and started it, but when I
> try to connect to an instance using dashboard, I get this message:
> "VNC console is currently unavailabe. Please try again later"
>
>
> Thanks a lot and sorry for bothering.
>
>    *Sergio Ariel *
>
> *de la Campa Saiz*
>
> GMV-SES Infraestructura /
> GMV-SES Infrastructure
>
>
>
>
>
>
>
> *GMV*
>
> Isaac Newton, 11
> P.T.M. Tres Cantos
> E-28760 Madrid
> Tel.
>
> +34 91 807 21 00
> Fax
>
> +34 91 807 21 99
> www.gmv.com
>
>
>
>
>
>
> ------------------------------
> This message including any attachments may contain confidential
> information, according to our Information Security Management System, and
> intended solely for a specific individual to whom they are addressed. Any
> unauthorised copy, disclosure or distribution of this message is strictly
> forbidden. If you have received this transmission in error, please notify
> the sender immediately and delete it.
> ------------------------------
> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información clasificada por su emisor como confidencial en el
> marco de su Sistema de Gestión de Seguridad de la Información siendo para
> uso exclusivo del destinatario, quedando prohibida su divulgación copia o
> distribución a terceros sin la autorización expresa del remitente. Si Vd.
> ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y
> proceda a su borrado. Gracias por su colaboración.
> ------------------------------
> Esta mensagem, incluindo qualquer ficheiro anexo, pode conter informação
> confidencial, de acordo com nosso Sistema de Gestão de Segurança da
> Informação, sendo para uso exclusivo do destinatário e estando proibida a
> sua divulgação, cópia ou distribuição a terceiros sem autorização expressa
> do remetente da mesma. Se recebeu esta mensagem por engano, por favor avise
> de imediato o remetente e apague-a. Obrigado pela sua colaboração.
> ------------------------------
>
> _______________________________________________
> Openstack-operators mailing list
> Openstack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
非淡薄无以明志,非宁静无以致远
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120420/260de5ec/attachment-0002.html>


More information about the Openstack-operators mailing list