JulyIghor / QtBitcoinTrader

Secure multi crypto exchange trading client
https://sourceforge.net/projects/bitcointrader/
730 stars 374 forks source link

Bitstamp API errors #155

Closed 1benik closed 10 years ago

1benik commented 10 years ago

In the latest version of Qt Bitcoin Trader (version 1.07.99), I can not use the exchange Bitstamp. The error message below is shown after starting Qt Bitcoin Trader:

Identification required to access private API. Please enter valid API key and secret. Please try to enable "Trade" and "Info" rights for this API pair. If it did not help, please generate new API keys and re-create a new profile.

Missing key, signature and nonce parameters 202

The rights of the API key are set properly in my Bitstamp account. I also tried adding a new profile with a new API key in Qt Bitcoin Trader, but the same error message is shown after starting Qt Bitcoin Trader with the new profile. Below is a link to Pastebin with a debug log from Qt Bitcoin Trader:

http://pastebin.com/BN9QAR40

JulyIghor commented 10 years ago

What Client ID you have used when you add new profile?

1benik commented 10 years ago

I used the Client ID shown on the "Balance" page in my Bitstamp account. My Client ID is: 506853

JulyIghor commented 10 years ago

Try to enable Old API access on this page: https://www.bitstamp.net/account/settings/ My account is not verified, on Bitstamp so I can not test it by myself.

1benik commented 10 years ago

Unfortunately, there is no such option on the "Settings" page in my Bitstamp account. The only settings I can change are my bank account details, password and notification preferences. On the "API Access" page (https://www.bitstamp.net/account/security/api/) is also no option to enable the old API.

JulyIghor commented 10 years ago

2014-08-31 19 04 39

JulyIghor commented 10 years ago

I think I fixed it and it was not Bitstamp issue. Please sync and re-compile source code and confirm does it fixed or not.

1benik commented 10 years ago

The problem with the Bitstamp API is fixed after recompiling the source code. Thanks for the quick fix!