On Wed, Jul 7, 2021 at 1:53 PM Alex B. <[email protected]> wrote: > Hi, > > I´m trying to run Guacamole on some restricted network. On the normal > network it is working well, but on restricted network (there is general > problem with using Websockets). I´m not able to see any picture (connection > is established, because Windows 10 on the other site will be locked after > connection). > > I´m using reverse proxy to disable any WS communication (I have a rule > to send location /websocket-tunnel to 404). >
Can you provide more detail on how you're doing this? Depending on your reverse proxy, simply configuring a location that sends /websocket-tunnel to a 404 not found error may not actually be achieving what you think it is achieving - you may be rediecting http://server/guacamole/webscoket-tunnel rather than wss://server/guacamole/websocket-tunnel. > > I tried to compare "ok" state and this state. Only what I find is the > response code from Websocket connection to > 'ws://<server>:<port>/websocket-tunnel'. In both cases this call failed, > but in "ok" state it will fail without any message, but in second case, it > will fail with message: Error during WebSocket handshake: Unexpected > response code: 500. > I'm not sure what you mean when you say you compared it? > > I tried to redirect all 500 codes to 404, but without success. > This is a Bad Idea, and will both 1) not achieve what you want, and 2) cause misleading issues in the future. > > Can you please help me with this? I don´t know if it is an application > error (bug), or if my setup is wrong or if Guacamole cannot be used on > "WebSocket restricted" networks at all... > > Guacamole can certainly be configured to work without WSS, we just need more detail on how you've tried to go about this in order to help you. -Nick >
