Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: WS was inactive for too long #61

Open
waltereza opened this issue Jun 19, 2024 · 4 comments
Open

Error: WS was inactive for too long #61

waltereza opened this issue Jun 19, 2024 · 4 comments

Comments

@waltereza
Copy link

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.

@vadimpronin
Copy link
Owner

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

@waltereza
Copy link
Author

@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.

@Zippyops
Copy link

Zippyops commented Jul 8, 2024

HI, I am also facing the same issue.. do we have any suggestions?

@waltereza
Copy link
Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants