-
-
Notifications
You must be signed in to change notification settings - Fork 810
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
Okx Exchange - API key unknown #2832
Comments
Changes in OKX API server. I recently received an email from OKX telling their API servers will be updated to another host. I checked the "Updated Documentation" but I couldn't find this information so please check your email for more information. |
Hi @TitaniumMaker, thanks for the update! It will help us fixing the issue. |
Hi @TitaniumMaker, I use okx myself and am currently working on a fix which might also solve your issue. I wasn't aware of these okx changes. You got any docs or information regarding their go live? Also they are splitting the rest and websocket domains? What's the current behaviour? I've fixed the issue with current eu servers 'my.okx' not working. I have to implement a user friendly way to select custom hostnames still. This might only be for rest though, will have to investigate websocket behaviour. Soon as I find out where OctoBot is handling it's frontend expect me to push the changes to my fork and send a pull request for the team to review. |
Step 1: Have you search for this issue before posting it?
If you have discovered a bug in the bot, please search our issue tracker.
If it hasn't been reported, please create a new issue.
Step 2: Describe your environment
ccxt/ccxt#24601
Step 3: Describe the problem:
Describe the bug
When entering working api credentials the Exchange accounts setup throws an unknow api key error
Expected behavior
Succes: Account should be linked to api credentials
Steps to reproduce:
Observed Results:
Relevant code exceptions or logs:
More details here
I would like to add a region variable overwriting the hardcoded ccxt hostname for the okx provider, as shown in the above code this works. We could expose the variable as a boolean switch on the exchange setup page.
The text was updated successfully, but these errors were encountered: