No auth token
Jump to navigation
Jump to search
2023-02-14T06:23:44.876Z socket.io-client:socket transport is open - connecting 2023-02-14T06:23:44.877Z socket.io-client:manager writing packet {"type":0,"nsp":"/"} 2023-02-14T06:23:44.877Z socket.io-parser encoding packet {"type":0,"nsp":"/"} 2023-02-14T06:23:44.877Z socket.io-parser encoded {"type":0,"nsp":"/"} as 0 2023-02-14T06:23:44.877Z engine.io-client:socket flushing 1 packets in socket 2023-02-14T06:23:45.141Z engine.io-client:socket socket receive: type "message", data "4{"message":"No auth token"}" 2023-02-14T06:23:45.142Z socket.io-parser decoded 4{"message":"No auth token"} as {"type":4,"nsp":"/","data":{"message":"No auth token"}} 2023-02-14T06:23:45.143Z socket.io-client:manager disconnect 2023-02-14T06:23:45.143Z socket.io-client:manager closed due to forced close
Node.js, JavaScript runtime, Deno, nock, next.js, express.js, electron, Nest.js, nvm, package.json
, Webpack, node -r
, npm, nvm, node-gyp
, Node.js modules, Fastify, PM2, UnhandledPromiseRejectionWarning, node-inspector, Puppeteer, Node-config, Node-RED
Advertising: