Re: Disable Websocket

[yozh <st...@gmail.com>]

Hello,

I brought this up before, but never got an answer. How do I disable
websockets and use HTTP tunnel ? I`m using nginx as a proxy for port 80, and
it doesnt seem to fall back to HTTP, just times out since websense is
blocking websockets. How to I force to use HTTP ?



--
Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/

Re: Disable Websocket

[yozh <st...@gmail.com>]

Thank you for the reply. They are also doing HTTPS inspection so it does not
help... I was able to get ws to fail and it does fall back to the HTTP
tunnel, but seems only connects half the time and when it does it fails in
about 20 seconds... Thank you for the help, I guess I am out of luck. 



--
Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/

Re: Disable Websocket

[Mike Jumper <mi...@guac-dev.org>]

On Wed, Feb 21, 2018 at 8:08 AM, yozh <st...@gmail.com> wrote:

> Hello,
>
> I brought this up before, but never got an answer. How do I disable
> websockets and use HTTP tunnel ? I`m using nginx as a proxy for port 80,
> and
> it doesnt seem to fall back to HTTP, just times out since websense is
> blocking websockets. How to I force to use HTTP ?
>
>
I would recommend instead setting up encryption through enabling SSL on
your Nginx server, as that would likely both work around the problems with
the interfering proxy while also providing necessary security. It's
generally not recommendable to access remote desktop services without any
encryption.

You can effectively disable WebSocket by configuring your Nginx reverse
proxy to return a 404 for /guacamole/websocket-tunnel (assuming you are
serving Guacamole from /guacamole - adjust this accordingly if you are
using a different path). It is likely that the interfering proxy is
allowing WebSocket to partially succeed, hence the lack of proper fallback,
but the hard 404 error will force Guacamole to fallback to HTTP. Beware
that:

* The HTTP tunnel has reasonable performance but will not be as nice as
WebSocket.
* If your proxy interferes with WebSocket, there's a good chance it will
interfere with HTTP as well. If you cannot use encryption, and the proxy
prevents any form of streaming from working properly, you may be out of
luck.

- Mike