websockify.js : Server disconnected (code: 1006)  #3

Activity

1. CendioOssman commented on Oct 25, 2017

   

   CendioOssman

   on Oct 25, 2017

   Member

   More actions

   You have some incompatibility between websockify and the version of WebSocketServer you are using. I would suggest upgrading to the latest version of websockify.js.

   @DirectXMan12, perhaps time to push something updated to npm?
2. CendioOssman

   assigned

   DirectXMan12

   on Oct 25, 2017
3. evantobin commented on Mar 4, 2018

   

   evantobin

   on Mar 4, 2018

   More actions

   @DirectXMan12 Any update on upgrading the version in NPM?
4. mliudev commented on May 22, 2018

   

   mliudev

   on May 22, 2018

   Last edited by mliudev

   More actions

   Getting a similar error with the latest node on Windows Server 2008 R2:

   PS C:\> node --version
   v10.1.0
   PS C:\> npm --global ls
   `-- websockify@0.7.1
     +-- optimist@0.6.1
     | +-- minimist@0.0.10
     | `-- wordwrap@0.0.3
     +-- policyfile@0.0.6
     `-- ws@5.2.0
       `-- async-limiter@1.0.0

   I'm getting the following error:

   WebSocket settings:
       - proxying from :7777 to localhost:5900
       - Running in encrypted HTTPS (wss://) mode using: foo.pem, foo.pem
   C:\Users\Administrator\AppData\Roaming\npm\node_modules\websockify\websockify.js:129
           callback(true, 'binary');
           ^
   
   TypeError: callback is not a function
       at Object.selectProtocol [as handleProtocols] (C:\Users\Administrator\AppData\Roaming\npm\node_modules\websockify\we
   bsockify.js:129:9)
       at WebSocketServer.completeUpgrade (C:\Users\Administrator\AppData\Roaming\npm\node_modules\websockify\node_modules\
   ws\lib\websocket-server.js:260:33)
       at WebSocketServer.handleUpgrade (C:\Users\Administrator\AppData\Roaming\npm\node_modules\websockify\node_modules\ws
   \lib\websocket-server.js:220:10)
       at Server.upgrade (C:\Users\Administrator\AppData\Roaming\npm\node_modules\websockify\node_modules\ws\lib\websocket-
   server.js:78:16)
       at Server.emit (events.js:182:13)
       at onParserExecuteCommon (_http_server.js:535:14)
       at onParserExecute (_http_server.js:482:3)

   Does anyone know of a working version of node and this version of websockify? At some point there was a working combination.

   This issue seems to indicate that windows was working at some point in the beginning of this year.
   novnc/websockify#67 (comment)
5. mliudev commented on May 22, 2018

   

   mliudev

   on May 22, 2018

   Last edited by mliudev

   More actions

   As an update I was able to get this working with this version of websockify.js using node 10.1.0. I think I just need to package this up as a node module and install it globally.
6. alex88 commented on Jan 3, 2019

   

   alex88

   on Jan 3, 2019

   More actions

   The problem is the ws library version, instead of using >=0.4.27 use ~0.4.27 as dependency constraint in package.json and everything works.
   Problem is that ws is now at version 6.1.2 so quite far from the 0.x this package is using
7. CendioOssman commented on Jan 8, 2019

   

   CendioOssman

   on Jan 8, 2019

   Member

   More actions

   Ah, thanks. We'll have to update our dependencies then. Thanks for figuring it out.
8. samhed

   transferred this issue fromnovnc/websockifyon Jul 12, 2019