Using noVNC in the current version of Abiquo

...

The proxy we will use is called websockify and it is included in the noVNC distribution package. This software should run on a separate machine from any other Abiquo service.

When the user clicks on the eye icon, the client premium loads the VNC client (in this case noVNC) from the Abiquo Server. The Abiquo client GUI (noVNC client) requires access to the websockify proxy requires one at its public IP address on the websockify server. The noVNC clients will access this proxy via HTTP to port 41337. The websockify proxy requires HTTP access to the Abiquo API on port 80 to periodically download the hypervisor IP and Port details for the noVNC connections. . The websockify proxy also requires access to every hypervisor in your infrastructure (just like the vncproxy) and its VNC port range. 

As we are going to replace part of the platform, some small changes will be needed in order for all of this to work with the current release of Abiquo.

...

Replacing TightVNC applet with noVNC in the client-premium webapp

Download the noVNC distribution package from: http://kanaka.github.com/noVNC 

Note that this is the same package we used for the websockify

...