-
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bitstamp loadMarkets() fails: Parse Error #5149
Comments
@redwoz hi! What's your location? It is known to block some countries, for example, not accessible from Russia, so, i'm using it with a proxy. Have you tried with a proxy, btw? |
↑ This is actually a HTTP response text received from the exchange, saying that the parseError has happened on their side (we don't have such a message anywhere inside the code of the lib). So, it depends on factors outside of the codebase, probably your location/headers or some other cause. Will need some time to reproduce and resolve this. |
I've got the same error after updating node to v12 from v11.
Test code:
Output Node 11: handleRestResponse: Output Node 12: ExchangeNotAvailable [Error]: bitstamp GET https://www.bitstamp.net/api/v2/trading-pairs-info/ system request to https://www.bitstamp.net/api/v2/trading-pairs-info/ failed, reason: Parse Error |
@houtenbos do you still have this error and what's your version of CCXT ? |
@kroitor I have still the same error when running the script now with: |
@houtenbos which |
works for me jfyi |
@frosty00 yep, i think this is setup-specific or user-specific. @houtenbos would be great if you could try it on a clean setup to verify it, unfortunately, can't reproduce it yet. |
I've reproduced it on my side with Node 12.2, apparently, bitstamp doesn't like requests without a user-agent, so I've added a chrome user-agent, the fix will arrive in 1.18.633 in 20 minutes. |
This error still persists with Node 12 even with the user agent in the header. It goes away when using Node 11.
Error confirmed with: |
|
@shussekaido thx, this is very helpful! |
browsing to https://www.bitstamp.net/api/v2/trading-pairs-info/ via Chrome:
The text was updated successfully, but these errors were encountered: