Getting "Nonce is not increasing" error with Node.js WS Lib

[bitmex]

Getting "Nonce is not increasing" error with Node.js WS Lib

[andersea]

If you are using the same api key for both rest and websocket, there is a chance this can happen, since api calls can fall out of sync. Try using different keys for the rest interface and the websocket and see if that resolves the issue.

[ko0f]

{"error":"Nonce is not increasing. This nonce: 1515130196494, last nonce: 1515128183690000"}

The two nonces have different format, one is in milliseconds and the other in microseconds. You should use the same format on both clients.

But as @andersea recommended, use different keys for RT and REST, they seem to have nonce conflicts. I couldn't figure out why, it looks like a server side issue.

[ryanfox]

Now the node-swagger and node-ws clients use the same nonce scheme. With a new API key, this shouldn't happen any more.

[annugaurish]

I have solved this problem by making changes in createSocket.js
Added following code in the createSocket function

wsClient.onreconnect = function() {
wsClient.url = makeEndpoint(options);

debug('Reconnecting to BitMEX at ', wsClient.url);

};

and in ReconnectionSocket.js added the following line in reconnect prototype
this.onreconnect();

this is to be added before this.open(this.url);

Changed API keys but it was not solving issue

[QuentinFAIDIDE]

Nonce is increased with each websocket request so you can send from time to time something with the send(msg, callback) method from the socket member of the _bitmexRealtimeApi2.default class (or even BitmexPlus class cause of inheritance) to fix this issue when the websocket client is not active. This was mentioned on another similar issue with the 'ping' message.
But pinging does not sounds like a good persistent fix, especially when Bitmex servers might already have lots of inactive opened sockets they will want to kick out one day, because if someone wants to use REST requests for prices instead of WS when they have no position opened and don't want to open one (I do), he can't disconnect the socket with the connector member functions, he has to access its member objects and hack around, it kind of breaks regular OOP encapsulation.
Bitfinex node API lets you request a reference to a websocket object from their main connector class, maybe this project needs to do the same and encapsulate the socket in another class so users can manipulate and start ws connections by themselves.