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)
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)