Hello,
bad news: noVNC uses websockets to open a connection to a tcp port on the
sunstone frontend which your reverse proxy is probably not letting
through. Actually, this port depends on the VM ID that you are connecting
to (proxy_base_port + vm_id), so as things are now there is no
straightforward way that you can get Sunstone VNC working with a reverse
proxy solution unless you take care of proxying a wide range of ports, or
find a way to let the connections through directly to them.
good news: We realised of this limitation and this will be changed for the
next release as part of http://dev.opennebula.org/issues/1209. The idea is
that we run a single websockets proxy instance on a single fixed port.
So im afraid you just need to wait some weeks,
Hector
En Thu, 31 May 2012 21:51:48 +0200, Alberto Zuin - Liste
<li...@albertozuin.eu> escribió:
Hello all,
I'm setting up a new cloud (little, but this time it's mine ;-) with
OpenNebula 3.4.1.
Sunstone works like a charm when connecting directly on port 9869, but I
want using Lighttpd for ssl proxy. In this situation there is a problem
using NoVNC web console: when I click on the icon, appear the popup on
the bottom but no console.
No error in lighttpd log and in sunstone log.
Any suggestions?
Thanks,
Alberto
--
Hector Sanjuan
OpenNebula Developer
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
