The novnc-server will translate WebSockets traffic to normal socket
traffic, therefore you don't have to expose the host IP to the final user,
she will interact with the proxy.
Cheers
On 10 February 2015 at 11:33, Nico Schottelius
nico-opennebula@schottelius.org wrote:
Hey,
I think I
Hey Daniel,
thanks for following up - I will lock down vnc ports to to only
allow access from the frontend to this a try today!
Cheers,
Nico
Daniel Molina [Fri, Feb 13, 2015 at 09:17:55AM +0100]:
The novnc-server will translate WebSockets traffic to normal socket
traffic, therefore you don't
Hi,
Are you using the novnc-server included in OpenNebula? This component uses
a websocket proxy, so that you don't have to expose the VNC socket to your
users, and it will take care of the different tcp sockets.
Cheers
On 6 February 2015 at 12:50, Nico Schottelius
Hey,
I think I haven't (at least I didn't enable it explicitly).
If the novnc-server is enabled, how do I configure the templates?
Because at the moment, vnc listens to 0.0.0.0 and is accessible if
someone knows the IP and port.
Cheers,
Nico
Daniel Molina [Tue, Feb 10, 2015 at 10:54:36AM
Good day,
we are about to setup our fourth hosting plattform in the next weeks,
based on opennebula 4.10.2, ubuntu 14.0 and gluster 3.x (x ~= 4..6).
In our tests the VNC socket of the VMs has been exposed on the hosts
directly accessible on 0.0.0.0 - for everyone. Given that sunstone
will be
