On Fri, Apr 28, 2017 at 11:12 PM, Suncatcher16 <[email protected]> wrote:
> As I got your words, when the server writes > > > Connected to Guacamole. Waiting for respond > > it means that Guacamole server connected to guacd successfully, and when > it > write then > > > The connection had been closed because the server is taking too long to > > respond > > it means that guacd cannot bounce back Guacamole server. Am I correct? > This message means that no response was received from the server for long enough that the client assumed the connection was closed. This is essentially the same message you were seeing in the guacd logs, but from the opposite end of the chain. All layers along the Guacamole stack have essentially the same timeout rules, and will abort the connection if no data is seen for 15 seconds. If communication isn't working properly, it's possible to see both of these messages. The best thing to do at this point would be to investigate things one layer at a time, starting from the browser, to determine why data is not reaching Guacamole. Though the client is also complaining of a lack of data, that's most likely because the server is waiting to hear back from the client before responding, and something is interfering with that response. Do you see any errors in your browser's JavaScript console (or the network tab of your browser's dev tools) regarding WebSocket failures? Have you confirmed whether there is any sort of proxy between the browser and the Guacamole server? (This includes some virus scanning software). - Mike
