Errorr Message: Negotiate Unknown, 503 #67

LRonHubs · 2017-09-08T16:33:07Z

Error Message: Negotiate Unknown
Exception: undefined
Error Data: 503

I get this error when trying to connect to WebSockets. Is this something on bittrex's end? If so is it a permanent thing?

ale316 · 2017-09-08T16:43:53Z

Getting this too. They said they were attacked (https://twitter.com/ramikawach/status/906184766969356289), which prompted them to CloudFlare all their endpoints, including the signalr ones.

zduerr · 2017-09-08T17:01:17Z

is there a workaround for this?

LRonHubs · 2017-09-08T17:18:53Z

Spam the PUSH api i guess

masalinas · 2017-09-08T18:15:14Z

@LRonHubs what do you mean with Spam the PUSH api??

TimLaMason · 2017-09-08T18:23:49Z

I think he means using the Rest API for grabs. I'd be careful of overuse, as it may get your key banned though.

…

On Sep 8, 2017 2:17 PM, "algoscale1" ***@***.***> wrote: facing same issue — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#67 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGJjzBEEg7dtX5HasLnB-CPOr5whi8G5ks5sgYSrgaJpZM4PRah8> .

masalinas · 2017-09-08T18:26:21Z

@TimLaMason I was using the API more than one week and I never received any error, or banned ... meaby is it a temporal problem?? I created other key and the error is the same

junkomatic · 2017-09-08T18:31:53Z

Then endpoint is giving '503 - Service Temporarily Unavailable'. I presume they will reactivate it later, or else enable functionality for account auth headers. I have an alert set for if it reactivates normally. Keep us posted if anyone here's anything.

TimLaMason · 2017-09-08T18:37:20Z

I mean using the rest api for frequent requests in place of the websocket, if it is down. Most api's will ban your key if you make requests more than one every ten seconds or so (just an example). I'm not sure exactly what bittrex's policy is. I'm just saying for those who are thinking of "Spaming the rest api" in place of the signalr hub, it may not be a good idea.

…

On Sep 8, 2017 2:26 PM, "Miguel Angel Salinas Gancedo" < ***@***.***> wrote: @TimLaMason <https://github.com/timlamason> I was using the API more than one week andI never receive any error, or banned ... meaby is it a temporal problem?? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#67 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGJjzJHAv3r1E8-kpBVCefLZNKfMkrLmks5sgYbNgaJpZM4PRah8> .

masalinas · 2017-09-08T18:39:55Z

How can I receive the complete error from bittrex?

junkomatic · 2017-09-08T18:50:45Z

SignalR websocket hubs we're primarily designed for .net. if you code a c# hub client it outputs the error message, and you can also enable tracing to see the raw feed.

masalinas · 2017-09-08T19:00:25Z

My client I have this code:

// listen to Bittrex WebSocket
    var websocketsclient = bittrex.websockets.listen( function( data ) {
        if (data.M === 'updateSummaryState') {
            data.A.forEach(function(data_for) {
                app.io.emit('bittrex-event', data_for.Deltas);
            });
        }
    });

    websocketsclient.serviceHandlers.connectFailed = function(error) {
        console.log("Websocket connectFailed: ", error);
    };

    websocketsclient.serviceHandlers.onerror = function(error) {
        console.log("Websocket error: ", error);
    };

    websocketsclient.serviceHandlers.connectionLost = function(error) {
        console.log("Connection Lost: ", error);
    };

But not receive any erro detail only the:

Error Message: Negotiate Unknown
Exception: undefined
Error Data: 503

But where is the callback that receive this error??? how can I get this error in my code???

masalinas · 2017-09-08T19:16:44Z

@junkomatic how do you code for receive the error: '503 - Service Temporarily Unavailable'?
because i only reveive the error: Error Data: 503

junkomatic · 2017-09-08T19:16:45Z

503 is an http error response code that literally means "Service Temporarily Unavailable". There's not much more data than that.

LRonHubs · 2017-09-08T20:07:21Z

SignalR websocket hubs we're primarily designed for .net. if you code a c# hub client it outputs the error message, and you can also enable tracing to see the raw feed.

…

On Sep 8, 2017 3:16 PM, "Miguel Angel Salinas Gancedo" < ***@***.***> wrote: @junkomatic <https://github.com/junkomatic> how do you code for receive the error: '503 - Service Temporarily Unavailable' because i only reveive the error: Error Data: 503 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#67 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWRK7NkCHsuCJKKL87P3i_JrD2mPHhYCks5sgZKdgaJpZM4PRah8> .

ale316 · 2017-09-08T20:20:23Z

@masalinas You can go into the signalr-client node module and print the request out.

Error Message: Negotiate Unknown
Exception: undefined
Error Data: 503

Is just a catch all error.

What Bittrex is returning is the CloudFlare HTML page saying that they're verifying your connection. I believe the only thing we can do is wait.

n0mad01 · 2017-09-08T21:54:26Z

i've created a pull request for the signalR lib to at least fix the pass of binding errors into the onerror serviceHandler.
mwwhited-archives/signalr-client-nodejs#20

the 503 issue i haven't looked more closely yet.

strelov1 · 2017-09-08T22:59:36Z

Hmm, why using this service https://www.websocket.org/echo.html WS bittrex is available?

AGoetzDev · 2017-09-09T01:58:42Z

As already mentioned, the websocket endpoint is currently protected by cloudflare's anti bot system. It is possible to bypass it, by executing a request to the negotiate endpoint (or any page on bittrex really) just as a regular browser would and letting cloudflare do its thing (how cloudflare's bot protection works is explained here: link) then grab the identity cookie and the clearance cookie and send those as the Cookie header together with the User-Agent header (which must be the same as in the request used to obtain the cookies) with the negotiate and websocket connect request. As an example, for python cloudflare-scrape does just that.

