Javascript VNC client

[jonathanhoskin]

Started from a post to the mailing list by Konstantin Antipov:
http://list.xvpsource.org/mailman/private/xvp-users/msg00925.html

Konstantin has modified the existing source to use a Javascript VNC client. Maybe discuss it here?

[shadowdao]

I prefer a javascript VNC client honestly.

[jonathanhoskin]

As do I. I'd be interested to see how many users would be negatively affected by a switch from Java to JS? I suppose in the worst case the fix is only a browser-upgrade away.

[rnilssen]

If it has a long list of issues or significantly worse featureset than the java client Id cast my vote for java or for a user preference based dual solution.

[shadowdao]

I've got the files, I'm going to do some testing with it. XenServer still uses RFB as it's protocol right? That was one of the issues listed (slow speed).—
--Josh

On Sat, Jan 11, 2014 at 2:27 AM, rnilssen notifications@github.com
wrote:

If it has a long list of issues or significantly worse featureset than the java client Id cast my vote for java or for a user preference based dual solution.

Reply to this email directly or view it on GitHub:
#8 (comment)

[kantipov]

I've created a fork - https://github.com/kantipov/xvp.git
There are a new version of noVNC there - works faster.

[muralikalyan]

it includes changes only from web part, where is /etc change .conf files?

[kantipov]

You should install apache > 2.4.4 with mod_wstunnel and add location:

<Location /websockify>
ProxyPass ws://localhost:6080/
ProxyPass wss://localhost:6080/
Allow from all

Also you should run noVNC/utils/launch.sh

[muralikalyan]

Its working with apache - 80 port, but if iam try to access https its giving Server disconnected (code: 1006)

[kantipov]

There are a lot of reasons may be here. You should look javascript console for details. Also, sometimes helps simply refresh window (I wrote about this bug in xvp mailist). If you use self-signed certificate you need to add security exception.

[shadowdao]

I went ahead and built the source of XVP on CentOS6, Installed Apache 2.4.4 and put the javascript mod in place. I found a few variables were hard coded to hit kantipov xvp server( I removed them and put in the correct variable) and tried to use the mod_wstunnel, but failed.

To fix this I moved apache to localhost, and put haproxy on the public IP, directing normal traffic to apache and redirecting /websockify to NoVNC. after that it worked very well.

Maybe we should consider adding haproxy to the software stack for xvp?

[jonathanhoskin]

I've struck problems with WSS + Apache elsewhere. HAProxy sounds like the go, unless we can find a reason and/or fix for the mod_wstunnel problem?

[kantipov]

Oh, I planned to remove hardcode later, but forgot about it. Sorry guys.
And what problems do you have with mod_wstunnel?

[shadowdao]

Personally mod_wstunnel seems hit or miss, even when configured correctly.

I think if we were to put haproxy in front of apache it would protect apache from possible exploits (not to say haproxy is impervious.) and haproxy works right out of the box, and is very well documented.