bitrich-info/xchange-stream

Kraken websocket not working

atiqkhan26 opened this issue · 6 comments

atiqkhan26 commented

Hi experts,

I am trying to test the public channel of Kraken's beta environment and keep getting this error. Has anyone got it working for Kraken?

10:01:18.444 [nioEventLoopGroup-2-1] INFO info.bitrich.xchangestream.kraken.KrakenStreamingService - Connecting to wss://beta-ws.kraken.com 10:01:19.340 [nioEventLoopGroup-2-2] INFO info.bitrich.xchangestream.service.netty.WebSocketClientHandler - WebSocket Client connected! 10:01:19.340 [nioEventLoopGroup-2-2] WARN info.bitrich.xchangestream.kraken.KrakenStreamingService - Resubscribing channels 10:01:19.344 [nioEventLoopGroup-2-2] INFO info.bitrich.xchangestream.kraken.KrakenStreamingService - System status: KrakenSystemStatus{connectionID='9183671655362526710', event='systemStatus', status='online', version='0.3.0'} 10:01:19.548 [nioEventLoopGroup-2-2] ERROR info.bitrich.xchangestream.kraken.KrakenStreamingService - Channel ticker-LTC/USD has been failed: Public channels not available in this endpoint 10:01:45.826 [nioEventLoopGroup-2-2] ERROR info.bitrich.xchangestream.kraken.KrakenStreamingService - Channel ticker-LTC/USD has been failed: Subscription Not Found

Any help resolving this will be highly appreciated.

Thanks

atiqkhan26 commented

Although Kraken documentation says beta-ws.kraken.com can work with both public and private channels, it doesn't seem to be the case. I have to get the public channels from ws.kraken.com and private ones from beta-ws.kraken.com

Am I missing something which might be behaving differently for me.

mdvx commented

I have not tried to connect to the beta channel yet, only provided a method to so in PR #457. There is also the Futures channel, which I want to implement too. @atiqkhan26 @badgerwithagun

mdvx commented

Just rememebered, with Kraken the Api keys can get broken after which I get continual Invalid nonce errors. My solution is to create a new API key.

Speculation: I think maybe the server remembers the last nonce across sessions, and if you sent a big one up, you just set a high water mark.

mdvx commented

I stopped getting invalid nonces errors, after I got multiple keys for multiple processes - now dev has a key, QA has one as does UAT

mdvx commented

can we close this @atiqkhan26 @badgerwithagun