ThePrimeagen · 2017-09-09T02:31:19Z

@AlxGDev how is that a solution? My bot has a lot of responsibility and this really worries me that I could just be taken offline for several hours...

usmankhanic · 2017-09-09T10:00:08Z

Does anyone know if bittrex have commented on this?

ninesalt · 2017-09-09T11:23:16Z

Need a fix for this asap

TimLaMason · 2017-09-09T12:11:38Z

There is also a .net fix: https://github.com/elcattivo/CloudFlareUtilities Similar to python's cfscrape. This may help. On Sep 9, 2017 7:23 AM, "Swailem95" <notifications@github.com> wrote: Need a fix for this asap — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#67 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGJjzLq13g2upPlxv4gFI7lKHczR13gGks5sgnUkgaJpZM4PRah8> .

metachris · 2017-09-09T13:02:31Z

@AlxGDev thanks for your suggestion! It also worked for me.

For anyone interested: the goal is to add your cookie and user-agent headers to the signalR websockets connection here: https://github.com/mwwhited/signalr-client-nodejs/blob/master/WhitedUS.SignalR/WhitedUS.signalR/signalR.js#L295

I copied the bittrex and signalr node modules intop my project and modified them a little to achieve this. But you could also edit the signalr-client file directly (not recommended, but the quickest way).

bigdataboss · 2017-09-09T13:06:57Z

Just replace connectws() function. For the future we could add headers opt. To get cookie without browser you can use nightmare.js

var connectws = function(callback) {
    wsclient = new signalR.client(
      opts.websockets_baseurl,
      opts.websockets_hubs, 
      undefined, true
    );
    wsclient.headers['User-Agent'] = 'YOUR BROWSER UA';
    wsclient.headers['cookie'] = 'cf_clearance=YOUR CF_CLEARENCE FROM BROWSER';
    wsclient.start(); 
    wsclient.serviceHandlers = {
      bound: function() {
        ((opts.verbose) ? console.log('Websocket bound') : '');
      },
      connectFailed: function(error) {
        ((opts.verbose) ? console.log('Websocket connectFailed: ', error) : '');
      },
      disconnected: function() {
        ((opts.verbose) ? console.log('Websocket disconnected') : '');
      },
      onerror: function(error) {
        ((opts.verbose) ? console.log('Websocket onerror: ', error) : '');
      },
      bindingError: function(error) {
        ((opts.verbose) ? console.log('Websocket bindingError: ', error) : '');
      },
      connectionLost: function(error) {
        ((opts.verbose) ? console.log('Connection Lost: ', error) : '');
      },
      reconnecting: function(retry) {
        ((opts.verbose) ? console.log('Websocket Retrying: ', retry) : '');
        // change to true to stop retrying
        return false;
      }
    };
    return wsclient;
  };

0b01 · 2017-09-09T14:24:09Z

@CyberWlf I did exactly that. But it's still not working for me...

