Re: unable to use websocket - HTTP tunnel instead

2018-02-14 Thread Mike Jumper
On Wed, Feb 14, 2018 at 4:45 AM, wouterve wrote: > ... > In the new hostfile, i placed only the information regarding the websocket > AND changed the port to 8080 (forgot this before) > > > ServerName name > > I'm not sure I see why you would want Apache to listen on port 8080, as normally you

Re: unable to use websocket - HTTP tunnel instead

2018-02-14 Thread wouterve
Hi, sry for late reply, haven't had much time to spend on this project lately. @jonathan hunter: the order of is important indeed as the documentation points out: > Important > The Location section for /guacamole/websocket-tunnel must be placed after > the Location section for the rest of Guac

Re: unable to use websocket - HTTP tunnel instead

2017-12-31 Thread Nick Couchman
On Sun, Dec 31, 2017 at 9:50 AM, Jonathan Hunter wrote: > Just a thought - does the order of the directives in apache's > config make a difference? I had something very similar when getting mine > working (see my other thread about printing not working over HTTP, only via > web socket) > This a

Re: unable to use websocket - HTTP tunnel instead

2017-12-31 Thread Jonathan Hunter
Just a thought - does the order of the directives in apache's config make a difference? I had something very similar when getting mine working (see my other thread about printing not working over HTTP, only via web socket) FWIW, my working Apache config pretty much boils down to just this below,

Re: unable to use websocket - HTTP tunnel instead

2017-12-21 Thread wouterve
For your interest; here is the output from WS debugger from chrome: Request URL:ws://192.168.217.115:8080/guacamole/websocket-tunnel?token=4DCC454D12B7F3C94527AF58561DB49EF5737345164CA56BAAA7D21AEBAB9786&GUAC_DATA_SOURCE=mysql&GUAC_ID=1&GUAC_TYPE=c&GUAC_WIDTH=1045&GUAC_HEIGHT=769&GUAC_DPI=96&GUAC_