search

CheshireCaat / bas-remote-node

NodeJS library, which allows you to automate Google Chrome browser.
MIT License
28 stars 7 forks source link

Can't send data because WebSocket is not opened. #19

Open dmitryp-rebel opened 11 months ago

dmitryp-rebel commented 11 months ago

Hello. I experience occasional but quite often error on launch puppeteer-with-fingerprints plugin:

Version: puppeteer-with-fingerprints@1.4.3

Thread #0 failed: Error: Can't send data because WebSocket is not opened. at exports.throwIf (C:\bots\test\node_modules\websocket-as-promised\src\utils.js:4:11) at WebSocketAsPromised.send (C:\bots\test\node_modules\websocket-as-promised\src\index.js:252:5) at SocketService.send (C:\bots\test\node_modules\bas-remote-node\src\services\socket.js:89:14) at BasRemoteClient._send (C:\bots\test\node_modules\bas-remote-node\src\index.js:223:25) at BasRemoteClient.send (C:\bots\test\node_modules\bas-remote-node\src\index.js:254:17) at BasRemoteClient._startThread (C:\bots\test\node_modules\bas-remote-node\src\index.js:275:10) at C:\bots\test\node_modules\bas-remote-node\src\index.js:190:12 at new Promise () at BasRemoteClient.runFunction (C:\bots\test\node_modules\bas-remote-node\src\index.js:189:21) at C:\bots\test\node_modules\browser-with-fingerprints\src\plugin\connector\index.js:31:16

What could be a reason?

dmitryp-rebel commented 11 months ago

Still getting a lot of those running multiple processes

jmoneyy112 commented 5 months ago

I am getting this:

{ "message": "Cannot connect to the WebSocket server (reason: connection failed)\nThis could be due to the fact that the engine was not downloaded or unpacked correctly.\nTry completely deleting the engine folder and restarting the code until it completes.\nIf this does not help, open an issue with a detailed description of the problem." }