bigdataboss · 2017-09-09T14:31:20Z

@RickyHan double check everything. If Bittrex works in your browser and you copied user-agent and the cookie correctly it should work.

ale316 · 2017-09-09T14:34:27Z

@RickyHan Hey, I just got it to work on my server. Make sure that the IP you used to get the cf_clearance is the same as the one making the subsequent requests.

For the server I used this python library (https://libraries.io/github/Limero/cloudflare-scrape), to grab User-Agent and cf_clearance cookie, then did what @CyberWlf suggested (thanks!) and it worked.

0b01 · 2017-09-09T14:36:47Z

@CyberWlf @ale316 Thanks, I'll try that on my IPv4 server. My home address uses IPv6.

Update: It's working! Thank you! It's indeed because of IPv6.

0xecute · 2017-09-09T14:42:48Z

Did you make it work with python?
I got the correct cookie and the correct user agent header, but I got the following error from signalr-client:
error: There was an error invoking Hub method 'corehub.SubscribeToExchangeDeltas'.

Thanks for your help

ale316 · 2017-09-09T14:46:17Z

@0xecute If it throws that error, it is connected, so it seems to not be an issue with Cloudflare's protection. I guess make sure you're invoking the call correctly.

thanhlm86 · 2017-09-09T16:44:16Z

@armandohg help me, i run node scraper.js

{ errorType: 0, error: { Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 3128 3128:8 0 at ClientRequest.onError (C:\Users\ThinkPad\Desktop\node-bittrex-api\node_modules\tunne l-agent\index.js:177:17) at Object.onceWrapper (events.js:316:30) at emitOne (events.js:115:13) at ClientRequest.emit (events.js:210:7) at Socket.socketErrorListener (_http_client.js:401:9) at emitOne (events.js:115:13) at Socket.emit (events.js:210:7) at emitErrorNT (internal/streams/destroy.js:64:8) at _combinedTickCallback (internal/process/next_tick.js:138:11) at process._tickCallback (internal/process/next_tick.js:180:9) code: 'ECONNRESET' } }

mjmau · 2017-09-09T16:47:35Z

Thanks to @CyberWlf and @armandohg, combining your two fixes works great!

bigdataboss · 2017-09-09T17:08:44Z

Now let's combine them! Your connectws():

var connectws = function(callback) {
   wsclient = new signalR.client(
     opts.websockets_baseurl,
     opts.websockets_hubs, 
     undefined, true
   );
   if (opts.headers) {
     wsclient.headers['User-Agent'] = opts.headers.user_agent;
     wsclient.headers['cookie'] = opts.headers.cookie;
   }
   wsclient.start(); 
   wsclient.serviceHandlers = {
     bound: function() {
       ((opts.verbose) ? console.log('Websocket bound') : '');
     },
     connectFailed: function(error) {
       ((opts.verbose) ? console.log('Websocket connectFailed: ', error) : '');
     },
     disconnected: function() {
       ((opts.verbose) ? console.log('Websocket disconnected') : '');
     },
     onerror: function(error) {
       ((opts.verbose) ? console.log('Websocket onerror: ', error) : '');
     },
     bindingError: function(error) {
       ((opts.verbose) ? console.log('Websocket bindingError: ', error) : '');
     },
     connectionLost: function(error) {
       ((opts.verbose) ? console.log('Connection Lost: ', error) : '');
     },
     reconnecting: function(retry) {
       ((opts.verbose) ? console.log('Websocket Retrying: ', retry) : '');
       // change to true to stop retrying
       return false;
     }
   };
   return wsclient;
 };

Your main code:

const bittrex = require('node.bittrex.api');
const cloudscraper = require('cloudscraper');

cloudscraper.get('https://bittrex.com/', function (error, response, body) {
    if (error) {
        console.log('Cloudscraper error occurred');
    } else {  
        bittrex.options({
            headers: {
                cookie: response.request.headers["cookie"],
                user_agent: response.request.headers["User-Agent"]
            }
        });
        console.log('CloudFlare nailed');
        start(); // Your code here
    }
});

ninesalt · 2017-09-09T17:15:20Z

Can we expect an official update to the module soon though?

bigdataboss · 2017-09-09T17:25:48Z

@Swailem95 Take a look: https://github.com/n0mad01/node.bittrex.api

ninesalt · 2017-09-09T17:30:13Z

Well that sucks. Maybe someone's going to open a PR and fix it himself. That would be great.

glaucoheitor · 2017-09-09T18:24:49Z

Just need to update you code @CyberWlf, because response.request.headers["cookie"] replies with __cfduid AND cf_clearance.

bigdataboss · 2017-09-09T18:33:37Z

@glaucoheitor It's a hot fix, not an official solution. BTW, what's the problem with __cfduid ? It seems working

glaucoheitor · 2017-09-09T18:35:17Z

I know it's a hotfix. I am trying to use this here too.
Here don't work with that code. but if I put the cf_clearence code directly to signalR it works

bigdataboss · 2017-09-09T18:44:38Z

@glaucoheitor Works on my side. I don't see any reason why __cfduid could interrupt the process. You can update my solution btw :)

glaucoheitor · 2017-09-09T18:46:25Z

That what's weird, cause it works directly on the module file.

I was trying to update your solution, but I dont have that much knowledge. lol

bigdataboss · 2017-09-09T18:51:57Z

@glaucoheitor double check that you copied the exact code. Especially connectws() function. I use new "headers" option

thanhlm86 · 2017-09-09T18:59:24Z

Any body help,

i try the way @armandohg, it show error :

{ errorType: 0, error: { Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 3128 3128:80 at ClientRequest.onError (C:\Users\ThinkPad\Desktop\node-bittrex-api\node_modules\tunnel-agent\index.js:177:17) at Object.onceWrapper (events.js:316:30) at emitOne (events.js:115:13) at ClientRequest.emit (events.js:210:7) at Socket.socketErrorListener (_http_client.js:401:9) at emitOne (events.js:115:13) at Socket.emit (events.js:210:7) at emitErrorNT (internal/streams/destroy.js:64:8) at _combinedTickCallback (internal/process/next_tick.js:138:11) at process._tickCallback (internal/process/next_tick.js:180:9) code: 'ECONNRESET' } }
how to fix problem? Thanks.

dparlevliet · 2017-09-09T23:32:15Z

For those looking for an integrated fix for this issue I have committed it to https://github.com/dparlevliet/node.bittrex.api

Important note: this makes the websocket connection asynchronous so please see the updated documentation https://github.com/dparlevliet/node.bittrex.api#websockets

There is a unit test added which you can test with npm test tests/websocket.js to ensure it works for you.

If you have any further comments or suggestions please add them to here dparlevliet#1

LRonHubs · 2017-09-10T01:08:53Z

Thank you @dparlevliet

masalinas · 2017-09-10T08:59:28Z

Thank you @dparlevliet

p0ntsNL · 2017-11-12T13:16:06Z

So for those that have issues with this on python, for me this works now:

Please correct me if I am wrong! :)


