feat: show error when use wrong API key

[chrisleekr]

Description

There have been several issues opened that the bot is stuck at loading. 99% of this issue is caused by using a wrong API key.

To provide more information, I've updated the front end to display an error message when the bot can't get account information.

Related Issue

#538

Motivation and Context

As description.

How Has This Been Tested?

Screenshots (if appropriate):

[rando128]

@chrisleekr, did you test in dev mode?

Launching the bot for local development via docker-compose -f docker-compose.yml up -d --build leads to the APIError screen.

_.get(accountInfo, 'accountType') is undefined.

[chrisleekr]

@rando128
yeah? hm, let me check.

[chrisleekr]

Hm, @rando128 are you sure you configured the API key? can you check again?
I just tested with the master branch and seems fine.

[rando128]

Yeah, that's weird. My .env has all the keys setup:

BINANCE_MODE=test

## Live
BINANCE_LIVE_API_KEY=...
BINANCE_LIVE_SECRET_KEY=...

## Test
BINANCE_TEST_API_KEY=...
BINANCE_TEST_SECRET_KEY=...

my docker-composer.yml has:

...
      target: dev-stage
...
      - BINANCE_MODE=test
...

I didn't change my setup, just pulled 0.094. And the APIError screen started to show up despite a functional environment.

If it works on your side and nobody is facing the same issue I have, I will simply hack my LockScreen.js.

[chrisleekr]

Yeah, I would assume you would have the correct configuration.
You might find a bug? Not sure. Let me know if you find anything.

[peweb]

@rando128 @chrisleekr
My bot stopped working after updating to from 094 to 0.95
I didnt change env and my API keys cant expetive because they are attached to static IP.
I added BINANCE_MODE=live in the env file as well but it didnt help.

I double checked everything, generated new API keys but I still cant login to the bot interface and keep getting the new error screen - Failed to load your account information.

Can you please help me fix it?

Thanks!

My env file is

BINANCE_MODE=live
BINANCE_LIVE_API_KEY=yMo.....
BINANCE_LIVE_SECRET_KEY=p242w...

BINANCE_TEST_API_KEY=fXQdqeK4aDCDx....
BINANCE_TEST_SECRET_KEY=7ZVCKtgrItrc60u....

BINANCE_SLACK_ENABLED=false
BINANCE_LOCAL_TUNNEL_ENABLED=false

BINANCE_FEATURE_TOGGLE_NOTIFY_ORDER_CONFIRM=false
BINANCE_FEATURE_TOGGLE_NOTIFY_DEBUG=false
BINANCE_FEATURE_TOGGLE_NOTIFY_ORDER_EXECUTE=true

BINANCE_AUTHENTICATION_ENABLED=true
BINANCE_AUTHENTICATION_PASSWORD=xxx
BINANCE_JOBS_TRAILING_TRADE_BOT_OPTIONS_AUTHENTICATION_LOCK_LIST=true
BINANCE_JOBS_TRAILING_TRADE_BOT_OPTIONS_AUTHENTICATION_LOCK_AFTER=120

I have
BINANCE_MODE=live in the docker-compose.server.yml

[habibalkhabbaz]

@peweb

There is a merged pull request #556 which solves a similar issue.
It may solve your issue too.

[rando128]

@peweb, depending on your grids status, you might be facing bug #555. It's fixed and merged in master, but not released. Though it is not related to the API error screen. Do you see any error in the console of your browser?

[peweb]

@rando128 yes,

How to switch to master?

[rando128]

Hum, AFAIK the bot doesn't use this library. So this is something else. Check this thread just in case.

[peweb]

@rando128 Yeah Loom extension!
Uninstalled it and now no errors in console but I still can login to the bot. May I downgrade to 0.94?

[peweb]

@chrisleekr @rando128
Just to let you know the master works fine. I prefer to work with docker-compose.server.yml so please, kindly release the last fixes. Thanks.

[VandrisV]

I have same issues master work fine till i loud dompose.server.yml and all stop.

[chrisleekr]

Guys, thanks for the investigation.

I will release a new version.