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

Unauthenticated WebSocket has disconnected from us. #54

Open
HSIS007 opened this issue Mar 9, 2022 · 0 comments
Open

Unauthenticated WebSocket has disconnected from us. #54

HSIS007 opened this issue Mar 9, 2022 · 0 comments

Comments

@HSIS007
Copy link

HSIS007 commented Mar 9, 2022

cursedchrome_1 | [March 9th 2022, 7:21:36 pm] A new browser has connected to us via WebSocket!
cursedchrome_1 | [March 9th 2022, 7:21:36 pm] Authenticating newly-connected browser...
cursedchrome_1 | [March 9th 2022, 7:21:36 pm] Unauthenticated WebSocket has disconnected from us.
cursedchrome_1 | (node:20) UnhandledPromiseRejectionWarning: A timeout occurred when authenticating WebSocket client.
cursedchrome_1 | (node:20) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

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

1 participant