from requests import Session
from signalr import Connection
import cfscrape
import time

markets = ['BTC-DGB', 'BTC-STRAT']

with cfscrape.create_scraper() as session:
  connection = Connection('http://socket.bittrex.com/signalr', session)

corehub = connection.register_hub('coreHub')

#create error handler
def print_error(error):
  print('error: ', error)

# debug information, show all data
def print_raw_data(*args, **kwargs):
  print (args, kwargs)

def ticker_data(*args, **kwargs):
  print ticker, (args, kwargs)

def market_data(*args, **kwargs):
  print market, (args, kwargs)

#connection.received += print_raw_data
connection.error += print_error

connection.start()
print "sending subscription request"
for market in markets:
  corehub.server.invoke('SubscribeToExchangeDeltas', market)

#corehub.client.on('updateSummaryState', ticker_data)
corehub.client.on('updateExchangeState', market_data)

connection.wait(120000) # close the connection if no message is received after this many seconds

jmontija · 2017-11-12T17:12:21Z

Nicely done cfscrape do the job. I don't know why we got this error the bittrex_socket is on and everything was working fine until yersterday.
Thanks

p0ntsNL · 2017-11-12T18:22:51Z

Nicely done cfscrape do the job. I don't know why we got this error the bittrex_socket is on and everything was working fine until yersterday. As well I was wondering if you know how to handle connection status to catch disconnection ? because I'm looping infinitly on connection.wait(0)
Thanks

I think its because Bittrex enabled Cloudflare today again :) so thats why I was working with cfscrape today

rclai · 2018-03-20T16:06:18Z

Is this still an issue? Just wondering since it's been months since there was any activity here.

0b01 mentioned this issue Sep 9, 2017

I'll take over #68

