Open waltereza opened 5 months ago
This error means that your client (browser) does not send anything to the websocket connection. Even when it has nothing to say it should periodically send pings or respond to them. So double check that your guacamole-js works properly with the websocket
@vadimpronin The problem occurs as soon as I start the connection, I receive some information from the server on the frontend, the Windows login screen image is rendered and the connection is closed, in about 10 seconds.
HI, I am also facing the same issue.. do we have any suggestions?
@Zippyops not one, the project has a great proposal, but the documentation is simplistic and the developer doesn't seem interested in helping when someone has a problem.
I created a simple server to test, and I get these 2 errors:
losing connection with error: 1000 [2024-06-19 03:18:21] [Connection 1] Closing connection with error: Error: WS was inactive for too long
No matter what configuration I do, the connection opens, and in a few seconds it drops, showing these errors.