Skip to content
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

Okex doesn't work #129

Closed
whitebone123 opened this issue Oct 10, 2021 · 13 comments
Closed

Okex doesn't work #129

whitebone123 opened this issue Oct 10, 2021 · 13 comments

Comments

@whitebone123
Copy link

Hi, I have all exchanges working except Okex. Do you also have the same problem? Below is my environment:

  • Docker on windows server 2019
  • Okex 'key', 'secrete' and 'password' are set through environment variables

In UI, under Okex exchange:

  • 'My balances' shows nothing.
  • 'New order' pops up error messagebox with text '[object object]'.
@aloysius-pgast
Copy link
Owner

Hi. My guess is you're passing an incorrect value for cfg.exchanges.okex.secret or cfg.exchanges.okex.password. Could you check network tab in browser console and see a 403 response is returned by gateway ?

@whitebone123
Copy link
Author

  1. Below is the screen shot of the network tab when error message popped up:
    image
  2. Below is the screen shot after close the error message:
    image

The error detail is:
{origin: "remote",…}
error: "okex {"error_message":"Please change to port v1 when you are using v1 apiKey. If you wish to use port v3, please register a v3 apiKey.","code":30016,"error_code":"30016","message":"Please change to port v1 when you are using v1 apiKey. If you wish to use port v3, please register a v3 apiKey."}"
extError: {errorType: "ExchangeError.InvalidRequest.UnknownError",…}
origin: "remote"
route: {method: "GET", path: "/exchanges/okex/balances/"}

@aloysius-pgast
Copy link
Owner

aloysius-pgast commented Oct 10, 2021

Can you try to generate a new api key (using V3 option) on Okex and see if it's working better ? (as the error message seems to indicate that's api key is using an old format).

@whitebone123
Copy link
Author

whitebone123 commented Oct 10, 2021

There is only V5 API key generation option in Okex now. Is it why the geatway throwh error?
image

@whitebone123
Copy link
Author

I've generated another V5 API key and had the same error in gateway.

@aloysius-pgast
Copy link
Owner

Hi. I published a new version with support for OKex v5 API. After pulling the new docker image & re-creating the container, everything should be better. Let me know

@whitebone123
Copy link
Author

Hi, I've pulled the new version on dcoker. Everything works fine except 'Okex/My balances'. It shows an empty table, but I have few USDT in this account.
image

@aloysius-pgast
Copy link
Owner

Can you ensure that you're using "Unified account" for OKex ?

@whitebone123
Copy link
Author

Yes, it is. My account mode is 'simple spot trading user'. I switched to 'Single-currency margin mode' and got the same result in Gateway.

@aloysius-pgast
Copy link
Owner

With a new account, balance shows up correctly after transfering funds from Funding account to Trading account. Are you able to trade from https://www.okex.com/trade-spot ?

@whitebone123
Copy link
Author

whitebone123 commented Oct 12, 2021

Hi, according to your suggestion, I transferred the USDT from funding account to trading account (unified account). And, It appeared in 'my balances'. Sorry about my misunderstanding of the unified account.
BTW, do you have plan to support more exchanges like MEXC, Gate.io.

@aloysius-pgast
Copy link
Owner

Glas it’s working 😉. Regarding adding more exchanges it might be possible but this project was mainly developed for our own use (small team of crypto enthusiasts). The idea was to make basic trading automation easier and have a unified basic ui across the exchanges we used the most. While the project is maintained, it does not really have enough traction to spend time integrating and supporting many exchanges. So unless we have many requests to implement a specific exchange, we will probably stick to the current ones 😁

@whitebone123
Copy link
Author

Ok, thanks. It's an excellent project. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants