2.13 Common error messages, exchange API error codes, various problems encountered by digital currency robots!

Common bot error messages, exchange API error codes

• API documentation and address collection

  • Bibox

    https://github.com/Biboxcom/api_reference/wiki/api_reference

  • hadax

    https://github.com/huobiapi/API_Docs/wiki/REST_api_reference

  • Gate.IO

    https://gate.io/api2

  • Bit-Z

    https://www.bit-z.com/api.html

  • Bitfinex

    https://bitfinex.readme.io/v2/reference

  • Deribit

    • The v1 version:

    https://www.deribit.com/pages/docs/api https://github.com/deribit/deribit-api-js/blob/master/src/RestClient.js

    • The v2 version:

    https://www.deribit.com/static/console/index.html https://docs.deribit.com/v2/#deribit-api-v2-0-0

    Exchange testing environment:https://test.deribit.com

  • Kraken

    https://www.kraken.com/en-us/help/api#get-ticker-info

  • GDAX

    https://docs.gdax.com/

  • Binance

    https://github.com/binance-exchange/binance-official-api-docs/blob/master/errors.md

  • ZB

    https://www.zb.com/i/developer

  • OKEX

    https://www.okex.com/rest_request.html(abandoned)

    https://github.com/okcoin-okex/OKEx.com-api-docs/tree/master/API-For-Spot-CN(Coin in cash)

    https://github.com/okcoin-okex/OKEx.com-api-docs/tree/master/API-For-Futures-CN(contract)

  • Coin Pro

    https://github.com/huobiapi/API_Docs/wiki

  • BitPie

    http://api-docs.expie.com/en/latest/http-api/order-api.html#market-order-place

  • CoinEx

    https://github.com/coinexcom/coinex_exchange_api/wiki

  • BitMEX

    https://www.bitmex.com/api/explorer/

  • BigOne

    https://open.big.one/docs/authentication.html

  • P network

    https://poloniex.com/support/api/

  • HitBtc

    https://api.hitbtc.com/#rest-api-reference

  • OKCoin is an international site.

    https://support.okcoin.com/hc/zh-cn/articles/360000695152-REST-API请求交互

  • OCX

    https://github.com/ocxapi/api-docs/blob/master/api_v2.zh_CN.md

  • CoinBig

    https://github.com/coinbigapi/coinbigapi/wiki/API-Document

  • IDAX

    https://github.com/idax-exchange/idax-official-api-docs/blob/master/rest-api - IDAX.md

  • FCOIN

    https://developer.fcoin.com/zh.html

  • Bizu people

    https://github.com/bizukex/API-docs-bizu.com/blob/master/README.md

  • OKEX (V3 API)

    https://www.okex.com/docs/zh/

  • HuobiDM (token contract) is a cryptocurrency exchange.

    https://github.com/huobiapi/API_Docs/wiki/REST_api_reference_Derivatives

  • BHEX

    https://github.com/bhexopen/BHEX-OpenApi/blob/master/doc/rest-api.md

  • EXX

    https://www.exx.com/help/restApi

• The code of the coin API error:

  • REST Error Code

• OKCoin API error code is:

  • REST error code The code is wrong.

The error code is (massive transaction)

• WebSocket error code The code is wrong.

• Polynetic error codes

  

• Common misinformation

• 1、GetAccount: Post https://www.okcoin.cn/api/v1/userinfo.do: EOF

  This error was reported in the protocol establishing the EOF unintentional termination symbol in the file stream, causing the interruption. The reason may be that the API access frequency is too high. The policy routing frequency can be taken into account. This error is not of great impact if the frequency is not particularly high.

• 2, the token error GetTicker: 534:

  This problem is long-standing, the error code is returned by the token server. However, the API documentation was not queried and did not see the 534 error, which should be a network error. If it is not very frequent, it does not affect much.

• 3, connection reset by peer error:

  

  Search for information:

  The problem is a network error.

• 4、 GetTicker: Get https://api.huobi.com/staticmarket/ticker_btc_json.js: dial tcp: lookup api.huobi.com: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

  

  The problem is a network error.

• 5th, memory error.

  

  This may be related to memory insufficiency or virtual memory usage.

• 6, Common error: Attributes of undefined variables are accessed.

  

  The chart above shows that accessing the Price property of an undefined variable caused an error. Check where the.Price call is located to see if the previous variable is possible to be undefined.

• 7, a link was forced to close by the remote host.

  

  A link is forced to close by the remote host (exchange server) without interrupting the policy operation.

• 8 Exchange configuration issues

  

  Generally visited an incorrectly configured exchange. Check if the exchange configuration is correct and whether the policy has accessed unconfigured exchanges[n] objects.

• 9, Error reported when calling the Unix Nano () function.

  

  Download the latest host and call the function normally after deployment. This bug was found when using the previous versions of the host to run real-time.

• 10、nonce has expired

  

  The time has passed. 1, which may be the time of the system running the custodian and the time of the exchange server. How to deal with this: correct the time of the system where the administrator is.

  The API KEY that may have been used elsewhere on the exchange, causing timing discrepancies, caused this issue. How to do it: Reapply for the API KEY using the new API KEY.

• 11、no such host

  

  DNS configuration issue on local network try to use114.114.114.114

• 12、nonce not incremented

  

  It is possible that other programs have used the exchange account API KEY and then used the Inventor Quantification Connection, causing. It is also possible that due to too frequent access to the API in a short period of time, the error does not occur after the user adds the Sleep function (delay) test after each API call. Zaif exchanges limit nonce based on 1 second increase, all verified nonce API calls require 1 second interval.

• 13, wrong API KEY

  

  

• When deploying the admin (interface version) in win 10, double-click on the admin does not respond, change the command-line version. The admin displays no permissions.

  Reason: the security mechanism of win 10, default unrecognized applications are not allowed to run. Solution: Right-click to run the hostexe program, select the lock attribute bar, and at the bottom of the first page, find the lock unlock bar Select it. I'm going to try to get it up and running again.

• 15 Binance error reported

  

  If you withdraw too much money and the transaction rate is too low, it will cause Binance to close your account for a while, and you will report this error.

• 16th Binance Reported Mistake

  Recently, Binance has been reporting some time-lapse asynchronous errors such as:

  • Timestamp for this request was 1000ms ahead of the server’s time

  • Timestamp for this request is outside of the recvWindow

  If your host is running on a Linux system, you can try using this command to solve:

  # /ntp 服务移除
  # sudo launchctl remove org.ntp.ntpd
  # //更新本地时间
  # sudo ntpdate cn.pool.ntp.org
  

  • 

  The error is that the frequency of access to the exchange API is over-restricted, the IP is blocked, and the blocking can only be lifted at the time of the time stamp shown above.

• I have a lot of problems!

• 1, in digital currency futures (e.g. OKCoin futures) the following problems arise when operating multiple contracts using the exchange.Go function (e.g. concurrent operation):

  This strategy has caused a number of problems due to the use of the Go function (which was intended to operate concurrently), which causes the contract to be unable to be switched when running concurrently, and the actual contract type is not yet switched when the next contract is in the next contract, causing a series of problems. So do not use the exchange.GoAPI when operating multiple futures varieties, avoiding BUG.

• Other APIs

• exchange.SetMaxDigits is set to a decimal digit, and the parameter is 2, i.e. keep 2 digits.

I'm not sure.