Open

dparlevliet mentioned this issue Sep 9, 2017

Websockets and Cloudflare dparlevliet/node.bittrex.api#1

Closed

LRonHubs closed this as completed Sep 10, 2017

lookfirst mentioned this issue Sep 10, 2017

Implement websockets lookfirst/bittrex-typescript#3

Open

0b01 mentioned this issue Oct 11, 2017

Handle Cloudflare Cookie Auth aloysius-pgast/bittrex-signalr-client#1

Closed

This was referenced Nov 12, 2017

Error 503 trying to get candles from Bittrex dparlevliet/node.bittrex.api#61

Open

Websocket support ericsomdahl/python-bittrex#57

Open

KeKs0r mentioned this issue Jan 29, 2018

Bittrex streaming updates toorop/go-bittrex#23

Open

This was referenced Feb 14, 2018

Can't make call to Signalr, 503 dparlevliet/node.bittrex.api#143

Closed

Can't make a call to WS/Signalr, 503, possible cloudflare issue? #89

Open

Errorr Message: Negotiate Unknown, 503 #67

Errorr Message: Negotiate Unknown, 503 #67

Comments

LRonHubs commented Sep 8, 2017

ale316 commented Sep 8, 2017

zduerr commented Sep 8, 2017

LRonHubs commented Sep 8, 2017

masalinas commented Sep 8, 2017 • edited Loading

TimLaMason commented Sep 8, 2017 via email

masalinas commented Sep 8, 2017 • edited Loading

junkomatic commented Sep 8, 2017

TimLaMason commented Sep 8, 2017 via email

masalinas commented Sep 8, 2017

junkomatic commented Sep 8, 2017

masalinas commented Sep 8, 2017

masalinas commented Sep 8, 2017 • edited Loading

junkomatic commented Sep 8, 2017 • edited Loading

LRonHubs commented Sep 8, 2017 via email

ale316 commented Sep 8, 2017 • edited Loading

n0mad01 commented Sep 8, 2017

strelov1 commented Sep 8, 2017

AGoetzDev commented Sep 9, 2017

ThePrimeagen commented Sep 9, 2017

usmankhanic commented Sep 9, 2017

ninesalt commented Sep 9, 2017

TimLaMason commented Sep 9, 2017 via email

metachris commented Sep 9, 2017

bigdataboss commented Sep 9, 2017 • edited Loading

0b01 commented Sep 9, 2017

bigdataboss commented Sep 9, 2017

ale316 commented Sep 9, 2017 • edited Loading

0b01 commented Sep 9, 2017 • edited Loading

0xecute commented Sep 9, 2017

ale316 commented Sep 9, 2017

thanhlm86 commented Sep 9, 2017 • edited Loading

mjmau commented Sep 9, 2017

bigdataboss commented Sep 9, 2017

ninesalt commented Sep 9, 2017

bigdataboss commented Sep 9, 2017

ninesalt commented Sep 9, 2017

glaucoheitor commented Sep 9, 2017

bigdataboss commented Sep 9, 2017

glaucoheitor commented Sep 9, 2017

bigdataboss commented Sep 9, 2017

glaucoheitor commented Sep 9, 2017

bigdataboss commented Sep 9, 2017

thanhlm86 commented Sep 9, 2017

dparlevliet commented Sep 9, 2017

LRonHubs commented Sep 10, 2017

masalinas commented Sep 10, 2017

p0ntsNL commented Nov 12, 2017 • edited Loading

jmontija commented Nov 12, 2017 • edited Loading

p0ntsNL commented Nov 12, 2017

rclai commented Mar 20, 2018 • edited Loading

masalinas commented Sep 8, 2017 •

edited

Loading

masalinas commented Sep 8, 2017 •

edited

Loading

masalinas commented Sep 8, 2017 •

edited

Loading

junkomatic commented Sep 8, 2017 •

edited

Loading

ale316 commented Sep 8, 2017 •

edited

Loading

bigdataboss commented Sep 9, 2017 •

edited

Loading

ale316 commented Sep 9, 2017 •

edited

Loading

0b01 commented Sep 9, 2017 •

edited

Loading

thanhlm86 commented Sep 9, 2017 •

edited

Loading

p0ntsNL commented Nov 12, 2017 •

edited

Loading

jmontija commented Nov 12, 2017 •

edited

Loading

rclai commented Mar 20, 2018 •

edited

Loading