Websocket handshake Error about binance-api-node HOT 9 CLOSED

Any thoughts on this @balthazar or @bennyn ?

from binance-api-node.

Hey, is this something which happens randomly or everytime you try to open this socket?

from binance-api-node.

@balthazar Unfortunately, this has happened every time I've tried connecting to a websocket channel on various occasions.

from binance-api-node.

I tested with this code and it works like a charm. So the bug is not reproducible for me. :-/

const Binance = require('binance-api-node').default

const client = new Binance()

client.ws.ticker('ETHBTC', ticker => {
  console.log(ticker)
})

Which Binance API version are you using @JohnBDonner?

from binance-api-node.

@bennyn here's from my package-lock.json:

"binance-api-node": {
  "version": "0.7.4",
  "resolved": "https://registry.npmjs.org/binance-api-node/-/binance-api-node-0.7.4.tgz",
  "integrity": "sha512-NHsqnw3X+0koa5FHiaAepQE+SEZNH3OJ9H3WL8HZjapFw6BQNfowa8w7E5TAJVGsOL4vWf9UFuOs8xHfsZuk7w==",
  "requires": {
    "html5-websocket": "2.0.2",
    "isomorphic-fetch": "2.2.1",
    "lodash.zipobject": "4.1.3",
    "reconnecting-websocket": "3.2.2"
  }
}

Something to note is that in the documentation it says to install with yarn but I'm using npm. I've seen that can cause issues for some projects.

from binance-api-node.

Using npm should not matter, it's most likely a connectivity issue on your side, or something is wrong with the binance certificate you have on your client.

from binance-api-node.

I have same issue, It only came from when using on browser

from binance-api-node.

I find the issue because of the protocols pass to reconnecting-websocket is null, so the header Sec-WebSocket-Protocol was send when create web socket is NULL

from binance-api-node.

0.7.6 release published, closing

from binance-api-node.