Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 03F2E200D2D for ; Fri, 27 Oct 2017 19:29:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 02800160BF2; Fri, 27 Oct 2017 17:29:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1FCA01609DD for ; Fri, 27 Oct 2017 19:29:36 +0200 (CEST) Received: (qmail 33482 invoked by uid 500); 27 Oct 2017 17:29:36 -0000 Mailing-List: contact user-help@guacamole.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@guacamole.incubator.apache.org Delivered-To: mailing list user@guacamole.incubator.apache.org Received: (qmail 33470 invoked by uid 99); 27 Oct 2017 17:29:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Oct 2017 17:29:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 80EA61A1995 for ; Fri, 27 Oct 2017 17:29:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.265 X-Spam-Level: ** X-Spam-Status: No, score=2.265 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, HTML_OBFUSCATE_10_20=1.162, KAM_BADIPHTTP=2, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.625] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id uMhhYuNUlzQM for ; Fri, 27 Oct 2017 17:29:33 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 11FD15FE64 for ; Fri, 27 Oct 2017 17:29:31 +0000 (UTC) Received: (qmail 33453 invoked by uid 99); 27 Oct 2017 17:29:31 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Oct 2017 17:29:31 +0000 Received: from mail-yw0-f175.google.com (mail-yw0-f175.google.com [209.85.161.175]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id F09671A0372 for ; Fri, 27 Oct 2017 17:29:30 +0000 (UTC) Received: by mail-yw0-f175.google.com with SMTP id u142so6355497ywg.4 for ; Fri, 27 Oct 2017 10:29:30 -0700 (PDT) X-Gm-Message-State: AMCzsaWINs4ksyhsfsFk/fD72GGYX9MdzoO1GQbbd+n+YduO3ZC/WuNX 14HJveKGj2WHiwJkrNB6jCxTpZiHHh03M+hl+yI= X-Google-Smtp-Source: ABhQp+TypkoO/uTaADbffziT+FFmLY1hHnHeANOD9VFIljKvBf7g8UnxHFSYMzm2YsGrnTJ5H9DL4dB2lvGve7BE/z4= X-Received: by 10.129.96.134 with SMTP id u128mr925241ywb.464.1509125370359; Fri, 27 Oct 2017 10:29:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.99.87 with HTTP; Fri, 27 Oct 2017 10:29:29 -0700 (PDT) In-Reply-To: References: From: Nick Couchman Date: Fri, 27 Oct 2017 13:29:29 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: UNABLE TO CREATE WEBSOCKET CONNECTION To: user@guacamole.incubator.apache.org Content-Type: multipart/alternative; boundary="001a114735549f34f2055c8aa1ba" archived-at: Fri, 27 Oct 2017 17:29:38 -0000 --001a114735549f34f2055c8aa1ba Content-Type: text/plain; charset="UTF-8" On Fri, Oct 27, 2017 at 12:53 PM, Amarjeet Singh wrote: > Nick, > > I already tried as you said. It' working when I am proxying through Apache > or nginx. I am getting the following error in the browser through FES : > So, this indicates the problem is with FES. > > WebSocket connection to 'wss://172.16.1.180/accops-rdp > /websocket-tunnel?token=D796521006917D22C54DC3D94D4274510A0B > 92BB2C82F2FB394E6667F31AE34E&GUAC_DATA_SOURCE=default&GUAC_ID= > ACCOPS&GUAC_TYPE=c&GUAC_WIDTH=1920&GUAC_HEIGHT=410&GUAC_DP > I=96&GUAC_AUDIO=audio%2FL8&GUAC_AUDIO=audio%2FL16&GUAC_IMAGE > =image%2Fjpeg&GUAC_IMAGE=image%2Fpng&GUAC_IMAGE=image%2Fwebp' > >> failed: One or more reserved bits are on: reserved1 = 1, reserved2 = 0, >> reserved3 = 0 > > My guess is that this error message is from FES. > My Queries :- > > * Why I am getting the above mentioned error? *failed: One or more > reserved bits are on: reserved1 = 1, reserved2 = 0, reserved3 = 0 > I can't answer this question because I don't know anything about FES. Evidently something in "FES" is causing a failure and stopping the WebSocket connection. Since I don't know anything about FES, I can't help you there. > * What causes this issue if we are using proxy requests in general ?* > Since the error is with FES, and not with "proxy request in general," I'm not sure this is a valid question. You've tested it and you say everything works if you use Apache and nginx, but fails when FES is used, so proxy requests, in general, are working. Just not with FES. > > * Why there is a below exception in GuacamoleWebSocketTunnelEndpoint?* > > >> >> Thread-65] DEBUG o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Connection >> to guacd closed. >> org.apache.guacamole.GuacamoleConnectionClosedException: Connection to >> guacd is closed. >> at org.apache.guacamole.io.ReaderGuacamoleReader.read(ReaderGuacamoleReader.java:185) >> ~[guacamole-common-0.9.10-incubating.jar:na] >> at org.apache.guacamole.io.ReaderGuacamoleReader.readInstructio >> n(ReaderGuacamoleReader.java:197) ~[guacamole-common-0.9.10-incu >> bating.jar:na] >> at org.apache.guacamole.protocol.FilteredGuacamoleReader.readIn >> struction(FilteredGuacamoleReader.java:83) ~[guacamole-common-0.9.10-incu >> bating.jar:na] >> at org.apache.guacamole.protocol.FilteredGuacamoleReader.readIn >> struction(FilteredGuacamoleReader.java:83) ~[guacamole-common-0.9.10-incu >> bating.jar:na] >> at org.apache.guacamole.protocol.FilteredGuacamoleReader.read(F >> ilteredGuacamoleReader.java:66) ~[guacamole-common-0.9.10-incu >> bating.jar:na] >> at org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpo >> int$2.run(GuacamoleWebSocketTunnelEndpoint.java:162) >> ~[guacamole-common-0.9.10-incubating.jar:na] >> Caused by: java.net.SocketException: Socket closed >> at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.7.0_51] >> at java.net.SocketInputStream.read(SocketInputStream.java:152) >> ~[na:1.7.0_51] >> at java.net.SocketInputStream.read(SocketInputStream.java:122) >> ~[na:1.7.0_51] >> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) >> ~[na:1.7.0_51] >> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) >> ~[na:1.7.0_51] >> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) ~[na:1.7.0_51] >> at java.io.InputStreamReader.read(InputStreamReader.java:184) >> ~[na:1.7.0_51] >> at org.apache.guacamole.io.ReaderGuacamoleReader.read(ReaderGuacamoleReader.java:171) >> ~[guacamole-common-0.9.10-incubating.jar:na] >> ... 5 common frames omitted >> > > This likely occurs because guacd detects that there's no activity on the tunnel (because the WebSocket connection is failing) and guacd shuts down the connection. This is a peripheral error and probably not what you should be focused on until you fix the issues with FES. > *4. What should I have to handle if I proxy requests in FES ?* > I don't know. I don't know anything about FES, so it's very hard to say. Is FES custom code you've written? Is it another open source project? Is it proprietary code? The issue seems to be with FES, so that needs to be worked out. Since Guacamole works fine when proxied through Nginx, Apache, and any number of other web servers, the issue is not with Guacamole, or Tomcat, and its ability to handle other software proxying requests to it. -Nick --001a114735549f34f2055c8aa1ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On F= ri, Oct 27, 2017 at 12:53 PM, Amarjeet Singh <amarjeetxc@gmail.com= > wrote:
Nick,

I already t= ried as you said. It' working when I am proxying through Apache or ngin= x. I am getting the following error in the browser through FES :

So, this indicates the problem is w= ith FES.
=C2=A0

My guess is that this error message is from FES.<= /div>
=C2=A0
=C2=A0My Quer= ies :-

=C2=A0Why I am getting the above mentioned error?=C2=A0=C2=A0<= font color=3D"#ff0000">failed: One or more reserved bits are on: reserved1 = =3D 1, reserved2 =3D 0, reserved3 =3D 0

I can't answer this question because I don't = know anything about FES.=C2=A0 Evidently something in "FES" is ca= using a failure and stopping the WebSocket connection.=C2=A0 Since I don= 9;t know anything about FES, I can't help you there.
=C2=A0
=C2=A0What causes this issue if we are using proxy requests=C2= =A0 in general ?

Sinc= e the error is with FES, and not with "proxy request in general,"= I'm not sure this is a valid question.=C2=A0 You've tested it and = you say everything works if you use Apache and nginx, but fails when FES is= used, so proxy requests, in general, are working.=C2=A0 Just not with FES.=
=C2=A0

=C2=A0Why there is a b= elow exception in GuacamoleWebSocketTunnelEndpoint?=C2=A0

=C2=A0
=C2=A0Thread-65] D= EBUG o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Connection to guacd cl= osed.
org.apache.guacamole.GuacamoleConnectionClosedException: Conn= ection to guacd is closed.
= at org.apache.= guacamole.io.ReaderGuacamoleReader.read(ReaderGuacamoleReader= .java:185) ~[guacamole-common-0.9.10-incubating.jar:na]
at org.apache.guacamole.io.ReaderGuacamoleRead= er.readInstruction(ReaderGuacamoleReader.java:197) ~[guacamole-co= mmon-0.9.10-incubating.jar:na]
at org.apache.guacamole.protocol.FilteredGuacamoleReader.read= Instruction(FilteredGuacamoleReader.java:83) ~[guacamole-common-0= .9.10-incubating.jar:na]
at org.apache.guacamole.protocol.FilteredGuacamoleReader.readInstruction(FilteredGuacamoleReader.java:83) ~[guacamole-common-0.9.10-= incubating.jar:na]
at = org.apache.guacamole.protocol.FilteredGuacamoleReader.read(Filter= edGuacamoleReader.java:66) ~[guacamole-common-0.9.10-incubating.j= ar:na]
at org.apache.guacam= ole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWeb= SocketTunnelEndpoint.java:162) ~[guacamole-common-0.9.10-incubati= ng.jar:na]
Caused by: java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.7.0_51]
at java.net.SocketInputStream.read(SocketInputStream.java= :152) ~[na:1.7.0_51]
at jav= a.net.SocketInputStream.read(SocketInputStream.java:122) ~[na:1.7.0_51= ]
at sun.nio.cs.StreamDecod= er.readBytes(StreamDecoder.java:283) ~[na:1.7.0_51]
at sun.nio.cs.StreamDecoder.implRead(Str= eamDecoder.java:325) ~[na:1.7.0_51]
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) ~[na= :1.7.0_51]
at java.io.Input= StreamReader.read(InputStreamReader.java:184) ~[na:1.7.0_51]
at org.apache.guacamole.io.ReaderGuacamol= eReader.read(ReaderGuacamoleReader.java:171) ~[guacamole-common-0.9.10= -incubating.jar:na]
..= . 5 common frames omitted


This likely occurs because guacd de= tects that there's no activity on the tunnel (because the WebSocket con= nection is failing) and guacd shuts down the connection.=C2=A0 This is a pe= ripheral error and probably not what you should be focused on until you fix= the issues with FES.
=C2=A0
=
4. What should I have to handle if I proxy requests in FES= ?=C2=A0

I don&= #39;t know.=C2=A0 I don't know anything about FES, so it's very har= d to say.=C2=A0 Is FES custom code you've written?=C2=A0 Is it another = open source project?=C2=A0 Is it proprietary code?=C2=A0 The issue seems to= be with FES, so that needs to be worked out.=C2=A0 Since Guacamole works f= ine when proxied through Nginx, Apache, and any number of other web servers= , the issue is not with Guacamole, or Tomcat, and its ability to handle oth= er software proxying requests to it.

-Nick
--001a114735549f34f2055c8aa1ba--