FetchError: Unhandled promise rejection (ENOTFOUND) about binance-api-node HOT 6 CLOSED

Investigation: We can make use of our own error.code which will be ENOENT or ENOTFOUND in this case!

Small workaround:

const Binance = require('binance-api-node').default
const dotenv = require('dotenv')

process.on('unhandledRejection', error => {
  console.error('Catched Binance error', error)
  process.exit(1)
})

if (!process.env.BINANCE_API_KEY) dotenv.load()

const client = Binance({
  apiKey: process.env.BINANCE_API_KEY,
  apiSecret: process.env.BINANCE_API_SECRET,
})

async function getOrder() {
  try {
    const order = await client.getOrder({symbol: 'TRXETH', orderId: 20123533})
    console.log(`order (${Date.now()})`, order)
  } catch (error) {
    if (['ENOENT', 'ENOTFOUND'].includes(error.code)) {
      console.log('Waiting for internet to come back...')
    } else {
      throw error
    }
  } finally {
    setTimeout(getOrder, 2000)
  }
}

getOrder()

I tested this workaround for some time but sometimes I still receive the following error:

Error: Timestamp for this request is outside of the recvWindow.

@balthazar: Do you have any idea how we can tackle the recvWindow error?

from binance-api-node.

This second error is most likely due to your computer having an out-of-sync clock, maybe you should try updating it.

As for how to handle this case maybe we should catch the ENOENT and ENOTFOUND and throw a more meaningful error that we could include in our error map. The try catch approach seems like the preferred solution anyway, but we need to catch these connectivity errors of websockets too.

from binance-api-node.

The Timestamp for this request is outside of the recvWindow often happens, when I go offline and go back online. I think it's related to this. Can it be that the request gets cached and is too old, when I come back online?

from binance-api-node.

I am also getting Timestamp for this request is outside of the recvWindow any idea why?

from binance-api-node.

@bennyn Most likely it if it doesn't error out before the connection goes back on

from binance-api-node.

I will close the issue here because we now export ErrorCodes and based on them the using application can retrigger certain API calls.

@jsappme The "Timestamp for this request is outside of the recvWindow" issue will be tackled in this issue: #80 - Please also try to use the useServerTime property, it might already fix your issue. 😃

from binance-api-node.